From: Kyle Meyer <kyle@kyleam.com>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Bug: headline folding broken by whitespace
Date: Sat, 31 Oct 2020 12:49:48 -0400 [thread overview]
Message-ID: <874kma8hn7.fsf@kyleam.com> (raw)
In-Reply-To: <9ab68310-7aeb-7a6a-0a73-07c292dd23d7@grinta.net>
Daniele Nicolodi writes:
> Hello,
>
> i saw a few reports of bugs related to folding and unfolding of
> headlines recently, but I think this is not a duplicate.
I think you're referring to
https://orgmode.org/list/87h7qu10ht.fsf@eml.cc
https://orgmode.org/list/CAJj=8EFJXFu9ZQ11cO24AAu=1jykW2Zr+=R4FLuKG=bLjfUe+g@mail.gmail.com
The cases reported there are resolved by e8070d71a (Revert "org.el:
Allow empty subtrees to be folded back", 2020-10-26).
> I just noticed that with the latest release (Org mode version 9.4
> (9.4-27-g47bf60-elpa @ /Users/daniele/.emacs.d/elpa/org-20201026/)
> unfolding of headlines is broken by whitespace. In particular with a
> buffer with this content:
>
> * Foo
> ** Bar
> bar bar bar+49 1520 7178926
>
>
> * Baz
>
> where the line before "* Baz" contains a single whitespace character,
> the headline "* Foo" can be folded but cannot be unfolded. Removing the
> whitespace while the headline is folded fixes the problem.
Yep, with your test case (making sure to add a space on the line before
Baz), I can trigger the issue on your reported version (47bf6005b), and
it goes away with e8070d71a. So, it looks like the same underlying
problem and should go away with the next elpa bump.
next prev parent reply other threads:[~2020-10-31 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 15:06 Bug: headline folding broken by whitespace Daniele Nicolodi
2020-10-31 16:28 ` Russell Adams
2020-10-31 16:44 ` Daniele Nicolodi
2020-10-31 16:53 ` Kyle Meyer
2020-10-31 16:49 ` Kyle Meyer [this message]
2020-10-31 16:59 ` Daniele Nicolodi
2020-10-31 17:58 ` Kyle Meyer
2020-10-31 20:43 ` Russell Adams
2020-10-31 21:12 ` Kyle Meyer
2020-11-02 8:25 ` Richard Kim
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=874kma8hn7.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=daniele@grinta.net \
--cc=emacs-orgmode@gnu.org \
/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).