emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Inserting a new item vs a new headline
Date: Wed, 31 Oct 2012 12:28:17 +0100	[thread overview]
Message-ID: <80ehke98z2.fsf@somewhere.org> (raw)

Hello,

I find weird the positioning of a new headline, when created via M-RET.

Let me explain with the following ECM:

--8<---------------cut here---------------start------------->8---
* Current section

** List

- Foo
- Baz
@                                  <<< @ = position of the cursor

* Next section
--8<---------------cut here---------------end--------------->8---

If I want to add new item to the list, I press M-RET. It will do the right
thing, and conserves the whitelines below:

--8<---------------cut here---------------start------------->8---
* Current section

** List

- Foo
- Baz
- @


* Next section
--8<---------------cut here---------------end--------------->8---

C-RET, on the other hand, will go at the most far position (one character
before the next section), and glue the new headline there:

--8<---------------cut here---------------start------------->8---
* Current section

** List

- Foo
- Baz


** @
* Next section
--8<---------------cut here---------------end--------------->8---

Often, when not thinking at that, I already insert white lines, but then, I
unavoidably have to remove them by hand.

--8<---------------cut here---------------start------------->8---
* Current section

** List

- Foo
- Baz

@

* Next section
--8<---------------cut here---------------end--------------->8---

becomes this:

--8<---------------cut here---------------start------------->8---
* Current section

** List

- Foo
- Baz



** @
* Next section
--8<---------------cut here---------------end--------------->8---

I would have loved to see the `**' where the cursor was.

I find this not inline with what would happen if I'd know the text of my new
headline:

--8<---------------cut here---------------start------------->8---
* Current section

** List

- Foo
- Baz

@Text of my new headline

* Next section
--8<---------------cut here---------------end--------------->8---

becomes, when M-RETing[1], as *I* expect it:

--8<---------------cut here---------------start------------->8---
* Current section

** List

- Foo
- Baz

** Text of my new headline@

* Next section
--8<---------------cut here---------------end--------------->8---

All of this is really about details. And, maybe, they're due to misuse of
C-RET and M-RET.

Just wanted to signal them, in case that...

Best regards,
  Seb

[1] Not C-RETing...

-- 
Sebastien Vauban

                 reply	other threads:[~2012-10-31 11:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=80ehke98z2.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).