From: Leonard Randall <leonard.a.randall@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: York Zhao <gtdplatform@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: (org-insert-headline '(4)) should insert new headline before point
Date: Wed, 23 Apr 2014 22:42:43 +0100 [thread overview]
Message-ID: <CAMRQoAkE3AbaK-UJnqrR45qLJafL2-fhEkbJfZfgb5qr3dS8_A@mail.gmail.com> (raw)
In-Reply-To: <87zjjdafa3.fsf@bzg.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]
Hi Bastien,
I just wanted to report an issue with this fix. In many use cases it makes
C-RET less useful, and renders the speedkeys command `i' useless. It makes
C-RET function much like M-RET, and it makes `i' insert headlines before
any content.
So if I call C-RET in the middle of the following headline:
---
** Important Meeting
SCHEDULED: <2014-04-26 Sat 16:30>
headline content...
---
I get:
---
** Important
** Meeting
SCHEDULED: <2014-04-26 Sat 16:00>
headline content...
---
And when I use the speedkeys command `i' at the beginning, I get
---
** Important Meeting
**
SCHEDULED: <2014-04-26 Sat 16:00>
headline content...
---
Both of these break the scheduling cookie and defeat the main purpose of
these commands.
Reverting the change restores expected behavior in these cases, but then I
suppose we are left with York's problem.
All best,
Leonard
On 22 April 2014 10:23, Bastien <bzg@gnu.org> wrote:
> Hi York,
>
> thanks for coming back to this.
>
> York Zhao <gtdplatform@gmail.com> writes:
>
> > What I meant was that with one prefix argument, the command
> > `org-insert-heading' should insert a new heading *before* the
> > current heading, not after.
>
> Actually, this has little to do with the prefix argument: when
> at the beginning of a heading or a list item, M-RET should add
> a new heading/item *before* the current heading/item.
>
> This is fixed now, thanks for reporting this,
>
> PS: Using C-u M-RET will force `org-insert-heading-respect-content'
> to `t', i.e. add the headline at the end of the subtree. As Nicolas
> noted, this is the same than C-RET.
>
> --
> Bastien
>
>
[-- Attachment #2: Type: text/html, Size: 2426 bytes --]
next prev parent reply other threads:[~2014-04-23 21:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 22:59 (org-insert-headline '(4)) should insert new headline before point York Zhao
2014-04-05 3:01 ` York Zhao
2014-04-05 6:03 ` Grant Rettke
2014-04-17 14:21 ` Bastien
2014-04-20 20:46 ` York Zhao
2014-04-21 8:39 ` Nicolas Goaziou
2014-04-22 9:23 ` Bastien
2014-04-23 21:42 ` Leonard Randall [this message]
2014-04-23 21:48 ` Leonard Randall
2014-04-25 5:43 ` Eric Abrahamsen
2014-04-25 7:29 ` Bastien
2014-04-25 10:39 ` Leonard Randall
2014-04-29 12:35 ` Bastien
2014-04-29 13:59 ` Leonard Randall
2014-04-29 14:20 ` Bastien
2014-04-30 7:12 ` Leonard Randall
2014-04-30 8:44 ` Bastien
2014-04-30 17:03 ` Leonard Randall
2014-05-04 2:37 ` Leonard Randall
2014-05-21 1:43 ` Bastien
2014-06-02 12:11 ` Leonard Avery Randall
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMRQoAkE3AbaK-UJnqrR45qLJafL2-fhEkbJfZfgb5qr3dS8_A@mail.gmail.com \
--to=leonard.a.randall@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=gtdplatform@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.