From: Jason Dunsmore <emacs-orgmode@dunsmor.com>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: emacs-orgmode@gnu.org, Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: [PATCH] Preserve trailing blank lines
Date: Wed, 26 Jan 2011 12:52:04 -0600 [thread overview]
Message-ID: <87oc73xzu3.fsf@riotblast.dunsmor.com> (raw)
In-Reply-To: <87k4i3qg27.fsf@gnu.org> (Bastien's message of "Tue, 18 Jan 2011 00:13:52 +0100")
Bastien <bastien.guerry@wikimedia.fr> writes:
> Jason Dunsmore <jason@dunsmor.com> writes:
>
>> I now understand this is a formatting convention issue.
>
> I'm trying to figure out when this patch is useful. I understand this
> is when `org-blank-before-new-entry' doesn't set heading to t or auto,
> but I don't understand what it the difference the patch introduces then.
>
> Could you send a _visual_ example, with useless empty lines that you
> want to get rid off when org-metaup etc ?
Convention 1: Newline above headings
This seems to be used more often when the body does not have delimiting
newlines.
Configuration:
--8<---------------cut here---------------start------------->8---
(setq org-blank-before-new-entry '((heading . t)
(plain-list-item . t)))
--8<---------------cut here---------------end--------------->8---
Org example:
--8<---------------cut here---------------start------------->8---
* Section
** Subsection 1
Body
** Subsection 2
Body
--8<---------------cut here---------------end--------------->8---
Convention 2: Newline after bodies
This seems to be used more often when the body does have delimiting
newlines.
Configuration:
--8<---------------cut here---------------start------------->8---
(setq org-blank-before-new-entry '((heading . nil)
(plain-list-item . nil)))
--8<---------------cut here---------------end--------------->8---
Org example:
--8<---------------cut here---------------start------------->8---
* Section
** Subsection 1
Body
** Subsection 2
Body
--8<---------------cut here---------------end--------------->8---
I've seen both conventions in use on Worg and in Org-mode tutorials.
I just tested these configurations and Org examples out with the patch
and it seems to work well. I've been using the patch on my systems for
a while now and haven't noticed any bad side-effects.
Let me know if you need any other information.
Regards,
Jason
next prev parent reply other threads:[~2011-01-26 18:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 1:24 [PATCH] Preserve trailing blank lines Jason Dunsmore
2011-01-08 18:02 ` Carsten Dominik
2011-01-10 15:58 ` Jason Dunsmore
2011-01-17 23:13 ` Bastien
2011-01-26 18:52 ` Jason Dunsmore [this message]
2011-02-07 8:17 ` Bastien
2011-02-15 16:31 ` Jason Dunsmore
2011-03-09 10:07 ` [Accepted] " Bastien Guerry
2011-03-09 10:07 ` [PATCH] " Bastien
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=87oc73xzu3.fsf@riotblast.dunsmor.com \
--to=emacs-orgmode@dunsmor.com \
--cc=bastien.guerry@wikimedia.fr \
--cc=carsten.dominik@gmail.com \
--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).