From: Carsten Dominik <carsten.dominik@gmail.com>
To: Tom <levelhalom@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: VISIBILITY:folded hides all empty lines after heading if org-cycle-separator-lines is set to negative
Date: Wed, 12 May 2010 15:57:19 +0200 [thread overview]
Message-ID: <047BDF9D-5BE0-44FE-A3CC-148F14B15D8B@gmail.com> (raw)
In-Reply-To: <loom.20100511T211906-196@post.gmane.org>
Hi Tom,
nice catch! This is fixed now.
Thank you!
- Carsten
On May 11, 2010, at 9:27 PM, Tom wrote:
> Here is an org file:
>
> ---- file begin -----
> * test1
> :PROPERTIES:
> :VISIBILITY: folded
> :END:
> ** test2
>
>
>
>
> * test3
>
> ---- file end -----
>
> org-cycle-separator-lines is set to -2, so org should hide one empty
> line after the heading when it's folded and leave the others there.
>
> If I fold the test1 tree with TAB then it collapses only one empty
> line after test2 and leaves the other empty lines, so this is correct.
>
> If I add VISIBILITY:folded to the test1 tree then and reopen the file
> all the empty lines are hidden after test2 regardless of how many
> there are.
> If I then unfold and then fold the test1 tree manually with TAB it
> works correctly.
>
> So it looks like VISIBILTY:folded doesn't take the negative value of
> org-cycle-separator-lines into account.
>
> Org-mode version 6.33x
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
next prev parent reply other threads:[~2010-05-12 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 19:27 VISIBILITY:folded hides all empty lines after heading if org-cycle-separator-lines is set to negative Tom
2010-05-11 20:41 ` Tom
2010-05-12 13:57 ` Carsten Dominik [this message]
2010-05-12 14:24 ` Carsten Dominik
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=047BDF9D-5BE0-44FE-A3CC-148F14B15D8B@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=levelhalom@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).