From: Thorsten Meinecke <kaefer@aglaia.aball.DE>
To: zsh-workers@math.gatech.edu
Subject: vi mode weird when editing previous history entries
Date: Tue, 19 Nov 1996 21:58:20 +0100 (MET) [thread overview]
Message-ID: <m0vPxFP-00008PC@aglaia.aball.DE> (raw)
This bug is around a little longer, I've seen it in zsh-3.0.0 too.
The effect of it is twofold (maybe there are two separate bugs in-
stead):
- it either zaps the current buffer (after movement commands) or
- it dumps core when attempting deletions with certain movements
commands.
To reproduce it, you'll need a none-empty history. Scroll up into
an old history entry, say with up-history (or other history key
commands -- `!' and expand-or-complete won't do), enter vi-cmd-mode
and do vi-set-mark, optionally followed by movements and then do
vi-goto-mark. Key order:
vi-cmd-mode ^[
up-history ^P
vi-set-mark ma
vi-goto-mark `a
The current buffer: is gone. Doesn't happen when editing a new
buffer freshly filled by typing or one filled by bang expansion.
Now try to vi-delete with vi-goto-mark as movement command. NOT!
There is at least one similar sequence that violates segmentation:
up-line-or-history ^[[A (bound to a cursor key)
vi-cmd-mode ^[
vi-delete d
end-of-buffer-or-history \M-x end-of-buffer-or-history
I don't think it's something system-specific. Regards,
--Thorsten
reply other threads:[~1996-11-19 21:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m0vPxFP-00008PC@aglaia.aball.DE \
--to=kaefer@aglaia.aball.de \
--cc=zsh-workers@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).