unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Eli Qian" <eli.q.qian@gmail.com>,
	"Stefan Monnier" <monnier@iro.umontreal.ca>,
	"Gerd Möllmann" <gerd.moellmann@gmail.com>,
	"Matt Armstrong" <matt@rfc20.org>
Cc: 58928@debbugs.gnu.org
Subject: bug#58928: 29.0.50; overlays in org-mode are disrupted after call `org-capture`
Date: Tue, 01 Nov 2022 08:14:02 +0200	[thread overview]
Message-ID: <834jvjdwwl.fsf@gnu.org> (raw)
In-Reply-To: <87eduohyds.fsf@gmail.com> (message from Eli Qian on Mon, 31 Oct 2022 21:58:55 +0800)

> 1. start "emacs -Q"
> 2. type "C-x C-f" and "test.org" and RET
> 3. type the following:
> * DONE test
> CLOSED: [2022-10-31 Mon 18:27]
> :LOGBOOK:
> - State "DONE"       from "TODO"       [2022-10-31 Mon 18:27]
> :END:
> * DONE test
> CLOSED: [2022-10-31 Mon 18:27]
> :LOGBOOK:
> - State "DONE"       from "TODO"       [2022-10-31 Mon 18:27]
> :END:
> * DONE test
> CLOSED: [2022-10-31 Mon 18:27]
> :LOGBOOK:
> - State "DONE"       from "TODO"       [2022-10-31 Mon 18:27]
> :END:
> * DONE test
> CLOSED: [2022-10-31 Mon 18:27]
> :LOGBOOK:
> - State "DONE"       from "TODO"       [2022-10-31 Mon 18:27]
> :END:
> 
> 4. call `org-shifttab`(S-TAB), make sure all headlines are in 
> OVERVIEW.
> 5. load the following code:
> (setq org-capture-templates
>       '(("l" "test" entry (file "path to org")
>            "* %?"
>            :prepend t
>            :empty-lines 0)))
> 
> 6. Call `org-capture` in test.org buffer, and type something.
> 
> 
> Actual:
> 
> You will see overlays (org-ellipsis) will move randomly, and 
> reopening this file will return to normal.
> 
> Expected:
> 
> `org-capture` works fine, no format disruption.

Could someone please look at this problem ASAP?

Thanks.





  reply	other threads:[~2022-11-01  6:14 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 [this message]
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
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=834jvjdwwl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58928@debbugs.gnu.org \
    --cc=eli.q.qian@gmail.com \
    --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).