From: Scott Otterson <scotto@u.washington.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Release 5.22 (Carsten Dominik
Date: Tue, 19 Feb 2008 10:02:40 -0800 [thread overview]
Message-ID: <47BB19C0.2050508@u.washington.edu> (raw)
In-Reply-To: <200802191705.m1JH5qll027622@bp34.u.washington.edu>
Carsten Dominik wrote:
> - M-RET no longer brakes a line in the middle, it will make a
> new line after the current or (if cursor is at the beginning
> of the line) before the current line.
>
I there a way to restore the old M-RET behavior?
I use it all the time when brainstorming: Often, when I see that the
headline I'm typing is getting too complicated, I find that it needs to
be broken into sub topics -- easy to do when you can walk the cursor
through the headline and break it up with M-ret.
Suppose I've typed:
* Danish Bakfietsen: extended front wheel centers mass, adds steering
linkage, cost, handling?
This is too long, and I have more info to add. After a couple of
M-ret's and M-right arrows, I have:
* Danish Bakfietsen
** extended front wheel centers mass
** adds steering linkage, cost, handling?
I realize that I will have a lot to say about cost and handling, so I
M-ret again:
* Danish Bakfietsen
** extended front wheel centers mass
** adds steering linkage,
*** cost,
*** handling?
For me, one of the biggest org mode strengths is how quickly you can map
out a thought and then reorganize with a few quick keystrokes -- the old
M-ret behavior is just one example. Based on listserv traffic, it
sounds like most people use org mode for task tracking and GTD, so maybe
my usage scenario is too outside of the mainstream, but still, I really
liked M-ret the way it was.
Keep up the good work,
Scott
next parent reply other threads:[~2008-02-19 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200802191705.m1JH5qll027622@bp34.u.washington.edu>
2008-02-19 18:02 ` Scott Otterson [this message]
2008-02-19 18:33 ` Re: Release 5.22 (Carsten Dominik Nick Dokos
2008-02-19 19:17 ` Raimund Kohl-Füchsle
2008-02-19 19:45 ` Carsten Dominik
2008-02-20 11:04 ` Phil Jackson
2008-02-20 11:25 ` Detlef Steuer
2008-02-20 11:29 ` Phil Jackson
2008-02-20 11:44 ` Bastien
2008-02-20 12:20 ` Carsten Dominik
2008-02-22 11:13 ` Carsten Dominik
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=47BB19C0.2050508@u.washington.edu \
--to=scotto@u.washington.edu \
--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).