From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: [BUG] org-mode 8.3.x directly opens URL/ follows Timestamp, if Return is clicked Date: Mon, 30 May 2016 10:11:23 -0500 Message-ID: <8760tvd1ic.fsf@fastmail.fm> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33139) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b7Or3-0002LW-41 for emacs-orgmode@gnu.org; Mon, 30 May 2016 11:11:46 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b7Oqx-0003uw-1o for emacs-orgmode@gnu.org; Mon, 30 May 2016 11:11:43 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:43697) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b7Oqu-0003ql-MR for emacs-orgmode@gnu.org; Mon, 30 May 2016 11:11:38 -0400 In-Reply-To: (Martin Beck's message of "Mon, 30 May 2016 14:42:35 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Martin Beck Cc: emacs orgmode-mailinglist "Martin Beck" writes: > I recently upgraded from org-mode 8.2.x to org-mode 8.3.4 and > all-in-all, it worked really great without too many side effects. > Thanks to all of you who contributed and made it such a robust > upgrade. :-) > > However, there is one change that is annoying for me every time I > want to enter a linebreak after a Link, URL or timestamp: > > When I move the cursor after a Link, URL or timestamp and hit return, > it follows the link and opens the URL or jumps to the date of the > timestamp in an agenda view. > I can change that by first entering a space after the link, but I > often forget that and it's not a really robust workaround for me. > > So I wonder how/when this change happened and if I maybe can get the > old behavior back? > This bug was fixed on October 31, 2015 with the following commit: a87c34cb8d58e7019c8d081c02bbac9e93cef8ab Unfortunately, that commit must have been applied only to the master branch, as it is not present in the maint branch and thus was not released as part of org-mode 8.3.4. I'm not sure why that commit was never merged into maint. I'm flagging this as a bug to ensure that it is merged. I think the only solution at the moment would be to upgrade to a more recent development version either by checkout org out through git or using elpa: http://orgmode.org/elpa.html Matt