emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bastien.guerry@wikimedia.fr>
To: Jason Dunsmore <emacs-orgmode@dunsmor.com>
Cc: emacs-orgmode@gnu.org, Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: [PATCH] Preserve trailing blank lines
Date: Mon, 07 Feb 2011 09:17:07 +0100	[thread overview]
Message-ID: <87bp2o1cos.fsf@gnu.org> (raw)
In-Reply-To: <87oc73xzu3.fsf@riotblast.dunsmor.com> (Jason Dunsmore's message of "Wed, 26 Jan 2011 12:52:04 -0600")

Hi Jason,

Jason Dunsmore <emacs-orgmode@dunsmor.com> writes:

> Convention 1: Newline above headings
> Convention 2: Newline after bodies
>
> 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.

I'm back to this patch -- thanks for the clear explanations.

However, with your patch, I get a weird behavior.

Config:

,----
| (setq org-blank-before-new-entry '((heading . nil)
|                                    (plain-list-item . nil)))
`----

Test file:

,----
| * Section
| 
| ** Subsection 1
| Body
| 
| ** Subsection 2
| Body
`----

Trying to move Subsection 1 down (with org-metadown):

,----
| * Section
| Body              <<<<<< ??
| 
| ** Subsection 2
| 
| ** Subsection 1
| Body
`----

Are you able to reproduce this?  

-- 
 Bastien

  reply	other threads:[~2011-02-07  8:17 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
2011-02-07  8:17         ` Bastien [this message]
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=87bp2o1cos.fsf@gnu.org \
    --to=bastien.guerry@wikimedia.fr \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@dunsmor.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).