emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: headline folding broken by whitespace
Date: Sat, 31 Oct 2020 13:58:25 -0400	[thread overview]
Message-ID: <87sg9u6zwe.fsf@kyleam.com> (raw)
In-Reply-To: <c117302e-66f9-10c5-6328-3463de1779a2@grinta.net>

Daniele Nicolodi writes:

> This is funny. I have two emacs instances running: one with my
> customizations and an emacs -Q one. The first exhibits the issue, the
> second does not

If your emacs -Q session is just using the Org that comes with Emacs
27.1, it won't have the commit that introduced the regression: ee3c3b554
(org.el: Allow empty subtrees to be folded back, 2020-09-05).  That was
part of the 9.3.8 release.

> matching what Russel reports.

As I mentioned elsewhere in the thread, my guess is that Russell was
using your example as is, rather than adding the space on the line
(where X is below).

--8<---------------cut here---------------start------------->8---
* Foo
** Bar
   bar bar bar+49 1520 7178926

* Baz
--8<---------------cut here---------------end--------------->8---

If I use that example (with no custom configuration), the issue
(i.e. Foo won't unfold) starts with ee3c3b554 and goes away when that
commit is reverted in e8070d71a.

  reply	other threads:[~2020-10-31 17:59 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
2020-10-31 16:59   ` Daniele Nicolodi
2020-10-31 17:58     ` Kyle Meyer [this message]
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:

  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=87sg9u6zwe.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=daniele@grinta.net \
    --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).