From: Michael Schaap <cygwin@mscha.com>
To: <zsh-users@sunsite.dk>
Subject: Re: ehh... zsh: correct 'cvs' to '_cvs' [nyae]? n
Date: Thu, 12 Jul 2001 13:03:40 +0200 [thread overview]
Message-ID: <5.1.0.14.2.20010712125607.0371ca50@imap.local.mscha.com> (raw)
In-Reply-To: <Pine.SV4.4.33.0107120935080.11121-100000@itsrm2.mow.siemen s.ru>
At 07:37 12-7-2001, Andrej Borsenkow wrote:
>On Thu, 12 Jul 2001, Michael Schaap wrote:
>
> > (The problem is that zsh doesn't find "/bin/cvs", but
> > "/bin/cvs.exe". Therefore, it tries to correct "cvs" to the closest it can
> > find, which is the autoloaded "_cvs" function.)
> >
>
>So, once again - should we stop hashing foo.exe (i.e. hash just foo)?
>Currently foo.exe is not visible anyway so I cannot see what difference
>would it have.
I don't think we should. If we would, running
% ls.exe
would no longer work. (Bad example - nobody would try this for ls, they
might for other (Windows) executables. For instance, I could imagine
typing "cmd.exe".)
The way things are done now seem to be the same as for Bash (which is,
after all, the Official Cygwin Shell). Also in Bash, ls<TAB> is completed
to both "ls" and "ls.exe", and /bin/ls<TAB> is only completed to "/bin/ls.exe".
I think this is the best we can do, without hacking the completion system
itself.
>The problem is, of course, =cmd won't be the same as /path/to/cmd.exe. But
>it the same with my patch as well.
I don't see why that would be a problem.
- Michael
prev parent reply other threads:[~2001-07-12 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 11:30 Andrew Markebo
2001-07-11 17:15 ` Bart Schaefer
2001-07-11 19:20 ` Andrew Markebo
2001-07-11 22:19 ` Michael Schaap
2001-07-12 5:37 ` Andrej Borsenkow
[not found] ` <Pine.SV4.4.33.0107120935080.11121-100000@itsrm2.mow.siemen s.ru>
2001-07-12 11:03 ` Michael Schaap [this message]
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=5.1.0.14.2.20010712125607.0371ca50@imap.local.mscha.com \
--to=cygwin@mscha.com \
--cc=zsh-users@sunsite.dk \
/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).