From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Andrew Markebo <flognat@flognat.myip.org>, zsh-users@sunsite.dk
Subject: Re: ehh... zsh: correct 'cvs' to '_cvs' [nyae]? n
Date: Wed, 11 Jul 2001 17:15:26 +0000 [thread overview]
Message-ID: <1010711171527.ZM30915@candle.brasslantern.com> (raw)
In-Reply-To: <m3bsmrog8j.fsf@localhost.localdomain>
On Jul 11, 1:30pm, Andrew Markebo wrote:
} Subject: ehh... zsh: correct 'cvs' to '_cvs' [nyae]? n
}
} Commandline correction.. which parameter have I now set wrong??
}
} aes@NOCTURN:Jul04<130> cvs --help-options
} zsh: correct 'cvs' to '_cvs' [nyae]? n
}
} aes@NOCTURN:Jul04<0> grep
} zsh: correct 'grep' to 'zgrep' [nyae]? n
My guess would be that you have *not* set one of either the HASH_CMDS
or HASH_DIRS setopts (or rather, that you have unsetopt'd them, as
they are on by default).
Does the above happen every time, or only the first time you use a
particular command, or sporadically?
The other possibility is that there are directories in your $PATH that
are automounted or some such, so that the command does not appear to
be available until zsh actually attempts to execute it.
Aside to zsh-workers: Regardless of the above, this really shouldn't
happen. I'd hate to suggest special-casing a leading underscore in the
correction code. Other possibilities?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-07-11 17:17 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 [this message]
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
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=1010711171527.ZM30915@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=flognat@flognat.myip.org \
--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).