From: Carsten Dominik <carsten.dominik@gmail.com>
To: PT <spamfilteraccount@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Making an org file more readable
Date: Mon, 24 Aug 2009 16:18:24 +0200 [thread overview]
Message-ID: <6389183B-B8F1-498B-9A96-8DECF364A777@gmail.com> (raw)
In-Reply-To: <loom.20090824T130450-666@post.gmane.org>
On Aug 24, 2009, at 1:11 PM, PT wrote:
> Nick Dokos <nicholas.dokos <at> hp.com> writes:
>>
>> You *can* get an empty line between two headers by having two empty
>> lines at
>> the end of the first section: the first empty line is considered
>> part of
>> the section and is folded with it, but the second one remains. E.g.
>
> One more thing for those who don't know this:
>
> I took a look at the relevant part of outline.el and turns out
> one empty line is enough if outline-blank-line is set to t.
>
>
> It's almost perfect. It would be perfect if outline would leave
> alone all empty lines after the content, so if I have e.g. two
> empty lines there then it would fold non-empty lines only leaving
> both empty lines visible, so that I could use as many
> empty lines for separation as I want.
Actually, Org pretty much overrules what outline does in this context.
I have just pushed a modification so that you can, after pulling
from git, set org-cycle-separator-lines to a negative number.
If you set it to -N, N empty lines will be required in order
to get a separation. But, if there are enough empty lines,
all will be shown.
You might want to set this to -1., I like my old value of +2 best.
- Carsten
next prev parent reply other threads:[~2009-08-24 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 5:30 Making an org file more readable PT
2009-08-24 5:46 ` Nick Dokos
2009-08-24 5:55 ` PT
2009-08-24 11:11 ` PT
2009-08-24 14:18 ` Carsten Dominik [this message]
2009-09-04 5:10 ` PT
2009-09-04 8:59 ` 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=6389183B-B8F1-498B-9A96-8DECF364A777@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=spamfilteraccount@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).