From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Qian <eli.q.qian@gmail.com>
Cc: Matt Armstrong <matt@rfc20.org>, Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
58928@debbugs.gnu.org
Subject: bug#58928: 29.0.50; overlays in org-mode are disrupted after call `org-capture`
Date: Tue, 1 Nov 2022 08:50:52 +0100 [thread overview]
Message-ID: <da060572-d689-6906-e611-70ef4a319ede@gmail.com> (raw)
In-Reply-To: <87sfj3gmsx.fsf@gmail.com>
On 01.11.22 08:11, Eli Qian wrote:
> This is my first bug reporting, so I apologize if there are any omissions.
>
> On Tue, Nov 01 2022, Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
>
>> I've evaluated the form above as-is in *scratch*, and done the S-tab.
>> I now have 4 lines looking like "* DONE test..." in the buffer.
>
> After Step 4, save the buffer to "~/test.org". Now You have 4 lines looking
> like "* DONE test..." in "~/test.org".
>
> In Step 5, the actual code is
>
> (setq org-capture-templates
> '(("l" "global notes" entry (file "~/test.org")
> "* %?"
> :prepend t
> :empty-lines 0)))
>>>> 6. Call `org-capture` in test.org buffer, and type something.
>>
>> M-x org-capture RET in test.org asks me what template to use, and I
>> choose 'l'. I then type something and hit C-c C-c. It asks me to let
>> it create a directory ~/org, and I let it do that. What I see after
>> that in the test.log buffer looks like it did before. There are same 4
>> lines.
>>
>> What am I doing wrong?
>>
>> (This is current master.)
>
> Step 6:
> M-x org-capture RET in test.org , you will see the capture buffer appears
> on the right, while test.org buffer on the left. Then type something,
> you will see the text in test.org buffer disrupted.
Thanks, that worked. (It's not a big deal, but please keep the others
in the CC.)
What I see now is that I have 2 windows. One is showing test.org, the
other is a buffer CAPTURE-test.org. While typing in CAPTURE-test.org,
the text in test.org is mangled with each key stroke. The invisible
parts (...) are moved around in test.org. C-l doesn't change anything.
Running with --enable-checking and ASAN doesn't show anything.
Do we have someone who knows Org internals, and can tell what exactly
typing in CAPTURE-test.org does, presumably with overlays?
next prev parent reply other threads:[~2022-11-01 7:50 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=da060572-d689-6906-e611-70ef4a319ede@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=58928@debbugs.gnu.org \
--cc=eli.q.qian@gmail.com \
--cc=eliz@gnu.org \
--cc=matt@rfc20.org \
--cc=monnier@iro.umontreal.ca \
/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.