From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: jarausch@igpm.rwth-aachen.de
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: Make zsh a tiny bit cleverer?
Date: Fri, 28 Apr 2000 16:39:56 +0000 [thread overview]
Message-ID: <1000428163957.ZM24956@candle.brasslantern.com> (raw)
In-Reply-To: <200004281539.RAA11660@numa1.igpm.rwth-aachen.de>
On Apr 28, 5:38pm, jarausch@igpm.rwth-aachen.de wrote:
} Subject: Re: Make zsh a tiny bit cleverer?
}
} On 28 Apr, Bart Schaefer wrote:
} > On Apr 28, 3:44pm, jarausch@igpm.rwth-aachen.de wrote:
} > } Subject: Make zsh a tiny bit cleverer?
} > }
} > } ABC
} > }
} > } zsh doesn't find it (that's OK, it's not yet hashed) and
} > } suggests
} > } correct 'ABCD' to 'ABC'
} > }
} > } If I say 'no' it finds and executes 'ABCD' but doesn't
} > } remember that there is an 'ABCD', indeed.
} >
} > This should have been fixed last October, at least in the 3.1.x series.
}
} What am I missing
You're not, I am.
The patches I mentioned are for a similar problem where there is a non-
executable `ABCD' earlier in the search path than an executable `ABCD',
which was causing the intended `ABCD' never to be found. The symptom
was the same (zsh would offer to correct `ABCD').
So the real answer is that you need to turn off the HASH_DIRS option.
When HASH_DIRS is on, zsh doesn't re-search for new commands until after
it has already forked, so it can't remember it.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next parent reply other threads:[~2000-04-28 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200004281539.RAA11660@numa1.igpm.rwth-aachen.de>
2000-04-28 16:39 ` Bart Schaefer [this message]
2000-04-28 13:44 jarausch
2000-04-28 15:36 ` 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=1000428163957.ZM24956@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=jarausch@igpm.rwth-aachen.de \
--cc=zsh-workers@sunsite.auc.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).