Re: Environment variable documentation
On Dec 1 16:59, Ken Brown wrote: On 12/1/2009 4:08 PM, Corinna Vinschen wrote: On Dec 1 19:24, John Morrison wrote: On Tue, December 1, 2009 4:32 pm, Ken Brown wrote: OK, my patch is attached. It anticipates the change to the default .bashrc file that we've been discussing in the thread cited above. Hi Ken, While I think it's a good idea to point out that they are (will be) unset in the users .bashrc I'm not sure it's a good idea to tell people where the default (/etc/defaults/etc/skel/.bashrc) is, since this will be overwritten by the base package. If people want to maintain their own set of changes which is used in future that the package does not overwrite /etc/skel/.bashrc is what they should edit. However, since the skel files are only copied *once* ~/.bashrc should be the first point of call. Hope that makes sense! Good point. I agree. A revised patch is attached. Thank you. I've applied your patch with Eric's change. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Environment variable documentation
On Nov 30 17:04, Ken Brown wrote: The discussion currently going on in the thread http://cygwin.com/ml/cygwin/2009-11/threads.html#00892 makes me think that the section on environment variables in the user's guide (http://cygwin.com/1.7/cygwin-ug-net/setup-env.html) could use some expansion. For example, it's not stated explicitly which Windows environment variables get imported into Cygwin (all of them?), nor is there a complete list of variables containing paths Yes, all of them. that get converted to Unix format. PATH, HOME, and LD_LIBRARY_PATH are mentioned, but TMPDIR, TMP, and TEMP are omitted. I think the last three should be listed, along with the suggestion that users might want to unset them in the Cygwin environment. Yes, TMPDIR, TMP, and TEMP are handled the same way as PATH, HOME, and LD_LIBRARY_PATH. These six variables are the set of environment variables which are subject to path conversion from Windows to POSIX and vice versa. I would be willing to take a stab at writing a patch if the developers think this would be useful. That sounds like a nice idea. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Environment variable documentation
On 12/1/2009 4:45 AM, Corinna Vinschen wrote: On Nov 30 17:04, Ken Brown wrote: The discussion currently going on in the thread http://cygwin.com/ml/cygwin/2009-11/threads.html#00892 makes me think that the section on environment variables in the user's guide (http://cygwin.com/1.7/cygwin-ug-net/setup-env.html) could use some expansion. For example, it's not stated explicitly which Windows environment variables get imported into Cygwin (all of them?), nor is there a complete list of variables containing paths Yes, all of them. that get converted to Unix format. PATH, HOME, and LD_LIBRARY_PATH are mentioned, but TMPDIR, TMP, and TEMP are omitted. I think the last three should be listed, along with the suggestion that users might want to unset them in the Cygwin environment. Yes, TMPDIR, TMP, and TEMP are handled the same way as PATH, HOME, and LD_LIBRARY_PATH. These six variables are the set of environment variables which are subject to path conversion from Windows to POSIX and vice versa. I would be willing to take a stab at writing a patch if the developers think this would be useful. That sounds like a nice idea. OK, my patch is attached. It anticipates the change to the default .bashrc file that we've been discussing in the thread cited above. Ken --- setup2.sgml.orig2009-12-01 10:37:00.15625 -0500 +++ setup2.sgml 2009-12-01 11:29:53.56250 -0500 @@ -4,7 +4,9 @@ You may wish to specify settings of several important environment variables that affect Cygwin's operation. Some of these settings need to be in effect prior to launching the initial Cygwin session (before -starting your bash shell, for instance), and are, consequentially, best +starting your bash shell, for instance). They should therefore be set +in the Windows environment; all Windows environment variables are +imported when Cygwin starts. Such settings can be placed in a .bat file. An initial file is named Cygwin.bat and is created in the Cygwin root directory that you specified during setup. Note that the Cygwin option of the Start Menu points to Cygwin.bat. Edit @@ -66,6 +68,21 @@ functiondlopen ()/function call and do not need this variable. /para +para +In addition to envarPATH/envar, envarHOME/envar, +and envarLD_LIBRARY_PATH/envar, there are three other environment +variables which, if they exist in the Windows environment, are +converted to UNIX format: envarTMPDIR/envar, envarTMP/envar, +and envarTEMP/envar. The first is not set by default in the +Windows environment but the other two are, and they point to the +default Windows temporary directory. If set, these variables will be +used by some Cygwin applications, possibly with unexpected results. +They are therefore unset in the default filename.bashrc/filename +file (filename/etc/defaults/etc/skel/.bashrc/filename). You may +prefer to set them to point to filename/tmp/filename or to any +other temporary directory of your choice. +/para + /sect1 sect1 id=setup-maxmemtitleChanging Cygwin's Maximum Memory/title -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Environment variable documentation
On Dec 1 11:32, Ken Brown wrote: On 12/1/2009 4:45 AM, Corinna Vinschen wrote: On Nov 30 17:04, Ken Brown wrote: I would be willing to take a stab at writing a patch if the developers think this would be useful. That sounds like a nice idea. OK, my patch is attached. It anticipates the change to the default .bashrc file that we've been discussing in the thread cited above. Ken --- setup2.sgml.orig 2009-12-01 10:37:00.15625 -0500 +++ setup2.sgml 2009-12-01 11:29:53.56250 -0500 @@ -4,7 +4,9 @@ You may wish to specify settings of several important environment variables that affect Cygwin's operation. Some of these settings need to be in effect prior to launching the initial Cygwin session (before -starting your bash shell, for instance), and are, consequentially, best +starting your bash shell, for instance). They should therefore be set +in the Windows environment; all Windows environment variables are +imported when Cygwin starts. Such settings can be placed in a .bat file. An initial file is named Cygwin.bat and is created in the Cygwin root directory that you specified during setup. Note that the Cygwin option of the Start Menu points to Cygwin.bat. Edit @@ -66,6 +68,21 @@ functiondlopen ()/function call and do not need this variable. /para +para +In addition to envarPATH/envar, envarHOME/envar, +and envarLD_LIBRARY_PATH/envar, there are three other environment +variables which, if they exist in the Windows environment, are +converted to UNIX format: envarTMPDIR/envar, envarTMP/envar, +and envarTEMP/envar. The first is not set by default in the +Windows environment but the other two are, and they point to the +default Windows temporary directory. If set, these variables will be +used by some Cygwin applications, possibly with unexpected results. +They are therefore unset in the default filename.bashrc/filename +file (filename/etc/defaults/etc/skel/.bashrc/filename). You may +prefer to set them to point to filename/tmp/filename or to any +other temporary directory of your choice. +/para + /sect1 sect1 id=setup-maxmemtitleChanging Cygwin's Maximum Memory/title Looks good. Thanks for doing this. Let's just wait until the .bashrc related thread settled down to a conclusion. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Environment variable documentation
On Tue, December 1, 2009 4:32 pm, Ken Brown wrote: On 12/1/2009 4:45 AM, Corinna Vinschen wrote: On Nov 30 17:04, Ken Brown wrote: The discussion currently going on in the thread http://cygwin.com/ml/cygwin/2009-11/threads.html#00892 makes me think that the section on environment variables in the user's guide (http://cygwin.com/1.7/cygwin-ug-net/setup-env.html) could use some expansion. For example, it's not stated explicitly which Windows environment variables get imported into Cygwin (all of them?), nor is there a complete list of variables containing paths Yes, all of them. that get converted to Unix format. PATH, HOME, and LD_LIBRARY_PATH are mentioned, but TMPDIR, TMP, and TEMP are omitted. I think the last three should be listed, along with the suggestion that users might want to unset them in the Cygwin environment. Yes, TMPDIR, TMP, and TEMP are handled the same way as PATH, HOME, and LD_LIBRARY_PATH. These six variables are the set of environment variables which are subject to path conversion from Windows to POSIX and vice versa. I would be willing to take a stab at writing a patch if the developers think this would be useful. That sounds like a nice idea. OK, my patch is attached. It anticipates the change to the default .bashrc file that we've been discussing in the thread cited above. Hi Ken, While I think it's a good idea to point out that they are (will be) unset in the users .bashrc I'm not sure it's a good idea to tell people where the default (/etc/defaults/etc/skel/.bashrc) is, since this will be overwritten by the base package. If people want to maintain their own set of changes which is used in future that the package does not overwrite /etc/skel/.bashrc is what they should edit. However, since the skel files are only copied *once* ~/.bashrc should be the first point of call. Hope that makes sense! J. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Environment variable documentation
On Dec 1 19:24, John Morrison wrote: On Tue, December 1, 2009 4:32 pm, Ken Brown wrote: OK, my patch is attached. It anticipates the change to the default .bashrc file that we've been discussing in the thread cited above. Hi Ken, While I think it's a good idea to point out that they are (will be) unset in the users .bashrc I'm not sure it's a good idea to tell people where the default (/etc/defaults/etc/skel/.bashrc) is, since this will be overwritten by the base package. If people want to maintain their own set of changes which is used in future that the package does not overwrite /etc/skel/.bashrc is what they should edit. However, since the skel files are only copied *once* ~/.bashrc should be the first point of call. Hope that makes sense! Good point. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Environment variable documentation
On 12/1/2009 4:08 PM, Corinna Vinschen wrote: On Dec 1 19:24, John Morrison wrote: On Tue, December 1, 2009 4:32 pm, Ken Brown wrote: OK, my patch is attached. It anticipates the change to the default .bashrc file that we've been discussing in the thread cited above. Hi Ken, While I think it's a good idea to point out that they are (will be) unset in the users .bashrc I'm not sure it's a good idea to tell people where the default (/etc/defaults/etc/skel/.bashrc) is, since this will be overwritten by the base package. If people want to maintain their own set of changes which is used in future that the package does not overwrite /etc/skel/.bashrc is what they should edit. However, since the skel files are only copied *once* ~/.bashrc should be the first point of call. Hope that makes sense! Good point. I agree. A revised patch is attached. Ken --- setup2.sgml.orig2009-12-01 10:37:00.15625 -0500 +++ setup2.sgml 2009-12-01 16:57:26.09375 -0500 @@ -4,7 +4,9 @@ You may wish to specify settings of several important environment variables that affect Cygwin's operation. Some of these settings need to be in effect prior to launching the initial Cygwin session (before -starting your bash shell, for instance), and are, consequentially, best +starting your bash shell, for instance). They should therefore be set +in the Windows environment; all Windows environment variables are +imported when Cygwin starts. Such settings can be placed in a .bat file. An initial file is named Cygwin.bat and is created in the Cygwin root directory that you specified during setup. Note that the Cygwin option of the Start Menu points to Cygwin.bat. Edit @@ -66,6 +68,34 @@ functiondlopen ()/function call and do not need this variable. /para +para +In addition to envarPATH/envar, envarHOME/envar, +and envarLD_LIBRARY_PATH/envar, there are three other environment +variables which, if they exist in the Windows environment, are +converted to UNIX format: envarTMPDIR/envar, envarTMP/envar, +and envarTEMP/envar. The first is not set by default in the +Windows environment but the other two are, and they point to the +default Windows temporary directory. If set, these variables will be +used by some Cygwin applications, possibly with unexpected results. +You may therefore want to unset them by adding the following two lines +to your filename.bashrc/filename file: + +screen +unset TMP +unset TEMP +/screen + +This is done in the default filename.bashrc/filename file. +Alternatively, you could set envarTMP/envar +and envarTEMP/envar to point to filename/tmp/filename or to +any other temporary directory of your choice. For example: + +screen +export TMP=/tmp +export TEMP=/tmp +/screen +/para + /sect1 sect1 id=setup-maxmemtitleChanging Cygwin's Maximum Memory/title -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Environment variable documentation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ken Brown on 12/1/2009 2:59 PM: I agree. A revised patch is attached. +You may therefore want to unset them by adding the following two lines +to your filename.bashrc/filename file: filename~/.bashrc/filename - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksV1aoACgkQ84KuGfSFAYBGigCfRzgqnbdxgqORiv1vBC3r5mA4 Q7EAoJ27WHrTXAZWACmkoIRcIl8CHbOK =7WbE -END PGP SIGNATURE- -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
