From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Joe Corneli <holtzermann17@gmail.com>
Cc: Org-mode mailing list <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: Fri, 21 Apr 2017 09:04:31 +0200 [thread overview]
Message-ID: <87tw5i44xs.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAN+qof=szt8w3161OCNBS2M3xN5hikHRgt7vOYQD_bLkF-VALg@mail.gmail.com> (Joe Corneli's message of "Fri, 21 Apr 2017 00:02:53 +0100")
Hello,
Joe Corneli <holtzermann17@gmail.com> writes:
> The (xxx) form for a link target, especially one outside of a block,
> doesn't seem to have meaning within the document model that Org
> understands.
Of course it does. It belongs to the link syntax. See, for example
`org-link-search' docstring. It could, however, be more visible in the
manual. In particular, it could be emphasized in both (info "(org)
Internal links") and (info "(org) External links"). Patch welcome !
> But I still think there is a legitimate bug report here, since the
> behaviour is not likely to be expected by the user.
Only if the user doesn't know about the syntax, which shouldn't happen
if the manual was great.
> Someone in my position has no interest in code refs, I was only trying
> to link to a bit of text in the buffer. Saying "oh but you can't link
> to this *one* kind of text" is perhaps a fair move. On the other hand,
> given that "following a link" just means "run a search process", that
> search process *could* be smart enough to notice that "no coderef was
> found, maybe the user meant to link to some plain text in
> parentheses". Then I wouldn't see an error.
But then, you wouldn't catch real, but mis-typed, coderef links. At
least, the error tells you something is wrong in the link syntax,
without creating false positives. So, I don't think this would be a net
gain overall.
Note that the same happens if your regular search text starts with an
asterisk. Org will understand you're looking after headlines only, which
may not be what you want. Ditto with the hash sign.
Org has some syntax for links, you need to know about it if you don't
want to get bitten. Hopefully, the manual could help you about it.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2017-04-21 7:04 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
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 [this message]
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=87tw5i44xs.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.