zsh-users
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: ZShell Users List <zsh-users@math.gatech.edu>
Cc: amol@blarg.net
Subject: Re: zsh for win32 - installation of zshrc
Date: Tue, 15 Sep 1998 10:18:23 -0700	[thread overview]
Message-ID: <980915101824.ZM2951@candle.brasslantern.com> (raw)
In-Reply-To: <AF4C1F8C5306D111AD5F0000F8662ED3053088B6@RED-MSG-41>

On Sep 14,  7:55pm, 'Sven Guckes' wrote:
} Subject: Re: zsh for win32 - installation of zshrc
}
} Quoting Bart Schaefer (schaefer@brasslantern.com):
} > 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


  parent reply	other threads:[~1998-09-15 17:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c=GB%a=_%p=Saudi_Internatio%l=SMS01-980911172557Z-1926@sms01.saudibank.com>
1998-09-12  5:43 ` 'Sven Guckes'
1998-09-12  6:53   ` Bart Schaefer
1998-09-14 17:55     ` 'Sven Guckes'
1998-09-14 20:59       ` Amol Deshpande
1998-09-14 18:40         ` Amol Deshpande
1998-09-14 19:54           ` Bart Schaefer
1998-09-14 23:53           ` 'Sven Guckes'
1998-09-15  0:52             ` Amol Deshpande
1998-09-15  2:19               ` 'Sven Guckes'
1998-09-15  6:31                 ` Amol Deshpande
1998-09-15 12:52                   ` David N. Blank-Edelman
1998-09-15 17:08                     ` Stephen Marley
1998-09-16 12:20                       ` Hannu Koivisto
1998-09-16 13:26                         ` Stephen Marley
1998-09-17 10:48                           ` Hannu Koivisto
1998-09-16 15:32                         ` Bart Schaefer
1998-09-15 17:18                   ` Bart Schaefer [this message]
1998-09-16 23:08 Amol Deshpande
  -- strict thread matches above, loose matches on Subject: below --
1998-09-15 21:56 Amol Deshpande
1998-09-16  0:55 ` Bart Schaefer
1998-09-15 18:04 Amol Deshpande
1998-09-15 18:00 Amol Deshpande
1998-09-15 20:59 ` Bart Schaefer
1998-09-15 21:40 ` Bart Schaefer
1998-09-11 18:27 Amol Deshpande
1998-09-11 16:41 Sven Guckes
1998-09-11 17:13 ` Stephen Rondeau
1998-09-11 20:11 ` ric hotchkiss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=980915101824.ZM2951@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=amol@blarg.net \
    --cc=zsh-users@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).