From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matt Lundin <mdl@imapmail.org>
Subject: Re: Behaviour of org-open-at-point and org-return (was commit
 4e864643 breaks org-return)
Date: Wed, 28 Oct 2015 09:02:04 -0500
Message-ID: <87pozzozvn.fsf@fastmail.fm>
References: <20151022165708.GL12141@scotty.home>
	<20151023200734.GM12141@scotty.home>
	<87twphxlgx.fsf@nicolasgoaziou.fr> <20151024064847.GA14197@pille.home>
	<20151025164126.GC10154@scotty.home>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46548)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mdl@imapmail.org>) id 1ZrRIp-00042f-EA
	for emacs-orgmode@gnu.org; Wed, 28 Oct 2015 10:02:15 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mdl@imapmail.org>) id 1ZrRIk-00021h-LA
	for emacs-orgmode@gnu.org; Wed, 28 Oct 2015 10:02:11 -0400
Received: from out3-smtp.messagingengine.com ([66.111.4.27]:43464)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mdl@imapmail.org>) id 1ZrRIk-00021b-Fr
	for emacs-orgmode@gnu.org; Wed, 28 Oct 2015 10:02:06 -0400
In-Reply-To: <20151025164126.GC10154@scotty.home> (Stefan-W. Hahn's message of
	"Sun, 25 Oct 2015 17:41:26 +0100")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>

"Stefan-W. Hahn" <stefan.hahn@s-hahn.de> writes:
>
> 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.

I can confirm this bug. It affected me when I was trying to enter
scheduling information:

E.g., if I insert the following with org-time-stamp...

<2015-10-28 Wed>
                ^

...the cursor is located after the time stamp (as shown). But if I hit
return to create a new line and enter a new data (text, a time stamp,
etc.), I am taken unexpectedly to the agenda.

Best,
Matt