From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: M-RET and C-RET turn current line of text into a heading?
Date: Thu, 16 May 2013 19:49:54 +0800 [thread overview]
Message-ID: <87mwrvw3dp.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAJcAo8vHqJC_PCAPTR09WzgzoZdE-vUxOQOF=4J8c1KNqnf7fA@mail.gmail.com
Samuel Wales <samologist@gmail.com> writes:
> Hi Eric,
>
> On 5/15/13, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>> I still think it's pretty important to have an option for creating a new
>> headline *below* all the contents of the current subtree -- what C-RET
>> used to do.
>
> This might be a good thing to make a user preference.
>
>> Also, the above provides a whole lot of options for creating a new
>> headline/item above the current line -- is that really such a common
>> thing to do?
>
> It is for me.
>
>> And the variable `org-M-RET-may-split-line' is still not taken into
>> account...
>
> I don't see why it shouldn't be taken into account.
You're right, I guess I just meant it wasn't explicit in your table.
I like the use of double M-RETs, I think that can be useful.
I still think C-RET should create a new heading at the end of the
subtree. A user setting to that effect is fine with me. I'd be happy
if C-RET at the beginning of a heading created a new headline above, but
in the middle or at the end I think it should still jump down and make a
new headline below all content.
Just to register my usage, as a single data point: I make heavy use of
both M-RET to create headings below point (very often to split a single
run of paragraphs into two subtrees), and C-RET to make headings below
subtree text. Very occasionally I use C-u C-u M-RET to make a "bottom
sibling". Very occasionally I use 'C-c *' to toggle heading.
Just two cents.
E
next prev parent reply other threads:[~2013-05-16 11:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 4:58 M-RET and C-RET turn current line of text into a heading? Eric Abrahamsen
2013-05-15 7:54 ` Christian Moe
2013-05-15 8:22 ` Eric Abrahamsen
2013-05-15 9:01 ` Christian Moe
2013-05-15 9:30 ` Eric Abrahamsen
2013-05-20 15:54 ` John Hendy
2013-05-20 16:00 ` John Hendy
2013-05-20 16:14 ` Matt Lundin
2013-05-20 18:41 ` John Hendy
2013-05-15 18:39 ` Samuel Wales
2013-05-16 3:17 ` Eric Abrahamsen
2013-05-16 3:42 ` Samuel Wales
2013-05-16 11:49 ` Eric Abrahamsen [this message]
2013-05-16 7:22 ` Daniel Bausch
2013-05-16 9:21 ` Detlef Steuer
2013-05-16 13:48 ` Rick Frankel
2013-05-16 16:10 ` Eric S Fraga
2013-05-16 6:21 ` Bastien
2013-05-16 9:23 ` Miro Bezjak
2013-05-16 19:11 ` Jason F. McBrayer
2013-05-17 11:20 ` Carsten Dominik
2013-05-17 13:42 ` Jason F. McBrayer
2013-05-17 13:26 ` Carsten Dominik
2013-05-17 19:07 ` Rick Frankel
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=87mwrvw3dp.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).