emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [feature request] org-insert-heading
Date: Sun, 12 Feb 2012 09:19:08 +0100	[thread overview]
Message-ID: <87d39kxy4j.fsf@gmail.com> (raw)
In-Reply-To: <87pqdll0z4.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 11 Feb 2012 18:43:43 +0100")

Hello,

Achim Gratz <Stromeko@nexgo.de> writes:

> I actually like the ability to split lines with M-RET, especially since
> there doesn't seem to be a sane way to tell org that "yes I want to
> split the line this time".  What I want is that "point at EOL" is
> recognized as a special situation, much like "point at BOL" already
> is.

Excepted that, unlike to headlines, EOL is _not_ a special position in
an item. Remember that an headline has to fit on a single line, whereas
an item may span over multiple paragraphs, tables, and even plain lists.

Look at the following example:

#+begin_src org
- first line of the first item

  another paragraph in the item

  one last paragraph

- second item
#+end_src

If I use M-RET with point between "first" and "item", I get ("|" being
the point):

#+begin_src org
- first line of the first

- |item

  another paragraph in the item

  one last paragraph

- second item
#+end_src

If I use M-RET with point a word further, that is after "item",
I logically have:

#+begin_src org
- first line of the first item

- |

  another paragraph in the item

  one last paragraph

- second item
#+end_src

It will be the same if I use M-RET before "another". I can also go on
with point after "another":

#+begin_src org
- first line of the first item

  another

- |paragraph in the item

  one last paragraph

- second item
#+end_src

It is very predictable, isn't it?

On the other hand, it isn't consistent to allow, at every EOL in the
item, to jump below contents and add a new item there.

Now, perhaps the variable's name is misleading, as it isn't really about
splitting lines, which make no sense in items, but splitting contents.

Note that you can easily obtain what you want with M-RET M-DOWN at
beginning of item, or even write a function to do with even less
keystrokes.


Regards,

-- 
Nicolas Goaziou

      parent reply	other threads:[~2012-02-12  8:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 20:40 [feature request] org-insert-heading Achim Gratz
2012-02-11  9:23 ` Nicolas Goaziou
2012-02-11 17:43   ` Achim Gratz
2012-02-11 18:00     ` Bernt Hansen
2012-02-11 18:17       ` Achim Gratz
2012-02-12  8:19     ` Nicolas Goaziou [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:
  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=87d39kxy4j.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=Stromeko@nexgo.de \
    --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).