From: "Bart Schaefer" <schaefer@brasslantern.com>
To: "Larry P . Schrof" <schrof@cig.mot.com>,
"Trinh, Timothy" <timothy.trinh@attws.com>
Cc: "'zsh-users@math.gatech.edu'" <zsh-users@math.gatech.edu>
Subject: Re: Problem running zsh on WinNT 4.0
Date: Fri, 12 Feb 1999 09:01:14 -0800 [thread overview]
Message-ID: <990212090115.ZM8419@candle.brasslantern.com> (raw)
In-Reply-To: <199902121550.KAA08438@po_box.cig.mot.com>
On Feb 12, 9:49am, Larry P . Schrof wrote:
} Subject: Re: Problem running zsh on WinNT 4.0
}
} I believe that should be called .zprofile instead of profile.zsh if you
} want it automatically read at zsh startup.
This part is correct.
} If the RCS option is unset, however, somewhere in /etc/zshenv, then the
} file WON'T be read, even if it is named correctly. (I'll be honest,
} I haven't looked at zsh on NT - functionality could be different
} as far as what startup files are read.)
Assuming you're using Amol Deshpande's zsh port, it will indeed read the
files \etc\zshenv, \etc\zshrc, etc. if you create a \etc directory on your
default drive (e.g. C:\etc).
It also reads $HOME\.zshenv, $HOME\.zshrc, etc., where HOME has to be set
in the environment by using the NT user account manager (use the option to
assign the user a home directory, don't just add HOME to the environment).
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-02-12 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-12 1:55 Trinh, Timothy
1999-02-12 15:49 ` Larry P . Schrof
1999-02-12 17:01 ` Bart Schaefer [this message]
1999-02-12 19:23 Trinh, Timothy
1999-02-12 19:40 ` Larry P . Schrof
1999-02-12 20:53 Trinh, Timothy
1999-02-12 20:54 Amol Deshpande
1999-02-13 0:49 Trinh, Timothy
1999-02-13 7:24 ` Bart Schaefer
1999-02-15 13:37 ` Chavdar Ivanov
1999-02-16 0:40 Amol Deshpande
1999-02-20 0:40 Trinh, Timothy
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=990212090115.ZM8419@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=schrof@cig.mot.com \
--cc=timothy.trinh@attws.com \
--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).