From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17170 invoked from network); 4 Jan 1997 23:40:17 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by coral.primenet.com.au with SMTP; 4 Jan 1997 23:40:16 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id SAA09818; Sat, 4 Jan 1997 18:46:43 -0500 (EST) Resent-Date: Sat, 4 Jan 1997 18:46:43 -0500 (EST) From: Zefram Message-Id: <9885.199701042347@stone.dcs.warwick.ac.uk> Subject: Re: history search bug{,fix} To: wayne@clari.net (Wayne Davison) Date: Sat, 4 Jan 1997 23:47:38 +0000 (GMT) Cc: zefram@dcs.warwick.ac.uk, zsh-workers@math.gatech.edu In-Reply-To: <199701042334.PAA19601@bebop.clari.net> from "Wayne Davison" at Jan 4, 97 03:34:40 pm X-Loop: zefram@dcs.warwick.ac.uk X-Stardate: [-31]8679.95 X-US-Congress: Moronic fuckers Content-Type: text Resent-Message-ID: <"QQhrj1.0.LP2.Zlkpo"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2725 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu Wayne Davison wrote: >Unfortunately this changes the way searching works in some cases. >For instance, if you type an 's' and then use history-search-backward >it will find a command that starts with the letter 's' (as before). >However, if you type the command again it searches for a command >that matches the current command instead of continuing to look for >commands that start with the letter 's'. The only time the new >behavior matches the old is when the initial search is for a full >word (i.e. it was terminated by a space). That's odd. It looks like history-search-{for,back}ward only behaved as documented if the word ended in a space, otherwise acting like history-beginning-search-{for,back}ward. Wouldn't it be better to make them actually behave as documented -- only look for complete words matching the current one? -zefram