From: Amol Deshpande <amold@MICROSOFT.com>
To: ZShell Users List <zsh-users@math.gatech.edu>,
"'Bart Schaefer'" <schaefer@brasslantern.com>
Subject: RE: zsh for win32 - installation of zshrc
Date: Tue, 15 Sep 1998 14:56:19 -0700 [thread overview]
Message-ID: <AF4C1F8C5306D111AD5F0000F8662ED3053088BD@RED-MSG-41> (raw)
> ----------
> From: Bart Schaefer[SMTP:schaefer@brasslantern.com]
> Sent: Tuesday, September 15, 1998 1:59 PM
> To: ZShell Users List
> Cc: amol@blarg.net
> Subject: Re: zsh for win32 - installation of zshrc
>
>
> "setopt correct" is worthless because it uses the full file name (e.g.
> "foo.exe") when trying to correct the spelling of a command ("foo") and
> therefore complains about nearly everything except builtins. (This is
> probably fixable by playing with hash/unhash commands.)
>
it's actually fixable by just renaming all your foo.exes to foo :-)
i thought it would be a waste of time for the shell to try all possible
extensions (.exe, .com, .bat, .cmd) for each command, so i didn't bother
to fix this.
> "setopt winnt_ignore_case winnt_lame_path_fix" seems to be a pretty good
> idea. I'm not sure exactly when "winnt_convert_backslash" is important.
>
you probaby need it in cases where you are deriving paths from other DOS
style paths.
For example, HOMDRIVE=F:, and HOMEPATH=\
so, if FOO=$HOMEDRIVE$HOMEPATH, then FOO is set
to F:\.
this will confuse the shell no end (all paths MUST be '/'-delimited)
if you set winntconvertbackslash, the theory is that the shell converts
'\' to '/' when matching paths.
in tcsh i could just do
set bar=$var:s#\\#/#:ah
to convert '\' to '/' before
assignment, but I was told there was no simple way in zsh to do the
same.
BTW, please don't cc amol@blarg.net. I am a member of this mailing list.
thanks,
-amol
next reply other threads:[~1998-09-15 22:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-15 21:56 Amol Deshpande [this message]
1998-09-16 0:55 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
1998-09-16 23:08 Amol Deshpande
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
[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
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=AF4C1F8C5306D111AD5F0000F8662ED3053088BD@RED-MSG-41 \
--to=amold@microsoft.com \
--cc=schaefer@brasslantern.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).