From: Matthew Lundin <mdl@imapmail.org>
To: "news.gmane.org" <rainer.stengele@diplan.de>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: Dividers in File
Date: Wed, 19 Nov 2008 11:04:46 -0600 [thread overview]
Message-ID: <87ljvfd4up.fsf@fastmail.fm> (raw)
In-Reply-To: <49243916.1020607@diplan.de> (news gmane org's message of "Wed\, 19 Nov 2008 17\:04\:38 +0100")
"news.gmane.org" <rainer.stengele@diplan.de> writes:
> Sebastian Rose schrieb:
>> Hi David,
>>
>>
>> "Eric Schulte" <schulte.eric@gmail.com> writes:
>>> Hi David,
>>>
>>> Is there any Reason why you don't just make the dividers the first level
>>> of headlines? -- Eric
>>
[snip]
>>
>>> "David A. Gershman" <dagershman@dagertech.net> writes:
>>>
>>>> In my org file, I have different sections setup. I'd like to separate
>>>> the sections with comment dividers. For example, I'd like to have:
>>>>
>>>> #####################
>>>> # Section 1
>>>>
>>>> * Heading 1
>>>> * Heading 2
>>>> * Heading 3
>>>>
>>>> # End Section 1
>>>> #####################
>>>>
>>>> #####################
>>>> # Section 2
>>>>
>>>> * Heading 1
>>>> * Heading 2
>>>> * Heading 3
>>>>
>>>> # End Section 2
>>>> #####################
>>>>
>>>> But when I fold stuff, I get:
>>>>
>>>> * Heading 1...
>>>> * Heading 3...
>>>> * Heading 1...
>>>> * Heading 3...
>>>>
>>>> Notice the dividers got folded into the trees. Any way to prevent this?
When I need quick dividers for better visibility, I adopt the approach
Eric mentions above. E.g.,
* ----section one------
* Heading one
* Heading two
* ----section two------
* Heading one
* Heading two
- Matt
next prev parent reply other threads:[~2008-11-19 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 19:34 Dividers in File David A. Gershman
2008-11-18 19:47 ` Eric Schulte
2008-11-18 22:21 ` Sebastian Rose
2008-11-19 16:04 ` news.gmane.org
2008-11-19 17:04 ` Matthew Lundin [this message]
2008-11-20 3:51 ` Eddward DeVilla
2008-11-20 7:26 ` Carsten Dominik
2008-11-19 20:50 ` Sebastian Rose
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=87ljvfd4up.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=emacs-orgmode@gnu.org \
--cc=rainer.stengele@diplan.de \
/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).