From: Drew Adams <drew.adams@oracle.com>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 15234@debbugs.gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: bug#15234: 24.3.50; Make C-x u repeatable
Date: Tue, 3 Sep 2013 07:49:19 -0700 (PDT) [thread overview]
Message-ID: <007fd28d-d1ee-432b-a9e0-6adef59c0317@default> (raw)
In-Reply-To: <CAH8Pv0g8EqhxixJabnDzmfmGyh=B-4n--EoopWWYZXYxwRq0qA@mail.gmail.com>
> > FWIW, I've always used `C-_' or `C-/'. But I still think it makes sense
> > to make `C-x u' repeatable. I haven't seen an argument to the contrary
> > (but if I do I might change my mind).
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12572#8
[The argument there is that if `C-x u u u...' repeats `undo' then typing
`u' directly after that will not insert a `u' character.]
Fair enough. And thank you - it's always good to see real arguments for
and against a proposal.
It's a good argument. Not a particularly strong one, IMO, but reasonable.
It's not strong because there are other, simple ways of exiting `undo' so
`u' will then insert (`<left> <right>', `x DEL', whatever).
This is similar to arguments against binding keys in `isearch-mode-map'
to do things in Isearch because it stops them from ending Isearch.
Yes, some people might want to use `C-x u' for `undo' AND want `C-x u u'
to insert `u'. My vote would still be for making `C-x u u' repeatable.
You can't please everyone, unless you add an option or you have two
different commands (or you abuse some prefix-arg combination, and that's
already pretty overloaded).
To accommodate that argument, I would also vote for binding `C-x u' to a
new command, `undo-repeat', as mentioned earlier. (Or perhaps just reuse
the previously used name for `C-x u': `advertised-undo'.)
Anyone wanting to have `u' to insert directly after `C-x u' could easily
opt out in that case, by changing the key binding to the original,
non-repeatable `undo'.
Or if you want to be conservative here, make binding `C-x u' to
`undo-repeat'/`advertised-undo' opt-in instead of opt-out. I'd vote for
that too.
Bottom line: we should provide a repeatable undo command for `C-x u',
whether bound by default (preferable) or not (ok).
next prev parent reply other threads:[~2013-09-03 14:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-01 12:21 bug#15234: 24.3.50; Make C-x u repeatable Jambunathan K
2013-09-01 15:23 ` Drew Adams
2013-09-01 16:11 ` Jambunathan K
2013-09-01 16:27 ` Juri Linkov
2013-09-01 16:45 ` Jambunathan K
2013-09-03 1:46 ` Stefan Monnier
2013-09-03 2:15 ` Drew Adams
2013-09-03 2:23 ` Jambunathan K
2013-09-03 2:27 ` Drew Adams
2013-09-03 6:32 ` Dani Moncayo
2013-09-03 14:49 ` Drew Adams [this message]
2013-09-03 15:31 ` Dani Moncayo
2013-09-03 16:19 ` Drew Adams
2013-09-03 16:41 ` Dani Moncayo
2013-09-03 20:58 ` Jambunathan K
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=007fd28d-d1ee-432b-a9e0-6adef59c0317@default \
--to=drew.adams@oracle.com \
--cc=15234@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--cc=kjambunathan@gmail.com \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).