emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Brand <michael.ch.brand@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Cc: sindikat <sindikat@mail36.net>
Subject: Re: M-RET and C-RET
Date: Fri, 2 Dec 2011 17:13:22 +0100	[thread overview]
Message-ID: <CALn3zogYj2+U5FtkDeXQxoHByoyL76eb8AoSG_a_dLuqUAtXbA@mail.gmail.com> (raw)
In-Reply-To: <20111126195304.61776.qmail@rage.so36.net>

Hi all

Now that I use M-RET more often when editing lists I was about trying
to make a patch to remove what seems to me an inconsistency between
headings and list items. But after I have read the docstrings of
org-insert-item and org-list-insert-item the current behavior seems so
intentional that I must have just missed some good reasons. Which are
they?

With

#+begin_src org
  ,*** abc
  ,*** def
  ,    - ghi
  ,    - jkl
#+end_src

M-RET on "e" or on "k" splits the line, ok. M-RET on the first "*"
(here also C-RET) or on "-" inserts a line above, ok. M-RET on "d"
inserts a line _below_ (and C-RET _below_ the end of the whole entry),
ok. M-RET on "j" inserts a line above but I expected it below. If I
want a line above I would move the point to "-" before doing M-RET
like I do on a heading where I move to the first "*" to get the insert
above.

Changing to the behavior expected by me would make it possible to add
a new list item below the last one in a list (a very frequent task)
without caring about configuring org-M-RET-may-split-line away from
its default. I configured it to nil for headline and item only to be
able to insert a new list item below the current with M-RET where I am
forced to be on or at right of "k" which by default splits which I
want only in very rare cases. And one should not be invited to avoid
M-RET and edit lists with "-" and TAB as illustrated in the thread
"org-list-indent-offset only works partially":
http://thread.gmane.org/gmane.emacs.orgmode/47954

Another inconsistency in my view: Since M-RET inserts above when on
"-" or before I would like to see M-RET and C-RET also insert above
when on the last "*" (or single visible "*" when hidestars) or before,
not only on the first "*" of the line.

Michael

On Sat, Nov 26, 2011 at 20:53, sindikat <sindikat@mail36.net> wrote:
>> You can use M-RET-may-split-line, to make it respect content in lists,
>
> more or less. I would guess the reason that they are different is to be
> able to always easily start a new heading.
> This is very helpful, thank you. But how to make it so M-RET will:
> 1. not split line;
> 2. add new list item while on plain list;
> AND
> 3. add new heading after content of the current heading?
> Maybe there should be a variable in addition to 'org-M-RET-may-split-line'
> such as 'org-M-RET-add-after-content'.
> [...]

  reply	other threads:[~2011-12-02 16:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26 19:53 M-RET and C-RET sindikat
2011-12-02 16:13 ` Michael Brand [this message]
2011-12-03 10:24   ` Nicolas Goaziou
2011-12-03 16:58     ` Michael Brand
2011-12-04 10:33       ` Nicolas Goaziou
2011-12-04 21:38         ` Michael Brand
2011-12-05 17:23   ` Greg Troxel
  -- strict thread matches above, loose matches on Subject: below --
2011-11-25 16:49 sindikat
2011-11-26  6:08 ` Tom Prince

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=CALn3zogYj2+U5FtkDeXQxoHByoyL76eb8AoSG_a_dLuqUAtXbA@mail.gmail.com \
    --to=michael.ch.brand@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sindikat@mail36.net \
    /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).