From: Matt Armstrong <matt@rfc20.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Eason Huang <aqua0210@foxmail.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
"Ihor Radchenko" <yantar92@posteo.net>,
"Eli Zaretskii" <eliz@gnu.org>,
58928@debbugs.gnu.org, "Eli Qian" <eli.q.qian@gmail.com>
Subject: bug#58928: 29.0.50; overlays in org-mode are disrupted after call `org-capture`
Date: Fri, 04 Nov 2022 11:06:13 -0700 [thread overview]
Message-ID: <87wn8awq5m.fsf@rfc20.org> (raw)
In-Reply-To: <jwvtu3fv13x.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> 4. Now the .notes buffer is like this:
>> * Tasks
>> ** TODO test1...
>> 5. Try step 2 again, now you will see the issue. Now the .notes buffer looks like this:
>> * Tasks
>> ** TODO test1...TODO
>> [2022-11-03 Thu]
>> test1
>
> With the latest changes I pushed, at the end of step 5 I see only:
>
> ** TODO test1...
>
> This doesn't look completely right (the "..." hides both the "test1"
> todo and the subsequent one), but I see exactly the same when
> I try it on Emacs-28, so are you sure it's something that changed with
> the new overlays code?
It isn't a regression in Emacs' overlay implementation. It is a bug
introduced in the org-mode shipped with Emacs 28. I verified that this
is fixed in current org mode dev version.
So, I think we're done here!
next prev parent reply other threads:[~2022-11-04 18:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 13:58 bug#58928: 29.0.50; overlays in org-mode are disrupted after call `org-capture` Eli Qian
2022-11-01 6:14 ` Eli Zaretskii
2022-11-01 7:01 ` Gerd Möllmann
[not found] ` <87sfj3gmsx.fsf@gmail.com>
2022-11-01 7:50 ` Gerd Möllmann
2022-11-01 8:08 ` Gerd Möllmann
2022-11-01 9:07 ` Ihor Radchenko
2022-11-01 9:20 ` Gerd Möllmann
2022-11-01 22:36 ` Matt Armstrong
2022-11-01 23:25 ` Matt Armstrong
2022-11-02 1:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-02 2:49 ` Matt Armstrong
2022-11-02 4:53 ` Gerd Möllmann
2022-11-03 13:10 ` Eason Huang
2022-11-03 14:25 ` Gerd Möllmann
2022-11-03 14:57 ` Eason Huang
2022-11-03 15:18 ` Gerd Möllmann
2022-11-03 15:41 ` Eason Huang
2022-11-03 15:02 ` Eason Huang
2022-11-03 15:45 ` Eason Huang
2022-11-03 16:12 ` Gerd Möllmann
2022-11-03 22:51 ` Matt Armstrong
2022-11-04 2:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-04 4:33 ` Matt Armstrong
2022-11-04 16:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-04 22:47 ` Matt Armstrong
2022-11-04 22:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-05 6:28 ` Eli Zaretskii
2022-11-04 3:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-04 18:06 ` Matt Armstrong [this message]
2022-11-05 2:45 ` Ihor Radchenko
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=87wn8awq5m.fsf@rfc20.org \
--to=matt@rfc20.org \
--cc=58928@debbugs.gnu.org \
--cc=aqua0210@foxmail.com \
--cc=eli.q.qian@gmail.com \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=yantar92@posteo.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 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).