Hi Jason,
I finally had a chance to better understand what your patch does and
fix. I've applied it now -- thanks for it and for your patience!
--
Bastien
Bastien writes:
> 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
> |
>
Hi Jason,
Jason Dunsmore 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
Bastien writes:
> Jason Dunsmore 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 differ
Jason Dunsmore 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 the
Carsten Dominik writes:
> On Jan 5, 2011, at 2:24 AM, Jason Dunsmore wrote:
>
>> I like to leave a blank line at the end of items that have bodies,
>> but I
>> found functions like org-metaup, org-metadown, and org-refile were
>> leaving that blank line behind.
>
> These commands treat empty line
On Jan 5, 2011, at 2:24 AM, Jason Dunsmore wrote:
I like to leave a blank line at the end of items that have bodies,
but I
found functions like org-metaup, org-metadown, and org-refile were
leaving that blank line behind.
These commands treat empty lines as belonging to the entry
below the
