unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Undo boundary
Date: Wed, 08 Dec 2004 16:22:48 +0200	[thread overview]
Message-ID: <87sm6g7tty.fsf_-_@jurta.org> (raw)
In-Reply-To: <jwv1xe153qn.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 08 Dec 2004 08:17:34 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> It would be nice if the undo history would recognize that:
>>   "any char" 
>>     followed by 
>>   m-x delete-backward-char
>
>> Is functionally the same as.
>
>>   "any char"
>>     followed by
>>   m-x undo
>
>> I admit it's easier said than done.
>
> What would be the benefit?
> I.e. in which cases would it make a diference?

It seems OP refers to the fact that `command_loop_1' has the built-in
constant value 20 for undo-boundary of self-inserting characters.

It makes sense to make it configurable.  Often `undo' undoes too much
characters than needed.  To get them back, the user has to break the
undo chain, redo undoing of the last 20 characters, and to start
to delete the needed amount of characters with delete-backward-char.

This is too inconvenient and also breaks the undo history unnecessarily.
Users with high keyboard repeat rate would prefer to change this value
to 1, press C-_ key, and hold it while `undo' undoes characters one
at a time.

However, this is useful only for the last inserted characters.
It would be a nuisance to undo characters one at a time for earlier
character insertions.  For them even the value 20 is too small.
It is desirable to undo whole blocks of earlier character insertions,
not in chunks of 20 characters.

-- 
Juri Linkov
http://www.jurta.org/emacs/

      parent reply	other threads:[~2004-12-08 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08  6:49 (no subject) Han Boetes
2004-12-08 13:17 ` Stefan Monnier
2004-12-08 13:31   ` Han Boetes
2004-12-08 14:22   ` Juri Linkov [this message]

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=87sm6g7tty.fsf_-_@jurta.org \
    --to=juri@jurta.org \
    --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).