From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Samuel Loury <konubinix@gmail.com>
Cc: OrgMode ML <emacs-orgmode@gnu.org>
Subject: Re: [BUG] org-open-at-point does not work anymore in comment blocks
Date: Fri, 18 Jul 2014 12:28:26 +0200 [thread overview]
Message-ID: <87vbqvm051.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87vbqvxgq9.fsf@konixwork.incubateur.ens-lyon.fr> (Samuel Loury's message of "Fri, 18 Jul 2014 09:34:38 +0200")
Hello,
Samuel Loury <konubinix@gmail.com> writes:
> On version baa2c5943a4afce71a6336cbd957139e840bd952.
>
> Links are not followed anymore in comment blocks.
>
> You may test it by launching (org-open-at-point) with the cursor into
> the link in the following example.
> * Test #+BEGIN_COMMENT [[http://orgmode.org/]] #+END_COMMENT
>
> It triggers a user error in lisp/org.el at line 10641 since there is no
> computed context.
This is to be expected. Commenting some part of a buffer tells the
parser to ignore it. The only purpose of comments is to deactivate some
syntax (e.g., a link, a timestamp...) in the buffer, which is exactly
what happens here.
If you want to ignore that part only during export, but still want to
use keep it active in the buffer, I suggest to use a drawer, with an
appropriate `org-export-with-drawers' value, e.g.,
#+OPTIONS: d:(not "IGNORE_ME")
:IGNORE_ME:
[[http://orgmode.org]]
:END:
This was discussed before on this ML. Some users made a point that
`org-open-at-point' should process links in node properties. In the case
of comments, though, I think we should be strict and use drawers
instead.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-07-18 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 7:34 [BUG] org-open-at-point does not work anymore in comment blocks Samuel Loury
2014-07-18 10:28 ` Nicolas Goaziou [this message]
2014-07-18 10:35 ` Samuel Loury
2014-07-28 13:42 ` Bastien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbqvm051.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=konubinix@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.