emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Luciano Passuello <lucianop@litemind.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Luciano Passuello <lucianop@litemind.com>,
	emacs-orgmode@gnu.org, Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: Insert heading above current one
Date: Sat, 30 Sep 2017 17:02:02 -0300	[thread overview]
Message-ID: <CACqKfLc4RxZ3-kVRyza_sv7s34DFc4kxFWD=CGMr6zu8E8E=TQ@mail.gmail.com> (raw)
In-Reply-To: <87mv5clk4v.fsf@nicolasgoaziou.fr>

Hello,

On Sat, Sep 30, 2017 at 4:29 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> OTOH, if we force the previous behaviour, as you suggest, there is no
> way to insert a new headline after the current subtree when point is at
> the beginning of a headline. A feature is lost.

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.

I see no reason why C-RET should behave differently, even if only for
consistency reasons.

> And I agree it should be deprecated. If there is no objection, I'll
> remove it.

I'm too much of a n00b to foresee all consequences of such
deprecation, so I prefer not to give my opinion here.
Doing a quick search on "org-insert-heading-respect-content t" I see
some people do find value in it.

Regards,
Luciano.

  reply	other threads:[~2017-09-30 20:03 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 [this message]
2017-09-30 20:21             ` Nicolas Goaziou
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='CACqKfLc4RxZ3-kVRyza_sv7s34DFc4kxFWD=CGMr6zu8E8E=TQ@mail.gmail.com' \
    --to=lucianop@litemind.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=mail@nicolasgoaziou.fr \
    /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).