From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: can undo unamalgamation be turned off reliably and completely?
Date: Mon, 30 Nov 2020 17:42:42 +0100 [thread overview]
Message-ID: <87r1oahk3h.fsf@web.de> (raw)
In-Reply-To: jwvlfejwj3b.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > If you set this variable to, say, t, that should turn off this feature.
> > Should exist in 25. May be named "undo-auto--current-boundary-timer"
> > there.
>
> No, this part of undo was all hard coded in C in Emacs-25.
I see the timer variable being introduced in Lisp with this commit:
| 44dfa86b7d382b84564d68472da1448d08f48129
| Author: Phillip Lord <phillip.lord@newcastle.ac.uk>
| AuthorDate: Thu Aug 6 21:33:58 2015 +0100
| Commit: Phillip Lord <phillip.lord@russet.org.uk>
| CommitDate: Thu Nov 12 21:06:05 2015 +0000
|
| Parent: 0aec2aaccd * lisp/emacs-lisp/package.el: Simplify describe-package-1
| Contained: emacs-25 emacs-26 master
| Follows: emacs-24.5-rc3-fixed (5481)
| Precedes: emacs-25.0.90 (1955)
|
| The heuristic that Emacs uses to add an `undo-boundary' has been
| reworked, as it interacts poorly with functions on `post-command-hook'
| or `after-change-functions'.
Am I interpreting the "Contained" and "Precedes" fields wrong?
> It got rewritten in Elisp for Emacs-26, which indeed makes it possible to
> change it much more easily.
How would you deactivate it in versions not yet having the rewrite?
Thanks,
Michael.
next prev parent reply other threads:[~2020-11-30 16:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 5:20 can undo unamalgamation be turned off reliably and completely? Samuel Wales
2020-11-29 8:57 ` Óscar Fuentes
2020-11-29 20:01 ` Michael Heerdegen
2020-11-30 1:59 ` Samuel Wales
2020-11-30 3:08 ` Michael Heerdegen
2020-11-30 4:44 ` Stefan Monnier
2020-11-30 16:42 ` Michael Heerdegen [this message]
2020-12-02 4:51 ` Samuel Wales
2020-12-02 4:52 ` Samuel Wales
2020-12-03 3:42 ` Samuel Wales
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=87r1oahk3h.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@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.
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).