From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21799 invoked from network); 27 Feb 2002 16:08:28 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 27 Feb 2002 16:08:28 -0000 Received: (qmail 858 invoked by alias); 27 Feb 2002 16:08:10 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 4710 Received: (qmail 844 invoked from network); 27 Feb 2002 16:08:09 -0000 Message-ID: <20020227160806.77968.qmail@web9304.mail.yahoo.com> Date: Wed, 27 Feb 2002 16:08:06 +0000 (GMT) From: =?iso-8859-1?q?Oliver=20Kiddle?= Subject: Re: up-line-or-search question To: dominik.vogt@gmx.de, zsh-users@sunsite.auc.dk In-Reply-To: <20020227143627.F5514@lifebits.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit --- Dominik Vogt wrote: > > Actually, that does not do what I want. I'd need > > up-line-or-history-beginning-search-backward > up-line-or-history-beginning-search-forward > > Since I still want to be able to navigate through the lines in the > ZLE. Is this closer to what you want: up-line-or-beginning-search-backward() { if [[ $LBUFFER == *$'\n'* ]]; then zle up-line-or-history else zle history-beginning-search-backward fi } zle -N up-line-or-beginning-search-backward If it is, this was discussed some time around about last November. A few variations on the idea were posted including a similar function for forward. Oliver __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com