From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eddward DeVilla" Subject: Re: Re: Dividers in File Date: Wed, 19 Nov 2008 21:51:43 -0600 Message-ID: References: <20081118193453.F32BC320057@mail.dagertech.net> <87y6zgbyur.fsf@gmail.com> <87r658k74d.fsf@kassiopeya.MSHEIMNETZ> <49243916.1020607@diplan.de> <87ljvfd4up.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1079247886==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L30a2-0005ZE-EK for emacs-orgmode@gnu.org; Wed, 19 Nov 2008 22:51:46 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L30a1-0005Z2-F4 for emacs-orgmode@gnu.org; Wed, 19 Nov 2008 22:51:45 -0500 Received: from [199.232.76.173] (port=45755 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L30a1-0005Yz-9F for emacs-orgmode@gnu.org; Wed, 19 Nov 2008 22:51:45 -0500 Received: from wf-out-1314.google.com ([209.85.200.174]:38629) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L30a1-0006mF-2T for emacs-orgmode@gnu.org; Wed, 19 Nov 2008 22:51:45 -0500 Received: by wf-out-1314.google.com with SMTP id 28so266022wfc.24 for ; Wed, 19 Nov 2008 19:51:43 -0800 (PST) In-Reply-To: <87ljvfd4up.fsf@fastmail.fm> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Matthew Lundin Cc: orgmode , "news.gmane.org" --===============1079247886== Content-Type: multipart/alternative; boundary="----=_Part_112802_1806777.1227153103308" ------=_Part_112802_1806777.1227153103308 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wed, Nov 19, 2008 at 11:04 AM, Matthew Lundin wrote: > "news.gmane.org" writes: > > > Sebastian Rose schrieb: > >> Hi David, > >> > >> > >> "Eric Schulte" 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" 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 > I've considered that myself, but I just don't like the look of it. More than once I've wished I could use something like the hline markup and get a horizontal line that was scoped with the reset of the outline in the org-buffer and on export. So something like the following ################# * foo 1 * foo 2 ----- * bar 1 *** bar 1.1 ----- * bar 2 ----- * Baz! ################ would display as ################ * foo 1 * foo2 ------------------ <= buffer or wrap wide, doesn't fold into foo2 * bar 1 *** bar 1.1 -------------- <= buffer or wrap wide, doesn't fold into Bar 1.1 but does fold into Bar 1 * bar 2 ------------------ <= buffer or wrap wide, doesn't fold into foo2 * Baz! ################ I'd guess it might not be too hard with the right but I haven't been annoyed enough to look into it. Edd ------=_Part_112802_1806777.1227153103308 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Wed, Nov 19, 2008 at 11:04 AM, Matthew Lundin <mdl@imapmail.org> wrote:
"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

I've considered that myself, but I just don't like the look of it.  More than once I've wished  I could use something like the hline markup and get a horizontal line that was scoped with the reset of the outline in the org-buffer and on export.  So something like the following

#################

* foo 1
* foo 2

-----

* bar 1
*** bar 1.1
  -----
* bar 2

-----

* Baz!

################

would display as

################

* foo 1
* foo2

------------------    <= buffer or wrap wide, doesn't fold into foo2

* bar 1
*** bar 1.1
  --------------    <= buffer or wrap wide, doesn't fold into Bar 1.1 but does fold into Bar 1

* bar 2

------------------    <= buffer or wrap wide, doesn't fold into foo2

* Baz!

################


I'd guess it might not be too hard with the right but I haven't been annoyed enough to look into it.

Edd
------=_Part_112802_1806777.1227153103308-- --===============1079247886== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============1079247886==--