Re: "No link found" for <return> after <2016-02-21 Sun>

[Josef Atmin <jatmin@web.de>]

Dear Nicolas!

On Tue, Feb 23, 2016 at 11:34:21PM +0100, Nicolas Goaziou wrote:
> Hello,
> 
> Josef Atmin <jatmin@web.de> writes:
> 
> >> when the curser is at the end of the line directly after <2016-02-21 Sun>, i.e. there
> >> comes a newline right after the '>', then typing <return> results in the message "No link
> >> found".  I guess this is a bug.
> 
> This is fixed in development version already (commit
> a87c34cb8d58e7019c8d081c02bbac9e93cef8ab).

Thanks for letting me know.  I guess it will make it to the unstable release soon.

So there remains my wishlist item, namely that typing <return> after a
link results in a newline rather than activation of the link.  I would
find it much better if only a <return> on the link would activate it,
because I am often in the situation where I am at the end of a line
and I want to insert a newline, but because there is a link at the end
of the line right before the curser (not at the cursor), the link is
activated, which is mostly harmless but anoying.  To avoid that, I
have to either first tiype a <space> and then a <return> or first
Ctrl-o and then <right>.  But it is hard for me to always be aware of
the link and change my automatism of simply typing <return>.

I believe that this behavior has actually changed in one of the recent
versions.  Can anybody point me to the discussion in which this change
(to activating the link upon <return> if the curser is behind the
link) was decided, so that I can understand the arguments for this
behavior that I personally don't like.

Best wishes,

Josef.