From: Erik Anderson <erikbpanderson@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Bug: Avoid following link when using org-return-follows-link and point is at end of line [8.3.2 (8.3.2-39-gd537a3-elpaplus @ /home/Erik/.emacs.d/elpa/org-plus-contrib-20151123/)]
Date: Thu, 26 Nov 2015 23:22:29 -0600 [thread overview]
Message-ID: <CAAFf7aw-dXSUPjoszdz+ZV1k0Q23cRjHLgWpo+O1scH+1prSfg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
Not a bug per se, but a tweak to existing behavior which I think most
people would prefer. The option org-return-follows-link is wonderfully
convenient except when the point is at the end of the line where the
intention is usually to insert a carriage return.
http://emacs.stackexchange.com/questions/18433/avoid-following-link-when-using-org-return-follows-link-and-point-is-at-end-of-l
---
lisp/org.el | 1 +
1 file changed, 1 insertion(+)
diff --git a/lisp/org.el b/lisp/org.el
index 8918747..6b9ffb3 100755
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -21326,6 +21326,7 @@ object (e.g., within a comment). In these case,
you need to use
;; `org-return-follows-link' allows it. Tolerate fuzzy
;; locations, e.g., in a comment, as `org-open-at-point'.
((and org-return-follows-link
+ (not (eolp))
(or (org-in-regexp org-ts-regexp-both nil t)
(org-in-regexp org-tsr-regexp-both nil t)
(org-in-regexp org-any-link-re nil t)))
--
2.5.3
Emacs : GNU Emacs 24.5.1 (x86_64-unknown-cygwin)
of 2015-06-23 on desktop-new
Package: Org-mode version 8.3.2 (8.3.2-39-gd537a3-elpaplus @
/home/Erik/.emacs.d/elpa/org-plus-contrib-20151123/)
[-- Attachment #2: Type: text/html, Size: 1753 bytes --]
next reply other threads:[~2015-11-27 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 5:22 Erik Anderson [this message]
2015-11-30 15:04 ` Bug: Avoid following link when using org-return-follows-link and point is at end of line [8.3.2 (8.3.2-39-gd537a3-elpaplus @ /home/Erik/.emacs.d/elpa/org-plus-contrib-20151123/)] Rasmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAFf7aw-dXSUPjoszdz+ZV1k0Q23cRjHLgWpo+O1scH+1prSfg@mail.gmail.com \
--to=erikbpanderson@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).