From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Luciano Passuello <lucianop@litemind.com>
Cc: emacs-orgmode@gnu.org, Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: Insert heading above current one
Date: Sat, 30 Sep 2017 22:21:46 +0200 [thread overview]
Message-ID: <87wp4gj5t1.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CACqKfLc4RxZ3-kVRyza_sv7s34DFc4kxFWD=CGMr6zu8E8E=TQ@mail.gmail.com> (Luciano Passuello's message of "Sat, 30 Sep 2017 17:02:02 -0300")
Luciano Passuello <lucianop@litemind.com> writes:
> Isn't that consistent with the regular org-insert-heading (M-RET)?
> When cursor is in the beginning of a headline, there's no way to
> create a heading below that line (using standard M-RET). It will
> always create it above. So, having the cursor in the beginning of the
> line overrides the standard behavior. Unless we move the cursor
> somewhere else, that feature is also lost.
Sorry, but this makes no sense. You want to insert a headline above
current one? Use M-RET. You want it below current headline? Use C-RET.
You have the best of both worlds, any behaviour is still available to
your fingertips.
> I see no reason why C-RET should behave differently, even if only for
> consistency reasons.
I do see reasons, and I explained them. M-RET and C-RET/C-u M-RET are
different beasts, just don't expect them to behave exactly the same.
I stand on my ground: current behaviour is better.
Regards,
next prev parent reply other threads:[~2017-09-30 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 14:12 Insert heading above current one Luciano Passuello
2017-09-29 14:41 ` Kaushal Modi
2017-09-29 14:46 ` Kaushal Modi
2017-09-29 19:55 ` Nicolas Goaziou
2017-09-29 22:58 ` Luciano Passuello
2017-09-30 7:29 ` Nicolas Goaziou
2017-09-30 20:02 ` Luciano Passuello
2017-09-30 20:21 ` Nicolas Goaziou [this message]
2017-09-30 20:50 ` Luciano Passuello
2017-09-30 10:47 ` Rasmus
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=87wp4gj5t1.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=lucianop@litemind.com \
/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).