From: Norbert Zeh <nzeh@cs.dal.ca>
To: zsh-users@zsh.org
Subject: Re: Path does not update until I logout/log in
Date: Tue, 04 Dec 2012 11:35:04 -0400 [thread overview]
Message-ID: <50BE1828.4060302@cs.dal.ca> (raw)
In-Reply-To: <1354631592.83211.YahooMailNeo@web140005.mail.bf1.yahoo.com>
On 12-12-04 10:33 AM, John wrote:
> If I install a new executable via my package manager, zsh doesn't allow me to see it via auto-completion until I either source my ~/.zshrc again. Is there a setting that would control this? Note that under bash, I don't need to tweak anything to get this behavior.
>
> Here is another tangible example:
>
> 1) Open two xterms
> 2) In one xterm do this: sudo ln -s /usr/bin/top /usr/bin/newsymlink
>
> Now, if in the 2nd xterm I start typing, nothing happens for autocomplete: newsy<TAB>
>
> Here is my config file:
>
> $ cat ~/.zshrc
> ZSH=$HOME/.zsh
>
> for config_file ($ZSH/lib/*.zsh) source $config_file
>
>
> for i in aliases commonrc functions zsh ; do [[ -f $HOME/.$i ]] && . $HOME/.$i ; done
>
>
> PROMPT='%(!.%{$fg_bold[red]%}.%{$fg_bold[white]%}%n@)%m %{$fg_bold[blue]%}%(!.%1~.%~) %#%{$reset_color%} '
>
>
> REPORTTIME=5
>
> autoload -U compinit
>
> compinit -i
zsh uses a hash table to store the list of known commands. When you
install a new command in your path, you need to update this hashtable by
invoking "rehash". This is similar to csh, I believe (been a while
since I used this last). bash, on the other hand, does a search for
valid commands every single time. zsh provides this possibility, too,
by setting the "rehash" option, but this is disabled by default because
it incurs a speed penalty.
Cheers,
Norbert
next prev parent reply other threads:[~2012-12-04 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 14:33 John
2012-12-04 15:35 ` Norbert Zeh [this message]
2012-12-04 16:25 ` Bart Schaefer
2012-12-04 15:38 ` Guillaume Brunerie
[not found] ` <20121204153753.GG19774@Hailey>
2012-12-04 18:27 ` John
2012-12-04 20:10 ` Bart Schaefer
2012-12-05 0:37 ` John
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=50BE1828.4060302@cs.dal.ca \
--to=nzeh@cs.dal.ca \
--cc=zsh-users@zsh.org \
/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).