Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <001f01bfe53f$e4e22730$f7c723cb@lifelesswks> From: "Robert Collins" To: References: <0B8B193792F5D111B1BB00A0C9B0FC352DEDD4 AT exchange DOT windh DOT net> Subject: Re: export doesn't work Date: Tue, 4 Jul 2000 08:41:55 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 AFAIK Cygwin works with NT's existing environment handling. NT keeps a separate environment for each process when it is launched, and you need to send an event to all programs for them to get a new environment. So export will set your current process's environment but not (say) that of another bash shell you are running. There is a tool in the NT resourcekit, SETENV I think, that can do this reasonably well. Rob ----- Original Message ----- From: "Peter Neubauer" To: Sent: Tuesday, July 04, 2000 7:12 AM Subject: export doesn't work Hello, does someone know why the EXPORT-command does not have any effect ón my NT system? do I have to have a special right or s thanks peter ;) -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com