lower case environment variables for abbreviations with cygwin
edwin.goei at sun.com
Sun May 23 02:44:20 EDT 2004
Adrian Aichner <adrian <at> xemacs.org> writes:
> Edwin Goei <Edwin.Goei <at> Sun.COM> writes:
> > When I was running xemacs on unix, I would set lower case environment
> > variables in my shell such as "setenv work /long/path/to/work/dir" and
> > then launch xemacs. Within xemacs I could then use find-file with
> > $work/xxx and it would all work.
> > I am now running on cygwin "XEmacs 21.4 (patch 13) \"Rational FORTRAN\"
> > [Lucid] (i686-pc-cygwin) of Sun May 25 2003 on TSUNAMI", and this no
> > longer works. The lower case env vars are converted to all caps (eg.
> > $WORK) which is more difficult to type.
> Hi Edwin, what shell are you using to set the lowercase env. var. on
> How do you do it?
> Does that shell recognize the lowercase env. variable?
> Is this really an XEmacs issue at all?
Sorry for the slow response. I didn't know you responded to me because I never
got your reply. :-( I just happen to be searching in google and found your
response! In any case, I think it's a cygwin related problem since I launch
xemacs using a shortcut with the following target:
'C:\cygwin\bin\bash.exe --login -c 'cygstart
Someone on the cygwin list suggested this, but I think cygstart may be
capitalizing the env var names. I'll ask on the cygwin list. Thanks, for the
BTW, there are problems with using env vars as abbreviations. For example,
adding a new abbreviation means adding a new envar and setting
process-environment and setting it in all shell-mode buffers. Maybe there is a
More information about the XEmacs-Beta