zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: zle: vi mode: wrong undo handling on fresh lines
Date: Tue, 28 Jan 2014 16:47:08 +0000	[thread overview]
Message-ID: <20140128164708.0c7facb6@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <140128082834.ZM21167@torch.brasslantern.com>

On Tue, 28 Jan 2014 08:28:34 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Jan 28,  2:58pm, Peter Stephenson wrote:
> }
> } > I think this is starting to get somewhere, but I suspect it needs
> } > tweaking.  For example, should that synthesised 'i' really be an 'a'?
> } 
> } Well, I think I'm going to commit it with the "a" because (i) this
> } definitely seems better than what was there before in any case and (ii)
> } hitting "ESC" and "." after typing the start of the line, which is my
> } naive way of getting it to repeat, does repeat what I just inserted
> } because of vi's quirk of backing up a character when leaving insert
> } mode.  Obviously I'm not claiming this is the end of the matter.
> 
> Sorry, I missed this when looking at your previous message.  I agree
> that "a" is more correct than "i" here.  In fact "A" might even be a
> reasonable choice.

Except, of course, if someone has redefined "a" / "A" in vicmd to the
widget delete-all-my-files-and-self-detonate.  Like the viins / vicmd
repeat thing you commented on, this is fundamental to the limitations of
the vi change buffer.  A partial fix might be to use tokens (and so
tokenise & metafy the vi change buffer), but I think this can of worms
is somewhat larger than that.

pws


  reply	other threads:[~2014-01-28 16:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-22 12:37 Hauke Petersen
2013-09-22 18:24 ` Bart Schaefer
2013-09-22 20:27   ` Hauke Petersen
2013-09-23  4:57     ` Bart Schaefer
2013-09-23 20:30 ` Peter Stephenson
2014-01-24 23:19   ` Oliver Kiddle
2014-01-25 19:15     ` Bart Schaefer
2014-01-27 12:43       ` Peter Stephenson
2014-01-27 16:11         ` Peter Stephenson
2014-01-28 14:58           ` Peter Stephenson
2014-01-28 16:28             ` Bart Schaefer
2014-01-28 16:47               ` Peter Stephenson [this message]
2014-01-28 17:41                 ` Bart Schaefer
2014-01-28 23:00           ` Oliver Kiddle
2014-01-29  2:59             ` Bart Schaefer
2014-01-29 10:50               ` Oliver Kiddle
2014-01-29 14:48                 ` Bart Schaefer
2014-01-30 14:51             ` Jun T.
2014-01-30 15:38               ` Peter Stephenson
2014-01-30 16:03                 ` Bart Schaefer
2014-01-31 12:00               ` Jun T.
2014-01-31 15:19                 ` Bart Schaefer
2014-01-31 15:33                   ` Peter Stephenson
     [not found]               ` <16181.1391175951@thecus.kiddle.eu>
2014-01-31 16:43                 ` Jun T.
2014-01-31 21:37               ` Oliver Kiddle
2014-01-31 22:32                 ` Oliver Kiddle
2014-02-01 19:27                   ` Bart Schaefer
2014-02-03 16:20                   ` Jun T.
2014-02-03 21:29                     ` Oliver Kiddle
2014-02-03 22:20                       ` Bart Schaefer
2014-02-03 23:26                         ` Oliver Kiddle
2014-02-04 17:11                           ` Jun T.
2014-02-05 22:00                             ` Oliver Kiddle
2014-02-02 22:10             ` Oliver Kiddle
2014-02-07 14:43             ` Oliver Kiddle
2014-02-07 16:22               ` Bart Schaefer
2014-01-27 16:29         ` Bart Schaefer

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=20140128164708.0c7facb6@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.org \
    /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).