From: Skip Collins <skip.collins@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: [BUG] buffer displays incorrectly after capture
Date: Wed, 27 Apr 2022 11:58:24 -0400 [thread overview]
Message-ID: <CABUh-76h=g1oaafekMo8YvB1GwwycGgDgr9bM1exL0BcxV8nOQ@mail.gmail.com> (raw)
In-Reply-To: <87o80mvrkv.fsf@localhost>
On Wed, Apr 27, 2022 at 4:48 AM Ihor Radchenko <yantar92@gmail.com> wrote:
> Fixed in 2d6f26c05 on main. And no, it was not that easy to fix.
> Captured headlines may or may not need to be unfolded.
Thanks. I confirm that behavior is correct for folded level 1
headlines. But the problem still exists at level 2 and deeper:
1. Open emacs with an empty file:
emacs test.org
2. From emacs, enable auto-revert-mode:
M-x auto-revert-mode
3. From a shell, add text to the file:
echo "* foo\nsome text\n** bar\nmore text\n" >>test.org
4. From emacs, cycle global visibility twice, so that the second level
headline is visible but folded:
S-TAB S-TAB
5. Observe the two folded headlines:
* foo...
** bar...
6. From the shell, add another level 2 headline at the end of the file:
echo "** baz\n" >>test.org
7. Observe that the new level 2 headline is not displayed as expected:
* foo...
** bar...
8. From emacs, move the cursor onto the "** bar" headline and cycle visibility:
TAB
9. Observe that the new level 2 headline still does not appear, but a
misplaced folding ellipsis does appear at the end:
* foo...
** bar
more text
...
10. Cycle global visibility twice:
S-TAB S-TAB
11. Observe the correct display of all headlines:
* foo...
** bar...
** baz
next prev parent reply other threads:[~2022-04-27 15:59 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
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 [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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-76h=g1oaafekMo8YvB1GwwycGgDgr9bM1exL0BcxV8nOQ@mail.gmail.com' \
--to=skip.collins@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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/org-mode.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).