From: "Trinh, Timothy" <timothy.trinh@attws.com>
To: "'jr@scms.rgu.ac.uk'" <jr@scms.rgu.ac.uk>
Cc: "'zsh-users@math.gatech.edu'" <zsh-users@math.gatech.edu>,
"'Bart Schaefer'" <schaefer@brasslantern.com>,
"Larry P . Schrof" <schrof@cig.mot.com>
Subject: RE: Problem running zsh on WinNT 4.0
Date: Fri, 12 Feb 1999 11:23:54 -0800 [thread overview]
Message-ID: <3AABFE76426DD211AC3000805FFE11768A712E@hq-msg04.nwest.mccaw.com> (raw)
When I set my window's HOME environment variable to %HOMEDRIVE%HOMEPATH,
this allowed the zsh program to
automatically source in my .zshrc (located in HOME), but not my profile
file(also located in HOME). I tried renaming the profile file to .zprofile,
.profile, and profile.zsh, but it still did not source in my profile file.
As a workaround, I placed the following line in my .zshrc file to source in
the profile file:
source $HOMEDRIVE$HOMEPATH/<profile file name>
If there is a better way of than what I have done, let me know.
One other thing, whenever I export a variable to a path which contain the
windows environment variable that contain backslashes,
this messes up the variable. Here is an example of what I mean:
export MY_OUTPUT_DIR="$HOMEDRIVE$HOMEPATH/output" (I have something like
this in my profile file)
The window's environment variable $HOMEDRIVE returns e: and $HOMEPATH
returns \job\timothy
When you echo MY_OUTPUT_DIR, you get a broken path of some sort. The broken
path is probably caused by the backslashes.
If you cd MY_OUTPUT_DIR, you get a error message which states: "cd: no such
file or directory: e:\job\timothy/output"
What do I need to do to have the zsh program interpret those backslashes as
forward slashes?
I have read the readme file that comes along with the zsh application
regarding the problem above and this is what it says:
NT-specific setopts:
------------------
* winntignorecase: ignore case in completions
* winntlamepathfix: convert the PATH environment variable back to
'\'-delimited instead of '/'-delimited when each child process is
forked.
* winntnoassociations: Do not try applications associated with extensions
if exec() fails.
* winntconvertbackslash: Convert backslashes to '/' when comparing named
directories etc. May be useful if you derive HOME from '\'-delimited
environment variables
It was nice to know this stuff, but it does not say anything about how to
implement it.
I am not sure what NT-specific setopts are and what and where I can deal
with them.
Any help is greatly appreciated and thanks for all the help you have given
me thus far.
Thanks again,
Timothy
----------
From: jr@scms.rgu.ac.uk[SMTP:jr@scms.rgu.ac.uk]
Sent: Friday, February 12, 1999 1:03 AM
To: timothy.trinh@mccaw.com
Subject: Re: Problem running zsh on WinNT 4.0
>I have just recently installed the zsh program on my WinNT 4.0. It
runs
>just fine, but each time it starts up, it does not source my
profile file.
>I always have to source in the my profile manaually(.
./profile.zsh). Is
>there some way were I have my profile sourced in when I start the
program?
I believe you have to have HOME set before zsh can find your
.profile file.
Check the FAQ, there should be some info there.
--
John Riddoch Email: jr@scms.rgu.ac.uk Telephone:
(01224)262730
Room C4, School of Computer and Mathematical Science
Robert Gordon University, Aberdeen, AB25 1HG
I am Homer of Borg. Resistance is Fu... Ooooh! Donuts!
next reply other threads:[~1999-02-12 19:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-12 19:23 Trinh, Timothy [this message]
1999-02-12 19:40 ` Larry P . Schrof
-- strict thread matches above, loose matches on Subject: below --
1999-02-20 0:40 Trinh, Timothy
1999-02-16 0:40 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-12 20:54 Amol Deshpande
1999-02-12 20:53 Trinh, Timothy
1999-02-12 1:55 Trinh, Timothy
1999-02-12 15:49 ` Larry P . Schrof
1999-02-12 17:01 ` Bart Schaefer
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=3AABFE76426DD211AC3000805FFE11768A712E@hq-msg04.nwest.mccaw.com \
--to=timothy.trinh@attws.com \
--cc=jr@scms.rgu.ac.uk \
--cc=schaefer@brasslantern.com \
--cc=schrof@cig.mot.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).