[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[O] Behaviour of org-open-at-point and org-return (was commit 4e864643 b
From: |
Stefan-W. Hahn |
Subject: |
[O] Behaviour of org-open-at-point and org-return (was commit 4e864643 breaks org-return) |
Date: |
Sun, 25 Oct 2015 17:41:26 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Mail von Stefan-W. Hahn, Sat, 24 Oct 2015 at 08:48:47 +0200:
Hello,
as I observed there is a change in behaviour of org-return from on
commit 4e864643bdb6bba3e000ea51fb746a26e40b1f77
Author: Nicolas Goaziou <address@hidden>
Date: Sun Oct 18 09:36:15 2015 +0200
for timestamps, date ranges and any link.
The same change of behaviour was done for org-open-at-point from on
commit d75fa9febc676af4893fba9e4d53d5babbb801aa
Author: Nicolas Goaziou <address@hidden>
Date: Sun Mar 2 10:32:51 2014 +0100
for timestamp, any link and footnote-reference (perhaps other I'm not sure).
For example of a link:
[[link][description]]x
If cursor was at position x the old behaviour of org-return (hitting <RET>)
was to open a new line, and position the cursor at the beginning of the new
line. The old behaviour of org-open-at-point was to say "no link".
For me this seems consistent because if you go with the cursor over
position x you see no hint and mouse-click do nothing. You have to go
over the link to see face changing and be able to mouse-click top follow
the link.
Additonally description of org-open-at-point say "... When point is on a
link, follow it....", not "on or after".
Also if you insert a link by yanking or org-insert-link cursor is positioned
directly after inserted link, cursor pos x s.o. With old behaviour you can
behaviour you can straight hit <RET> to get a newline. With new behaviour
you have to add space before <RET> or call open-line and position the
cursor.
For me the new behaviour seems inconsistend itself because everytime
I want to get a new line I noew have to check if cursor is positioned
right after a timestamp, or link. Or I have to shutoff org-return-follows-link.
Are there any other org'ers with opinions about this behaviour?
I'm really interested in your and others opinion about this behaviours
before building some workarounds for me personally. (Perhaps I have overseen
something in the big pictures?)
With kind regards,
Stefan
P.S. Excue me if not being subtle enough, its difficult to me beeing subtle
in a foreign language.
--
Stefan-W. Hahn It is easy to make things.
It is hard to make things simple.