zsh-users
 help / color / mirror / code / Atom feed
From: "'Sven Guckes'" <guckes@math.fu-berlin.de>
To: ZShell Users List <zsh-users@math.gatech.edu>
Cc: amol@blarg.net
Subject: Re: zsh for win32 - installation of zshrc
Date: Mon, 14 Sep 1998 19:55:52 +0200	[thread overview]
Message-ID: <19980914195552.C22353@math.fu-berlin.de> (raw)
In-Reply-To: <980911235322.ZM1397@candle.brasslantern.com>; from Bart Schaefer on Fri, Sep 11, 1998 at 11:53:22PM -0700

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.  :-/

> So of course c:\zshrc isn't going to work; it's looking for .zshrc
> (which prehaps you can't create on a Win95 machine because of the
> silly 8.3 filename rule, though I'm pretty sure you can on NT).

Well, how could I be sure?  Actually, I find that using "zshrc" would
be a nice workaround because of the "8.3" filename convention.

> So you either need to create a c:\etc\zshrc (and zlogin and zshenv
> and zlogout if you want) or find out what zsh thinks $HOME is set to
> (by starting zsh and typing "echo $HOME")
> and put files with names starting with a "." in there, if you can.

I'd rather look into a manual explaining this.  (hint hint ;-)

> It appears, from further perusal of the strings output, that $HOMEDRIVE
> and $HOMEPATH are used to generate part of the default $Path,
> as is a variable $ZSHROOT that isn't used in unix zsh.

I understand that the following "filenames" should work then:

        %HOMEDRIVE%%HOMEPATH%/.zshrc
        %HOME%/.zshrc
        %ZDOTDIR%/.zshrc

Now, which order do these take?  Amol?

A rough summary of this can be read on
http://www.math.fu-berlin.de/~guckes/zsh/windows.html

Sven


  reply	other threads:[~1998-09-14 18:02 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' [this message]
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
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=19980914195552.C22353@math.fu-berlin.de \
    --to=guckes@math.fu-berlin.de \
    --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).