Re: Behaviour of org-open-at-point and org-return (was commit 4e864643 breaks org-return)

[Nicolas Goaziou <mail@nicolasgoaziou.fr>]

Hello

"Stefan-W. Hahn" <stefan.hahn@s-hahn.de> writes:

> as I observed there is a change in behaviour of org-return from on
>
> commit 4e864643bdb6bba3e000ea51fb746a26e40b1f77
> Author: Nicolas Goaziou <mail@nicolasgoaziou.fr>
> 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 <n.goaziou@gmail.com>
> 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.

Fixed in both `org-return' and `org-open-at-point'. Thank you.

Regards,

-- 
Nicolas Goaziou