From: bas@phys.uva.nl (Bas V. de Bakker)
To: mpt95aes@pt.hk-r.se
Cc: zsh-users@math.gatech.edu
Subject: Re: Problems with arrow-up, ^P and so on.
Date: Fri, 2 Feb 1996 16:52:35 +0100 [thread overview]
Message-ID: <199602021552.AA15270@phys.uva.nl> (raw)
In-Reply-To: Andrew Eskilsson's message of Fri, 2 Feb 1996 15:31:22 +0100
Andrew Eskilsson <mpt95aes@pt.hk-r.se> writes:
> Suddenly zsh started to have problems with history-editing,
> sometimes it works, sometimes I have problems like:
Hmm, the symptoms sound a lot like you've gotten into vi editing mode,
while being used to emacs mode. Have you perhaps changed your EDITOR
or VISUAL variable to vi? Perhaps you should try putting a
"bindkey -e" in your .zshrc.
Hope this helps.
Bas.
next prev parent reply other threads:[~1996-02-02 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-02 14:31 Andrew Eskilsson
1996-02-02 15:52 ` Bas V. de Bakker [this message]
1996-02-02 16:22 ` Solved " Andy Eskilsson
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=199602021552.AA15270@phys.uva.nl \
--to=bas@phys.uva.nl \
--cc=mpt95aes@pt.hk-r.se \
--cc=zsh-users@math.gatech.edu \
/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).