Nicolas Goaziou writes:
> David Masterson writes:
>
>> Good try, but I think you got it backwards. I pulled down a daily
>> development snapshot tarball from yesterday (not good with git yet) and
>> tried it again. This time, it broke M-return by adding an extra blank
>> line after the header
Hello,
David Masterson writes:
> Good try, but I think you got it backwards. I pulled down a daily
> development snapshot tarball from yesterday (not good with git yet) and
> tried it again. This time, it broke M-return by adding an extra blank
> line after the header (ie. two blank lines),
Nicolas Goaziou writes:
> David Masterson writes:
>
>> * Header 1
>>
>> * Header 2
>>
>> Position the cursor on '1' and M-return will create a new header with a
>> blank line before and after it, but C-return will create a new header
>> with a blank line before, but not after it.
> I see. I
Hello,
David Masterson writes:
> * Header 1
>
> * Header 2
>
> Position the cursor on '1' and M-return will create a new header with a
> blank line before and after it, but C-return will create a new header
> with a blank line before, but not after it.
I see. I pushed a fix in master branch.
Nicolas Goaziou writes:
> David Masterson writes:
>> My example is simple.
>>
>> * emacs --no-init
>> * edit an org file with an outline
>> * position cursor at the end of an outline entry
>> * M-Return
>> ** result: a new header with a blank line before and after
>> * C-Return
>> ** result: a
Hello,
David Masterson writes:
> My example is simple.
>
> * emacs --no-init
> * edit an org file with an outline
> * position cursor at the end of an outline entry
> * M-Return
> ** result: a new header with a blank line before and after
> * C-Return
> ** result: a new header with a blank line
Nicolas Goaziou writes:
> David Masterson writes:
>> It apparently only affects org-insert-heading, but not
>> org-insert-heading-respect-content -- I'm not sure why. Is that
>> a bug?
> They should behave the same way, indeed. Again a minimal example would
> help.
My example is simple.
*
Hello,
David Masterson writes:
> It apparently only affects org-insert-heading, but not
> org-insert-heading-respect-content -- I'm not sure why. Is that
> a bug?
They should behave the same way, indeed. Again a minimal example would
help.
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
> David Masterson writes:
>> Why does org-insert-heading insert a heading with a blank line after it
>> inserts the heading while org-insert-heading-respect-context does not?
> It may be a bug. Do you have an ECM for it?
No. Thought it might be a mistake on my part.
Hello,
David Masterson writes:
> Why does org-insert-heading insert a heading with a blank line after it
> inserts the heading while org-insert-heading-respect-context does not?
It may be a bug. Do you have an ECM for it?
> Am I missing a setting? Or have I (accidently) set a setting without
Nicolas Goaziou writes:
> Neil Jerram writes:
>> On 23 November 2018 23:23:27 GMT, David Masterson
>> wrote:
>>>Probably a dumb question, but is there a standard format for Org
>>>outlines. I'm particularly wondering about the use of blank lines. I
>>>prefer to have blank lines before my
Hello,
Neil Jerram writes:
> On 23 November 2018 23:23:27 GMT, David Masterson
> wrote:
>>Probably a dumb question, but is there a standard format for Org
>>outlines. I'm particularly wondering about the use of blank lines. I
>>prefer to have blank lines before my headings for readability,
On 23 November 2018 23:23:27 GMT, David Masterson
wrote:
>Probably a dumb question, but is there a standard format for Org
>outlines. I'm particularly wondering about the use of blank lines. I
>prefer to have blank lines before my headings for readability, but I
>think a lot of other people
13 matches
Mail list logo
