emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode <emacs-orgmode@gnu.org>,
	Jisang Yoo <jisang.yoo.ac+org@gmail.com>
Subject: Re: M-RET inside the first second-level heading of the first first-level heading
Date: Fri, 17 May 2013 18:08:18 -0500	[thread overview]
Message-ID: <CA+M2ft_4exqcHxx=gNMJKBGUmn35WonjN_nuvv_Av8A20BgmLg@mail.gmail.com> (raw)
In-Reply-To: <F93454A9-137A-4BD3-A299-BC474C9EB6AE@gmail.com>

On Fri, May 10, 2013 at 1:49 AM, Carsten Dominik
<carsten.dominik@gmail.com> wrote:
> On 7.5.2013, at 23:34, John Hendy <jw.hendy@gmail.com> wrote:
>> On Tue, May 7, 2013 at 4:54 AM, Bastien <bzg@gnu.org> wrote:
>>> Hi John,
>>> John Hendy <jw.hendy@gmail.com> writes:
>>>> On Fri, Apr 26, 2013 at 1:54 AM, Bastien <bzg@gnu.org> wrote:
>>>>> Hi Jisang,
>>>>> Jisang Yoo <jisang.yoo.ac+org@gmail.com> writes:
>>>>>> 2. Place cursor at the beginning of "** bacon" and press M-RET and org creates
>>>>>> a first-level heading.
>>>>> This should now be fixed.  Thanks for reporting this,
>>>> There were some same/similar/related issues as well, and I'm still not
>>>> getting perfect results.
>>>> Using a minimal config (below), if I create this in a new file
>>>> * test
>>>> ** test1
>>>> ** test2
>>>> and then fold on * test, I get this:
>>>> * test...2
>>> I do have (setq require-final-newline t) in my config, which prevents
>>> this.  What happens is this: if you don't have the config above, the
>>> folding will get wrong and display the "2" from the end of the buffer.
>>>> Also, after navigating to the end of * test...2 (with it folded) and
>>>> issuing M-RET, I get a new second level heading after ** test2. I
>>>> would have expected a new first level headline since I did M-RET on a
>>>> first level headline. Or is that the default behavior?
>>> If you are before the "..." ellipsis, you are on a first level
>>> headline and M-RET will insert a first level headline.  Otherwise you
>>> are on a second level headline ("test2") and it will insert a second
>>> level headline.
>> Ah, that now makes sense. But... just to be clear, take this case:
>> * Headline1
>> - list1
>> - list2
>> Now fold it:
>> * Headline1<cursor>...
>> If I do M-RET at <cursor>, I get:
>> * Headline1
>> * <cursor>
>> - list1
>> - list2
>> Is that how it's supposed to work? My use case is generally to have a
>> new headline after * Headline1 *and* it's contents, not putting
>> contents inside the new headline.
>> C-RET seems to behave more like I'd expect. In reading the manual, I
>> think I was just confused on usage based on the definition of C-RET,
>> however this in the description of M-RET is confusing:
>> #+begin_quote
>> If the command is used at the end of a folded subtree (i.e., behind
>> the ellipses at the end of a headline), then a headline like the
>> current one will be inserted after the end of the subtree. Calling
>> this command with C-u C-u will unconditionally respect the headline's
>> content and create a new item at the end of the parent subtree.
>> #+end_quote
>> It makes it seem like my original case in which the cursor is behind
>> (after?) the ... should insert a same-level headline after the end of
>> the current subtree (which I would assume means that headline and all
>> contents). Am I reading that incorrectly? It doesn't really talk about
>> the behavior if you're before the ellipsis.
> Yes, this is also a bit confusing.  I think it would be desirable if it
> worked as described in the manual, but this is not what is happening.
> For now, I fixed the manual.

Much appreciated, and I'll be following the other M-RET and C-RET
thread as it seems some of this behavior will change in the near


> - Carsten
>> Thanks for clarifying,
>> John
>>>> If so, I guess my only concern is the folding of the end of a headline
>>>> if there's no hard return after it into the ellipsis of it's parent.
>>> Yes.  Maybe M-RET could/should handle this corner-case but since
>>> `org-insert-heading' is deserving a full rewrite, I'm not going to
>>> try to handle this corner-case myself... let's just keep it in mind
>>> when doing the rewrite.  Thanks for spotting it,
>>> --
>>> Bastien

      reply	other threads:[~2013-05-17 23:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 20:39 Jisang Yoo
2013-04-25 21:51 ` John Hendy
2013-04-26  6:54 ` Bastien
2013-05-02 18:51   ` John Hendy
2013-05-02 18:52     ` John Hendy
2013-05-07  9:54     ` Bastien
2013-05-07 21:34       ` John Hendy
2013-05-10  6:49         ` Carsten Dominik
2013-05-17 23:08           ` John Hendy [this message]

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:

  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='CA+M2ft_4exqcHxx=gNMJKBGUmn35WonjN_nuvv_Av8A20BgmLg@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=bzg@gnu.org \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jisang.yoo.ac+org@gmail.com \
    --subject='Re: M-RET inside the first second-level heading of the first first-level heading' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


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).