emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mikhail Skorzhisnkii <mskorzhinskiy@eml.cc>
To: Bastien <bzg@gnu.org>
Cc: Dmitrii Korobeinikov <dim1212k@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Folding headings which contain only blank lines
Date: Fri, 16 Oct 2020 21:36:46 +0300	[thread overview]
Message-ID: <87h7qu10ht.fsf@eml.cc> (raw)
In-Reply-To: <87lfhoahf6.fsf@gnu.org>


Patch ee3c3b554799c9f0fbe387848cd9eec7e9ab9d95 breaks unfolding 
org-cycle-separator-lines set to -1.

How to reproduce:
  1. Set org-cycle-separator-lines to -1;
  2. Try to fold and then unfold "Test" in the following file:
,* Test 1
,** Test 2

,* Test 3

Unfolding will not unfold Test1 with 
ee3c3b554799c9f0fbe387848cd9eec7e9ab9d95 applied. Reverting this 
patch makes it working back. Is there are any other way to fix 
this? Or may be this can be made as a customisation option?

Bastien <bzg@gnu.org> writes:

> Hi Dmitrii,
> Dmitrii Korobeinikov <dim1212k@gmail.com> writes:
>> When everything is folded (e.g. on startup), ellipses show 
>> after every
>> heading which has anything in it at all. This is true as well 
>> for the
>> headings containing only one or more blank lines. And while you 
>> can
>> unfold such lines, you can't fold them back unless you use 
>> Shift-Tab.
>> This appears to be inconsistent. Shouldn't it be possible to 
>> tab fold
>> such headings too?
> this should be fixed now (in ee3c3b554), thanks for reporting 
> this.

Kind regards,
  Mikhail Skorzhinskii

  reply	other threads:[~2020-10-16 18:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 10:47 Folding headings which contain only blank lines Dmitrii Korobeinikov
2020-09-05  6:03 ` Bastien
2020-10-16 18:36   ` Mikhail Skorzhisnkii [this message]
2020-10-17  6:23     ` Kyle Meyer
2020-10-23 14:59       ` Dmitrii Korobeinikov
2020-10-24  2:43         ` Kyle Meyer
2020-10-24 16:29           ` Dmitrii Korobeinikov
2020-10-25  5:48             ` Kyle Meyer
2020-10-27  4:12               ` Kyle Meyer

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=87h7qu10ht.fsf@eml.cc \
    --to=mskorzhinskiy@eml.cc \
    --cc=bzg@gnu.org \
    --cc=dim1212k@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).