Rasmus ras...@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
Le 23/11/2014 00:20, Nicolas Goaziou a écrit :
M-RET, is, first and foremost, an important keybinding for editing the
/structure/ of the document. The behaviour you want to add has nothing
to do with structure.
I guess this is the main decision point about Rasmus's proposal.
I'm not sure I
Hello,
Thierry Banel tbanelweb...@free.fr writes:
I'm not sure I understand the /structure/ argument. (Is structure
about hiding blocks? Parsing org docs?).
Nicolas, you have worked a lot on this topic (org-element, new drawer
syntax). May be you could elaborate on this.
M-RET, C-RET are
Hi,
Thanks for the comments.
This email is long (sorry); fortunately there are many blank lines. . .
Thierry Banel tbanelweb...@free.fr writes:
If not, maybe it would be better to keep the oriGiNaL cASe.
Yeah, fixed.
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Rasmus ras...@gmx.us
Hi,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Thierry Banel tbanelweb...@free.fr writes:
I'm not sure I understand the /structure/ argument. (Is structure
about hiding blocks? Parsing org docs?).
Nicolas, you have worked a lot on this topic (org-element, new drawer
syntax). May be you
Rasmus ras...@gmx.us writes:
I see it differently. I see M-RET as a function that magically adds
more of what is adjacent to point.
Your definition is fuzzy:
* Headline
[lots of text]
-- M-RET here will insert a headline, which is by no mean adjacent to point.
I—obviously—think
Rasmus ras...@gmx.us writes:
I don't find it complicated at all. . . It's DWIM!
I understand your DWIM argument. But we're talking about one of the most
central keybindings in Org, much like C-c C-c. Except I do not consider
C-c C-c as a usability model. Also, C-c C-c is not really dedicated
Hi,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
I—obviously—think what I propose is better than what we have now. Let's
go through the current functionality.
In this case I value simplicity over complexity (or smartness,
whatever you call it). Anyone, including newcomers, should be able
Rasmus ras...@gmx.us writes:
Newcomers ain't stupid.
I never said that.
However, here is an historical data point. SCHEDULED, DEADLINE and
CLOSED keywords, aka planning info, are not included as properties in
properties drawer so newcomers do not encounter invisible contents for
such basic
Hi,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Still, I think overload M-RET is more intuitive,
Intuitiveness is in the eye of the beholder...
Clearly.
Maybe some users will not find intuitive that M-RET usually inserts a
headline... unless it is in a plain list, in which case it
Hello,
Rasmus ras...@gmx.us writes:
Attached is a new version of the patch that will respect the variables
that also govern `org-insert-headline'. It's smarter and preserves the
layout better.
Thanks for the patch. However there are already mechanisms to complete
keywords faster (e.g.,
Hi,
Thanks for the comments.
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Rasmus ras...@gmx.us writes:
Attached is a new version of the patch that will respect the variables
that also govern `org-insert-headline'. It's smarter and preserves the
layout better.
Thanks for the patch.
Hi,
First, Thierry, I think this patch fixes the second misbehavior you
observed.
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
I looked through your comments and as always they made the patch much
better! Thanks!
Moreover, it can get in the way of expected M-RET behaviour, as in the
Le 22/11/2014 20:26, Rasmus a écrit :
Hi,
First, Thierry, I think this patch fixes the second misbehavior you
observed.
Fixed!
I was wondering, is there any reason why the new inserted keyword is
UPPERCASED?
If not, maybe it would be better to keep the oriGiNaL cASe.
Rasmus ras...@gmx.us writes:
Moreover, it can get in the way of expected M-RET behaviour, as in the
following example
- item
| #+caption: test
untenrsiu
I don't know if I should do something about this case. I guess it would
be possible, but I find it awkward when behavior
Hi,
Rasmus ras...@gmx.us writes:
Something I have wanted for a while is to have M-RET work as
expected(?) on keyword lines such as #+LATEX_HEADER, #+CAPTION etc.
[...]
Attached is a quick patch that works surprisingly well. I would work
more on it if you guys agree this would be useful.
16 matches
Mail list logo