emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 00:12:34 +0200	[thread overview]
Message-ID: <87zifa4tkd.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAN+qofmFC9hs4k64zDOvubCT35Kfsd8vnQ_T8xt0zYqSGa=VAA@mail.gmail.com> (Joe Corneli's message of "Thu, 20 Apr 2017 22:46:29 +0100")

Joe Corneli <holtzermann17@gmail.com> writes:

> In my opinion, capture and/or search should do something different for
> text beginning "(" and ending with ")",  when this text is a link
> target that is not within a code block.

See below.

> The docs say:
>
> "In literal examples, Org will interpret strings like ‘(ref:name)’ as
> labels"
>
> But the text (like this) in my example wasn't inside of a code block,
> nor was it presented as (ref:like this).

There are two syntaxs: the one within the code block, which is (ref:xxx)
by default and can be changed, and the one outside the block, which is
(xxx), and cannot be changed. See the following example from the manual:

     #+BEGIN_SRC emacs-lisp -n -r
     (save-excursion                  (ref:sc)
        (goto-char (point-min)))      (ref:jump)
     #+END_SRC
     In line [[(sc)]] we remember the current position.  [[(jump)][Line (jump)]]
     jumps to point-min.

Regards,

  reply	other threads:[~2017-04-20 22:12 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 [this message]
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

  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=87zifa4tkd.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 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).