From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5857 invoked from network); 7 Jan 2002 12:54:29 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 7 Jan 2002 12:54:29 -0000 Received: (qmail 1145 invoked by alias); 7 Jan 2002 12:54:06 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 4568 Received: (qmail 1134 invoked from network); 7 Jan 2002 12:54:05 -0000 To: "Bart Schaefer" Cc: zsh-users@sunsite.dk Subject: Re: zsh: correct 'sudo' to '_sudo' [nyae]? References: <87ofkvlh37.fsf@lynx.ionific.com> <1020106030307.ZM7583@candle.brasslantern.com> Mail-copies-to: nobody From: Hannu Koivisto Date: Mon, 07 Jan 2002 14:54:01 +0200 In-Reply-To: <1020106030307.ZM7583@candle.brasslantern.com> ("Bart Schaefer"'s message of "Sun, 6 Jan 2002 03:03:07 +0000") Message-ID: <87itaecoeu.fsf@lynx.ionific.com> User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: Hannu Koivisto "Bart Schaefer" writes: > On Dec 19, 11:00am, Hannu Koivisto wrote: >} >} I always get this message when I start a new shell (whether by >} logging to a system or by saying "zsh" when I'm logged on) and try >} to run sudo even though sudo is in path. rehash doesn't help, but >} "which sudo" always fixes the problem. What could be the culprit? > > It's not surprising that "rehash" doesn't help, as all that does is > empty the command hash table, and correction treats the contents of the > command hash table as the correct spellings. Ok, I tried it just because it has helped for the same problem when I have installed new software. > Does "rehash -f" (both empty the command hash and refill it again) help? No. > Do you use the HASH_LIST_ALL option? Unless that option is set, the > command hash table does not automatically fill itself during correction. I don't use it but I tried setting it and it changed nothing. -- Hannu