Rasmus writes:
> The attached patch re-enables breaks in region four of
> org-complex-heading-regexp, i.e. from the cookie up to tags. A quick test
> suggests it works nicely.
Pushed. Let me know if it's worse than before.
Rasmus
--
Need more coffee. . .
Hi Rasmus,
On Mon, May 18, 2015 at 05:39:36PM +0200, Rasmus wrote:
> Suvayu Ali writes:
>
> > As for Rasmus's examples of similar behaviour in other modes, I don't
> > like them either. Unfortunately again, I'm too short on time to fix the
> > behaviour in my setup.
>
> So far nobody has felt
Suvayu Ali writes:
> As for Rasmus's examples of similar behaviour in other modes, I don't
> like them either. Unfortunately again, I'm too short on time to fix the
> behaviour in my setup.
So far nobody has felt strongly enough about this to supply a patch, even
to org.texi or, I think, worg.
On Mon, May 18, 2015 at 06:33:51PM +1000, Brett Witty wrote:
>
> While there can be a bit of a culture shock getting used to org's "do the
> useful thing" as opposed to "do the literal thing", I think it's an
> advantage of the system, not a disadvantage. Headers are sacred in
> org-mode, so break
On 18 May 2015, Brett Witty wrote:
While there can be a bit of a culture shock getting used to org's "do the
useful thing" as opposed to "do the literal thing", I think it's an advantage
of the system, not a disadvantage. Headers are sacred in org-mode, so breaking
headers with RET seems subop
Titus von der Malsburg writes:
> On 2015-05-17 Sun 14:15, Rasmus wrote:
With your behavior you can (i) break the TODO tag; (ii) break the
cookie; (iii) break the tag. At least (i) and (ii) are quite
destructive.
>>>
>>> I am not sure what you mean, since a single undo will alway
Rasmus writes:
> Rainer M Krug writes:
>
>> OK - this makes sense. But instead of jumping to the next line, a
>> splitting of the header into two would make more sense, keeping the
>> correct syntax.
>
> That is literally what my patch does IF you are in region four (more
> or less) of org-comp
Rainer M Krug writes:
> OK - this makes sense. But instead of jumping to the next line, a
> splitting of the header into two would make more sense, keeping the
> correct syntax.
That is literally what my patch does IF you are in region four (more or
less) of org-complex-heading-regexp.
> Jumpin
Brett Witty writes:
> I agree with Rasmus' position. Just because the org format is plain text,
> doesn't mean the Emacs keybindings have to act identically to, say,
> Notepad. Otherwise, what's Emacs for? Similarly, I don't expect TAB to
> insert tabs into an org-mode document.
>
> While there c
I agree with Rasmus' position. Just because the org format is plain text,
doesn't mean the Emacs keybindings have to act identically to, say,
Notepad. Otherwise, what's Emacs for? Similarly, I don't expect TAB to
insert tabs into an org-mode document.
While there can be a bit of a culture shock ge
Titus von der Malsburg writes:
> While that may be a valid solution for some people, it is
> certainly not the Emacs way of doing things.
That's right. It is the Org mode way of doing things in Emacs.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
On 2015-05-17 Sun 14:15, Rasmus wrote:
> Hi Jarmo,
>
> Jarmo Hurri writes:
>
>> Rasmus writes:
>
>>> With your behavior you can (i) break the TODO tag; (ii) break the cookie;
>>> (iii) break the tag. At least (i) and (ii) are quite destructive.
>>
>> I am not sure what you mean, since a single
Hi Jarmo,
Jarmo Hurri writes:
> Rasmus writes:
>> With your behavior you can (i) break the TODO tag; (ii) break the cookie;
>> (iii) break the tag. At least (i) and (ii) are quite destructive.
>
> I am not sure what you mean, since a single undo will always heal the
> line again, regardless o
Rasmus writes:
Greetings Rasmus.
>> I would suggest that the original interpretation of Enter would not
>> be messed with. Messing with Alt-Enter and such is fine, but Enter,
>> please no.
>
> I disagree. Consider the more complete example:
>
> * TODO [#A] foo bar:tag:
>
> With your be
Titus von der Malsburg writes:
> One minor cosmetic issue:
>
> * TODO foo bar :test:
>
> When I RET between foo and bar, the tag moves to the left. I think it
> would be nicer if it would stay where it was.
In the attached patch current colu
On 2015-05-16 Sat 12:00, Rasmus wrote:
> Hi Titus,
>
> Titus von der Malsburg writes:
>
>> just tried the patch and while I still find it weird to change the
>> meaning of RET, this solution doesn’t get in my way as much as the
>> previous solution did.
>
> Try to:
>
> (with-temp-buffer (org-
Hi Titus,
Titus von der Malsburg writes:
> just tried the patch and while I still find it weird to change the
> meaning of RET, this solution doesn’t get in my way as much as the
> previous solution did.
Try to:
(with-temp-buffer (org-mode) (describe-mode)).
A lot of keys have been orgifi
Hi Rasmus,
just tried the patch and while I still find it weird to change the
meaning of RET, this solution doesn’t get in my way as much as the
previous solution did.
One minor cosmetic issue:
* TODO foo bar :test:
When I RET between foo and bar
Hi,
Thanks for the comments.
Nicolas Goaziou writes:
> "RET breaks headline text" may be more accurate.
OK.
>> + (let* ((context (if org-return-follows-link (org-element-context)
>> +(org-element-at-point)))
>> + (type (org-element-type context)))
>> +(cond
>> +
Hello,
Rasmus writes:
> The attached patch re-enables breaks in region four of
> org-complex-heading-regexp, i.e. from the cookie up to tags. A quick test
> suggests it works nicely.
Thank you.
> WDYT?
Some comments follow.
> Subject: [PATCH 2/2] org.el: RET works in headline text
>
> * org
Pressing "enter" in a headline to make a new headline is consistent with
the way many other text-mode outliners have worked in the past. Ctrl-O
to open a line is an Emacs standard keybinding.
I don't really have an issue with the way this works.
--
Bob Newell
Honolulu, Hawai`i
* Sent via Ma Gnu
I like this feature and hope that I can keep it by setting a variable if
changes are made.
All the best,
Tom
Titus von der Malsburg writes:
> I fully agree with this, I find this “feature” very irritating. There
> is a strong expectation that hitting enter inserts a line break
> at the positio
I fully agree with this, I find this “feature” very irritating. There
is a strong expectation that hitting enter inserts a line break
at the position of the cursor. Can we please stick to that?
When I put the cursor in the middle of a word and press enter that also
“breaks” the word. Yet we w
Hi Jarmo,
Jarmo Hurri writes:
> I was just amazed by the following detail in org. In the example below,
> if my cursor is anywhere inside the word "Example", and I press Enter, a
> new line will be inserted below, and the cursor will jump to the next
> line. The location of the cursor inside the
> -Original Message-
> On Behalf Of Jarmo Hurri
> Subject: [O] A Microsoftesque detail in org
>
> ...the software
> tries to be too intelligent, thus making it harder for the user.
Well, phrased. I usually just scream, "DON'T DO ME ANY FAVORS!"
--
,Dou
Jarmo Hurri writes:
> Greetings.
>
> I was just amazed by the following detail in org. In the example below,
> if my cursor is anywhere inside the word "Example", and I press Enter, a
> new line will be inserted below, and the cursor will jump to the next
> line. The location of the cursor inside
Greetings.
I was just amazed by the following detail in org. In the example below,
if my cursor is anywhere inside the word "Example", and I press Enter, a
new line will be inserted below, and the cursor will jump to the next
line. The location of the cursor inside the heading line is ignored, an
27 matches
Mail list logo
