emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: Counter-intuitive behavior of org-insert-heading
Date: Mon, 20 May 2013 11:07:03 -0500	[thread overview]
Message-ID: <87mwrpr5y0.fsf@fastmail.fm> (raw)

The following commit introduced a bug in org-insert-heading.

 commit 3449c6d001b8d261b104bc9dd42bf1290d74bc0b
 Author: Bastien Guerry <bzg@altern.org>
 Date:   Thu Apr 11 00:35:31 2013 +0200
 
     org.el (org-insert-heading): Convert the current line into a headline
     
     * org.el (org-insert-heading-respect-content): Fix docstring.
     (org-insert-heading): When in a non-empty non-headline line,
     convert the current line into a headline.
     
     Thanks to Bernt Hansen for reporting this issue

I have org-insert-heading-respect-content set to nil.

Previously, when hit M-Ret at the end of a line, a new headline was
created on the next line. Pressing return at the end of the line
containing the date would result in a new headline, as expected. E.g.,

* A heading
  [2013-05-20 Mon 11:02]
                
...would become

* A heading
  [2013-05-20 Mon 11:02]
* 

... with the cursor placed after the new asterisk

And if the cursor was at the end of a folded headline, such as.

* A heading...

...a new heading would be created as expected...

* A heading...
*

With the commit above, however, the following happens when I hit the
cursor at the end of the line:

* A heading
* [2013-05-20 Mon 11:02]

And with a folded headline, the same thing happens. When the cursor is 
placed after the invisible section and I hit M-Ret:

* A heading...

...unfolds and becomes...

* A heading
* [2013-05-20 Mon 11:02]

Best,
Matt

             reply	other threads:[~2013-05-20 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 16:07 Matt Lundin [this message]
2013-08-31  6:19 ` Counter-intuitive behavior of org-insert-heading Carsten Dominik

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=87mwrpr5y0.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --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).