RE: zsh for win32 - installation of zshrc

[Amol Deshpande <amold@xxxxxxxxxxxxx>]

by the way, you may find that if a user starts up zsh from another
drive, the shell will not find /etc/zshenv.

> ----------
> From: 	Bart Schaefer[SMTP:schaefer@xxxxxxxxxxxxxxxx]
> Sent: 	Tuesday, September 15, 1998 10:18 AM
> To: 	ZShell Users List
> Cc: 	amol@xxxxxxxxx
> Subject: 	Re: zsh for win32 - installation of zshrc
> 
> On Sep 14,  7:55pm, 'Sven Guckes' wrote:
> } Subject: Re: zsh for win32 - installation of zshrc
> }
> } Quoting Bart Schaefer (schaefer@xxxxxxxxxxxxxxxx):
> } > zagzig[21] zcat zsh.exe.gz | strings -a | less +/zshrc
> } 
> } Actually, I tried just that - but I figured that it would not work
> } as there is no directories /etc on Windows systems.  :-/
> 
> There is, however, a mkdir command ...
> 
> On Sep 15,  1:53am, 'Sven Guckes' wrote:
> } Subject: Re: zsh for win32 - installation of zshrc
> }
> } And I always thought that the value of a variable on the DOS shell
> } is "%var%" and not "$var".  or has this changed with WindowsNT?
> 
> It's a property of the shell (or rather, of command.com) not of the OS.
> So yes, if you were running a DOS batch file, you would use %var%.
> In zsh scripts, however, it's zsh that interprets the syntax, just as
> it does on unix, so you use $var.
> 
> } The value of a variable on Windows cannot be used as $VAR (I think)
> } but needs to be specified as %VAR% - and this is only possible in batch
> } files.  Right or wrong?
> 
> Mostly wrong.
> 
> If what you want to do is set the variables for all Windows apps, e.g.
> via the Environment tab in the System control panel, then you use %var%.
> If you're putting the variables in a zsh startup file, you use $var.
> 
> On Sep 14,  5:52pm, Amol Deshpande wrote:
> } Subject: RE: zsh for win32 - installation of zshrc
> }
> } Remember that these rules apply only if don't set HOME. Since there is
> } no /etc,  only the rules for locating files from $HOME are followed.
> 
> I don't have windows running at home, but yesterday I installed zsh.exe
> on an NT machine at work.  I created a d:\etc (d: being the boot drive on
> that machine) and put a zshenv file in it, and lo, zsh reads it.  So now
> the setting of TERM=vt100 and adding the gnu-win32 bin to the path and so
> on is in d:\etc\zshenv, and every user on that NT box gets it if they
> start zsh.  (I also put in HOME=$HOMEDRIVE$HOMEPATH; what was the reason
> for not defaulting $HOME from this on NT 4+ ?)
> 
> -- 
> Bart Schaefer                                 Brass Lantern Enterprises
> http://www.well.com/user/barts              http://www.brasslantern.com
>