From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Emacs-diffs Digest, Vol 4, Issue 70
Date: 24 Mar 2003 13:41:26 +0100 [thread overview]
Message-ID: <5xhe9t2ayx.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <E18xHK6-0002Ib-00@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> + * simple.el (set-mark-command): Doc fixes.
> + Allow pop-global-mark to be repeated with C-x C-SPC C-SPC...
>
> I think that is a bad idea. Peculiar repetitions like this can
> be useful, but they also are prone to causing surprises.
> So we should implement them only when really really important.
> I don't think this one is important enough.
>
> Would you please take it out?
I added this to make it analogue to C-u C-SPC C-SPC ... (which I
find is a wast improvement over the old C-u C-SPC C-u C-SPC ...
method).
The only problem with the new behaviour is if the user wants to set
the mark immediately after C-x C-SPC (I'd think that is quite rare),
but that case is not different from the situation where you would want
to set the mark immediately after doing C-u C-SPC C-SPC ...
So I really don't see why this is a bad idea, as I (and others)
actually find the difference in behaviour rather confusing, and think
the new method C-x C-SPC C-SPC... is a wast improvement over the old
C-x C-SPC C-x C-SPC... like it is for C-u C-SPC ...
In any case, I have now reverted the patch, so the old behaviour is
now the default; however, the IMO improved behaviour can still be
selected with a new user option `pop-global-mark-quick-repeat'.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next parent reply other threads:[~2003-03-24 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18wWjN-00038Q-01@monty-python.gnu.org>
[not found] ` <E18xHK6-0002Ib-00@fencepost.gnu.org>
2003-03-24 12:41 ` Kim F. Storm [this message]
2003-03-26 2:42 ` Emacs-diffs Digest, Vol 4, Issue 70 Richard Stallman
2003-03-28 15:06 ` Kim F. Storm
2003-03-29 18:39 ` Richard Stallman
2003-03-31 22:48 ` Kim F. Storm
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=5xhe9t2ayx.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.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.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).