emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Skip Collins <skip.collins@gmail.com>
To: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: buffer displays incorrectly after capture
Date: Mon, 4 Apr 2022 11:25:02 -0400	[thread overview]
Message-ID: <CABUh-76q6yP7NhxG3WeQvwdE=ah+B8+CaTqUyjDo09LkR+Ze0A@mail.gmail.com> (raw)
In-Reply-To: <CABUh-74xzKdCkpv5MutcaAjiMQd4Kx9ztWBdC-+BL3C0niSCWA@mail.gmail.com>

On Fri, Apr 1, 2022 at 3:46 PM Skip wrote:
> Another manifestation of the problem shows up when using
> auto-revert-mode. Starting with the single headline in a folded state
> as above, when I execute the following command in a shell,
> echo "* TODO bar :action:" >>capture.org
> then the capture.org buffer looks like this:
> * TODO foo :action:...* TODO bar :action:
> TAB unfolding the first headline shows up like this:
> * TODO foo :action:
> some text...* TODO bar :action:

I confirmed that the buffer display bug occurs with emacs -Q. Steps to
1. From a shell, open emacs with an empty file:
emacs -Q test.org

2. From emacs, enable auto-revert-mode:
M-x auto-revert-mode

3. From another shell, add text to the file:
echo "* foo\nsome text\n" >>test.org

4. From emacs, fold the headline:

5. From the shell, add more text to the file:
echo "* bar\n" >>test.org

6. Observe the incorrect display of the two headlines:
* foo...* bar

7. From emacs, fix the buffer display:

8. Observe the correct display of the two headlines:
* foo...
* bar

This bug seems to trigger when text is added indirectly to an org-mode
buffer, via both capture and auto-revert. I suspect it would show up
via refile as well.

  reply	other threads:[~2022-04-04 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 19:46 buffer displays incorrectly after capture Skip Collins
2022-04-04 15:25 ` Skip Collins [this message]
2022-04-07 23:26   ` [BUG] " Skip Collins
2022-04-26 22:52     ` [BUG] buffer folds incorrectly Skip Collins
2022-04-27  8:49     ` [BUG] buffer displays incorrectly after capture Ihor Radchenko
2022-04-27 15:58       ` Skip Collins
2022-04-27 23:37         ` 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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABUh-76q6yP7NhxG3WeQvwdE=ah+B8+CaTqUyjDo09LkR+Ze0A@mail.gmail.com' \
    --to=skip.collins@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).