From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4502 invoked from network); 31 Jan 1997 19:32:21 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by coral.primenet.com.au with SMTP; 31 Jan 1997 19:32:21 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id OAA26505; Fri, 31 Jan 1997 14:11:49 -0500 (EST) Resent-Date: Fri, 31 Jan 1997 14:11:49 -0500 (EST) Message-Id: <199701311913.LAA19406@bebop.clari.net> To: Peter Stephenson Cc: zsh-workers@math.gatech.edu (Zsh hackers list) Subject: Re: history-search-backward In-reply-to: pws's message of Fri, 31 Jan 1997 11:47:08 +0100. <199701311047.LAA22677@hydra.ifh.de> Date: Fri, 31 Jan 1997 11:13:22 -0800 From: Wayne Davison Resent-Message-ID: <"uMHCv2.0.4U6.qFayo"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2861 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Peter Stephenson writes: > Looks like another incompatibility got in while I wasn't paying much > attention: ^[p will only search backwards on complete words. I don't think anyone objected except me, which I found surprising. I think the new method is less versatile. Sure it agrees with the man page, but it would have been just as easy to fix the manual. The old method allowed someone to choose between searching for a whole command and a sub-string by including a space or not. Yes, I know that history-beginning-search-backward lets you do this and more (I've had that bound to ^[p for a long time now since it works like bash's default ^[p command and I like that better), but it seems to me that the undocumented working of the default binding was more intuitive for those that didn't want the command arguments getting into the search. ..wayne..