Nicolas Goaziou <[email protected]> writes:
> David Masterson <[email protected]> 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 before but not after
> I cannot reproduce your issue. The only difference that could occur is
> when you have sub-trees, since <C-RET> inserts the new headline at its
> end.
Hmm. Tried again. Severely trimmed my .emacs to the following:
;;
(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
(global-set-key "\C-cc" 'org-capture)
(global-set-key "\C-cb" 'org-switchb)
(custom-set-variables
'(package-archives
(quote
(("gnu" . "https://elpa.gnu.org/packages/")
("org" . "https://orgmode.org/")
("melpa-stable" . "https://stable.melpa.org/packages/"))))
'(package-selected-packages
(quote
(org adaptive-wrap auctex auto-correct python)))
'(text-mode-hook
(quote
(turn-on-flyspell visual-line-mode text-mode-hook-identify))))
(custom-set-faces
'(cursor ((t (:background "blue")))))
;;
I am running Emacs v26.1 on Cygwin under Windows with Org v9.1.14.
Everything seems to work fine (slow at times, but...). A simple file
produces the problem (and, of course, it is seen in much more complex
files).
* 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.
Not a Lisp person, but I was wondering if there is something different
in the way org-meta-return is doing its processing to determine if it
should handle a header, list, or a table? That extra processing doesn't
appear to be in C-return.
--
David