From: Nick Dokos <nicholas.dokos@hp.com>
To: PT <spamfilteraccount@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Making an org file more readable
Date: Mon, 24 Aug 2009 01:46:50 -0400 [thread overview]
Message-ID: <8858.1251092810@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from PT <spamfilteraccount@gmail.com> of "Mon, 24 Aug 2009 05:30:21 -0000." <loom.20090824T072924-831@post.gmane.org>
PT <spamfilteraccount@gmail.com> wrote:
> My main gripe with org is that the appearance is too
> crowded. Even if the header lines have different colors the
> individual projects and sections I keep in the file have no visual
> separation between them. For example, sometimes I'd like to add
> empty lines after a header, so there is some visual space before
> the next header begins. The problem is the empty lines at the end
> of the content are folded too when the content is folded.
>
> I know it's more of an outline issue than an org issue, but I ask
> here nevertheless: did anyone find a good way to separate the
> headers from each other in a big org file visually, so it is more
> readable?
>
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.
,----
|
| * foo
| This is a test.
| ** baz
| and another
|
|
| ** hunoz
| and one more
|
|
| * bar
`----
When you fold it, it becomes
,----
|
| * foo...
|
| * bar
`----
HTH,
Nick
next prev parent reply other threads:[~2009-08-24 5:48 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 [this message]
2009-08-24 5:55 ` PT
2009-08-24 11:11 ` PT
2009-08-24 14:18 ` Carsten Dominik
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=8858.1251092810@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.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).