emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Skip Collins <skip.collins@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: [BUG] buffer displays incorrectly after capture
Date: Thu, 28 Apr 2022 07:37:06 +0800	[thread overview]
Message-ID: <87ilqu85el.fsf@localhost> (raw)
In-Reply-To: <CABUh-76h=g1oaafekMo8YvB1GwwycGgDgr9bM1exL0BcxV8nOQ@mail.gmail.com>

Skip Collins <skip.collins@gmail.com> writes:

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

This is not a bug. You will routinely see constructs like this when you
jump to a deeply nested headline in real Org files. Only level 1
headlines are always kept visible by convention (and some people even
argue that this convention should be dropped e.g. in sparse trees).

To deal with such situations, see org-reveal (possibly with prefix


      reply	other threads:[~2022-04-27 23:36 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
2022-04-27 23:37         ` Ihor Radchenko [this message]

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=87ilqu85el.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=skip.collins@gmail.com \


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