From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: M-RET vs C-RET
Date: Tue, 25 Nov 2014 12:16:13 +0100 [thread overview]
Message-ID: <87y4qz7coy.fsf@gmx.us> (raw)
In-Reply-To: 86bnnvfv1l.fsf_-_@example.com
Hi,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Rasmus <rasmus@gmx.us> writes:
>
>> From my point of view, we can make every function tied to M-RET beyond
>> `org-insert-headline' configurable and turned off by default. This may,
>> however, also add confusion ("why did M-RET work in X's Org but not in
>> mine...").
>
> In this case, S-RET is a superior (as in less confusing) choice.
I see. That's probably OK.
> Anyway, I assume M-RET on keywords is just a first step. So, what's the
> big picture? I think it would help to know the complete specifications
> of the M-RET you envision, as it could make more sense than the sum of
> its parts.
You're the architect. I just submit an occasional patch or bug-fix
(under much guidance).
I don't have a grand vision, but, ideally, I'd want M-RET to "do the
right thing", which is my book is often create an element similar to
element at point, and is certainly not but my #+begin_src emacs-lisp
code on a headline. I agree the logical action is to the eye of the
beholder. To me, some elements have a very clear-cut "next logical
thing" (item, headline, white space (headline), some keywords, maybe
tables), others don't (e.g. src-blocks and export blocks.). IMO, we can
disable most of element-actions (literately keywords and tables) out of
the box, much like e.g. `scroll-left'.
Sebastien Vauban <sva-news@mygooglest.com>
writes:
> Having such a file:
>
> ** TODO Research
> - [...]
> - Elevator pitch|
>
> Check out with Laura...
>
> Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod
> [...]
>
> If I want to cut the task into 2 at the point of the cursor (vertical
> bar, after "pitch"), I thought doing M-RET or C-RET were the way to go.
Here's another of my pet-griefs
- a
- b
| → M-RET will give me an itme
| → M-RET will give me a headline
Why is the behavior a function of amount of whitespace/newlines to
nearest element? This makes not sense to me and goes against what I
want, namely act in accordance to element at point. . .
—Rasmus
--
Need more coffee. . .
next prev parent reply other threads:[~2014-11-25 11:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 14:41 [Prelim. patch] extend org-meta-return to keywords Rasmus
2014-11-22 1:23 ` [patch] " Rasmus
2014-11-22 9:52 ` Nicolas Goaziou
2014-11-22 12:19 ` Rasmus Pank Roulund
2014-11-22 19:26 ` Rasmus
2014-11-22 21:57 ` Thierry Banel
2014-11-22 23:20 ` Nicolas Goaziou
2014-11-23 11:08 ` Thierry Banel
2014-11-23 16:54 ` Nicolas Goaziou
2014-11-23 17:15 ` Rasmus
2014-11-23 17:54 ` Nicolas Goaziou
2014-11-23 18:11 ` Rasmus
2014-11-23 21:13 ` Nicolas Goaziou
2014-11-23 21:54 ` Rasmus
2014-11-25 9:00 ` Nicolas Goaziou
2014-11-25 10:12 ` M-RET vs C-RET Sebastien Vauban
2014-11-25 11:09 ` Nicolas Goaziou
2014-11-25 11:16 ` Rasmus [this message]
2014-11-26 23:50 ` Nicolas Goaziou
2014-11-27 0:55 ` Rasmus
2014-11-27 9:19 ` Andreas Leha
2014-11-23 17:00 ` [patch] extend org-meta-return to keywords Rasmus
2014-11-23 17:46 ` Nicolas Goaziou
2014-11-22 13:53 ` [Prelim. patch] " Thierry Banel
2014-11-22 14:31 ` Rasmus
2014-11-22 17:09 ` Thierry Banel
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=87y4qz7coy.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).