From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3546 invoked from network); 26 Nov 1997 17:35:08 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 26 Nov 1997 17:35:08 -0000 Received: (from list@localhost) by math.gatech.edu (8.8.5/8.8.5) id MAA07731; Wed, 26 Nov 1997 12:17:53 -0500 (EST) Resent-Date: Wed, 26 Nov 1997 12:11:08 -0500 (EST) From: Christopher Croughton Message-Id: <97Nov26.191202gmt+0100.17029@internet01.amc.de> Subject: History key bindings To: zsh-users@math.gatech.edu Date: Wed, 26 Nov 1997 18:10:51 +0100 X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"8c9Op.0.Gs1.hW5Vq"@math> Resent-From: zsh-users@math.gatech.edu X-Mailing-List: archive/latest/1152 X-Loop: zsh-users@math.gatech.edu X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu I'm using zsh version 3.0.0, with the up and down cursor keys being bound (at the moment) to history-beginning-search-backward and history-beginning- search-forward. These almost do what I want (i.e. they match on the start of the line) except that they put the cursor at the start (or rather leave it where it is) rather than putting it at the end of the line. The equivalent tcsh functions (and 4DOS on MSDOS) match on wherever you are when you first start the search but put the cursor at the end. For instance, with history: vi fred chmod +x fred vi bill vi fred.c typing $vi f_ and searching backwards will find 'vi fred.c' and put the cursor at the end of the line, whereas under zsh it will put the cursor after 'f'. Is there some way to cause zsh to remember the buffer up to where it was when the search started and use that, while putting the cursor at the end still? From the documentation it seems that up until version 3 something like this was normal, and then the history-search-backward etc. was changed to only match on the first word. Apart from this one (annoying, to me) problem, zsh is wonderful. If this is fixed in the latest release or the beta version then I'll try that... Thanks, Chris C