zsh-users
 help / color / mirror / code / Atom feed
From: "Kingsley G. Morse Jr." <change@nas.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@sunsite.dk
Subject: Re: Configuring zsh to leave keys in command mode after a vi "/" search
Date: Sat, 4 May 2002 18:42:27 -0700	[thread overview]
Message-ID: <20020504184227.A12725@debian1.loaner.com> (raw)
In-Reply-To: <1020504203443.ZM4671@candle.brasslantern.com>; from schaefer@brasslantern.com on Sat, May 04, 2002 at 08:34:43PM +0000

Bart,

Thanks for checking.

On Sat:20:34, Bart Schaefer wrote:
> On May 3, 10:26pm, Kingsley G. Morse Jr. wrote:
> } 
> }         $ <esc>/more<cr>
> }         ?more_
> }         $ more /etc/hosts
> } 
> } When I press "n" to find the next match ...
> } 
> }         $ more /etc/hostsn
> } 
> } Oops! zsh was in vi's *insert* mode, interpreted the "n" literally and
> } appended it to the end of the command!
> 
> I'm not able to reproduce this at all.  Zsh always stays in command mode
> for me after ending a search.

Interesting...

> What version are you running,

        $ zsh --version
        zsh 4.0.4 (i686-pc-linux-gnu)
        
> and what options do you have set?

        $ setopt
        autocd
        noautoparamslash
        autopushd
        autoresume
        nobgnice
        cdablevars
        noclobber
        correct
        correctall
        extendedglob
        globdots
        histignoredups
        interactive
        longlistjobs
        mailwarning
        monitor
        pushdminus
        pushdsilent
        pushdtohome
        rcquotes
        recexact
        shinstdin
        zle

Thanks,
Kingsley


      reply	other threads:[~2002-05-05  1:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04  5:26 Kingsley G. Morse Jr.
2002-05-04 20:34 ` Bart Schaefer
2002-05-05  1:42   ` Kingsley G. Morse Jr. [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020504184227.A12725@debian1.loaner.com \
    --to=change@nas.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).