From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Joe Corneli <holtzermann17@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: link beginning with parenthesis doesn't work [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)]
Date: Thu, 20 Apr 2017 21:35:51 +0200 [thread overview]
Message-ID: <878tmu6fe0.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <871ssnqjh6.fsf@gmail.com> (Joe Corneli's message of "Thu, 20 Apr 2017 14:53:49 +0100")
Hello,
Joe Corneli <holtzermann17@gmail.com> writes:
> I've noticed a problem with the link system.
>
> Reproduction steps.
>
> 1. Find any text in a file, surrounded by parentheses (like this).
>
> 2. org-capture the region in parentheses to come up with, e.g.,
>
> ** TODO This is a problem
> (like this)
> [[file:~/test.tex::(like%20this)]]
>
> 3. Now try to follow the file:... link with org-open-at-point.
>
> This triggers an error, with a backtrace as follows (between ~~~'s).
>
> If you remove the leading parenthesis so that the link looks like this instead:
>
> [[file:~/test.tex::like%20this)]]
>
> you can then jump to the captured text in the file, as expected.
>
> ~~~
> Debugger entered--Lisp error: (error "No match for coderef: like this")
The error message should give you the answer. Links within parenthesis
denote "coderefs". See (info "(org) Literal examples").
[[file:~/test.tex::(like%20this)]] means to refer to a coderef (like
this) in the file "test.tex".
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-04-20 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 13:53 Bug: link beginning with parenthesis doesn't work [9.0.5 (release_9.0.5-474-g942b62 @ /home/joe/org-mode/lisp/)] Joe Corneli
2017-04-20 19:35 ` Nicolas Goaziou [this message]
2017-04-20 21:46 ` Joe Corneli
2017-04-20 22:12 ` Nicolas Goaziou
2017-04-20 23:02 ` Joe Corneli
2017-04-21 7:04 ` Nicolas Goaziou
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=878tmu6fe0.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=holtzermann17@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.