unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Matt Armstrong <matt@rfc20.org>, Eli Zaretskii <eliz@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	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: Tue, 01 Nov 2022 09:07:26 +0000	[thread overview]
Message-ID: <87bkprm4a9.fsf@localhost> (raw)
In-Reply-To: <da060572-d689-6906-e611-70ef4a319ede@gmail.com>

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> 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?

I cannot reproduce using somewhat old Emacs 29
Development version 41d3d71a1e67 on master branch; build date 2022-10-28.

I can reproduce after updating to the latest master.

FYI, CAPTURE-test.org is nothing but a narrowed indirect buffer.
In this particular case, CAPTURE-test.org is narrowed to 1..4 before you
start typing. You can widen it and will see that it is still the
original Org file.

Note that test.org itself is also narrowed, which should not happen.
Although, narrowing of test.org during capture can also be seen using
Emacs 28.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>





  parent reply	other threads:[~2022-11-01  9:07 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 [this message]
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

  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=87bkprm4a9.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=58928@debbugs.gnu.org \
    --cc=eli.q.qian@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --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 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).