emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <eschulte@mitre.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: Whitespace and outline structure...
Date: Wed, 12 Dec 2007 09:07:27 -0800	[thread overview]
Message-ID: <18272.5455.565230.491260@gargle.gargle.HOWL> (raw)
In-Reply-To: <acf852aa0712120824g1458641biad48fa8ae2fc20b3@mail.gmail.com>

I'm not sure if this is the case for others as well, but I care more
about the number of lines of whitespace preceding headings in folded
org files. I would find an option like...

(setq org-preceding-blank-lines
      '((org-level-1 . 2)
	(org-level-2 . 1)
	(list-item   . 1)
	(t . delete)))

to be more helpful. Then when folding a subtree Orgmode would check
the next header following the subtree, and count back.

Just throwing this out there,
Thanks,
Eric

On Wednesday, December 12, at 17:24, Carsten Dominik wrote:
 > On Dec 12, 2007 4:17 PM, Bastien <bzg@altern.org> wrote:
 > > Yes.  Considering an option like:
 > >
 > > (setq org-allow-blank-lines   ;; or org-allow-max-blank-lines
 > >          '((org-level-1 . 2)
 > >            (org-level-2 . 1)
 > >            (list-item   . 1)
 > >            (t . delete))
 > >
 > > The rule for handling trailing blank lines would be as follow : when
 > > moving/cutting a subtree of level N, only allow a definite number of
 > > trailing blank lines (L_n).  If there is more than L_n lines, try to
 > > decide whether these additional blank lines are part of the subtree
 > > above... etc.  If blank lines cannot be attached to a subtree, either
 > > delete them, or reject them at the end of the subtree.
 > >
 > > Not sure how this could be implemented, but I just wanted to clarify
 > > what I had in mind.
 > 
 > I am not sure an option is the right thing here, because it will continue to
 > remain difficult to figure out where to put the boundaries.
 > 
 > The best might be to look *before* a heading and see how many empty
 > lines there are, and then include up to that many lines below the subtree.
 > It seems to me that this might get quite close to the right behavior,
 > but I am sure there will be cases where also this idea will not work
 > correctly.
 > 
 > - Carsten
 > 
 > 
 > _______________________________________________
 > 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

  reply	other threads:[~2007-12-12 17:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-11 11:47 Whitespace and outline structure Daniel Pittman
2007-12-11 13:39 ` Bastien
2007-12-11 13:55   ` Phil Jackson
2007-12-11 14:36     ` Bastien
2007-12-12 12:17       ` Daniel Pittman
2007-12-12 15:17         ` Bastien
2007-12-12 16:24           ` Carsten Dominik
2007-12-12 17:07             ` Eric Schulte [this message]
2007-12-12 17:36             ` Eric Schulte

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=18272.5455.565230.491260@gargle.gargle.HOWL \
    --to=eschulte@mitre.org \
    --cc=emacs-orgmode@gnu.org \
    /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).