From: "Frédéric Giquel via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 60467@debbugs.gnu.org
Subject: bug#60467: New problem introduced
Date: Thu, 22 Jun 2023 21:28:44 +0200 [thread overview]
Message-ID: <7ccb0e8131f84ca2ea0f0c0aed11dc197b578a64.camel@laposte.net> (raw)
In-Reply-To: <87o7ri74qv.fsf@localhost>
Hi all,
I'm reopening this bug because the fix has introduced a new problem.
This can be highlighted with the following procedure (verified with
Emacs 29.0.92) :
1. Open a file: emacs -Q <file>
2. Move point to a line you can comment
3. M-x comment-line
4. M-x undo
5. Check buffer modification status in modeline or use (buffer-
modified-p)
Without the patched version of combine-change-calls-1, the buffer
status is "not modified since last save". Same result if you use
another command, for example kill-line, at step 2.
With new version of combine-change-calls-1, the buffer is seen as
modified.
I'm not sure but I imagine it has something to do with the lack of
timestamp in buffer-undo-list created by combine-change-calls-1.
next prev parent reply other threads:[~2023-06-22 19:28 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 13:40 bug#60467: 30.0.50; primitive-undo: Changes to be undone by function different from announced Ihor Radchenko
2023-01-01 14:38 ` Eli Zaretskii
2023-01-02 0:46 ` Gregory Heytings
2023-01-02 1:50 ` Gregory Heytings
2023-01-02 9:31 ` Ihor Radchenko
2023-01-03 9:41 ` Gregory Heytings
2023-01-03 12:46 ` Eli Zaretskii
2023-01-03 13:44 ` Gregory Heytings
2023-01-03 14:48 ` Eli Zaretskii
2023-01-03 15:05 ` Gregory Heytings
2023-01-03 16:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-03 16:33 ` Gregory Heytings
2023-01-03 16:51 ` Gregory Heytings
2023-01-04 0:16 ` Gregory Heytings
2023-01-04 2:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-04 9:24 ` Gregory Heytings
2023-01-04 10:50 ` Gregory Heytings
2023-01-04 14:39 ` Eli Zaretskii
2023-01-04 14:43 ` Gregory Heytings
2023-01-04 14:36 ` Eli Zaretskii
2023-01-04 14:39 ` Gregory Heytings
2023-01-04 18:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-04 18:16 ` Gregory Heytings
2023-01-04 18:42 ` Eli Zaretskii
2023-01-04 21:04 ` Gregory Heytings
2023-01-03 14:56 ` Gregory Heytings
2023-01-03 15:16 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-03 15:29 ` Gregory Heytings
2023-01-03 16:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-08 15:43 ` Alan Mackenzie
2023-01-09 6:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-09 12:16 ` Eli Zaretskii
2023-01-13 22:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-14 7:06 ` Eli Zaretskii
2023-01-02 9:27 ` Ihor Radchenko
2023-06-22 19:28 ` Frédéric Giquel via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-06-23 11:01 ` Eli Zaretskii
2023-06-23 13:06 ` Gregory Heytings
2023-06-26 14:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-26 14:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-26 15:18 ` Gregory Heytings
2023-06-26 15:30 ` Eli Zaretskii
2023-07-01 14:14 ` Gregory Heytings
2023-07-01 14:27 ` Eli Zaretskii
2023-07-15 7:46 ` Eli Zaretskii
2023-08-03 7:38 ` Eli Zaretskii
2023-08-10 11:28 ` Gregory Heytings
2023-08-10 13:41 ` Eli Zaretskii
2023-08-10 13:55 ` Gregory Heytings
2023-08-12 7:09 ` Eli Zaretskii
2023-08-16 16:09 ` Gregory Heytings
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=7ccb0e8131f84ca2ea0f0c0aed11dc197b578a64.camel@laposte.net \
--to=bug-gnu-emacs@gnu.org \
--cc=60467@debbugs.gnu.org \
--cc=frederic.giquel@laposte.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.