emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Steen Hoyer <j.s.hoyer@wustl.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Radio targets in comment lines
Date: Thu, 22 Aug 2013 10:56:41 +0200	[thread overview]
Message-ID: <87ioyyxfw6.fsf@gmail.com> (raw)
In-Reply-To: <35822ACE-C595-4215-9BD6-613048F1691C@wustl.edu> (Steen Hoyer's message of "Wed, 21 Aug 2013 18:05:24 -0500")

Hello,

Steen Hoyer <j.s.hoyer@wustl.edu> writes:

> Org 8 seems to have changed the way radio links in comment lines work.
>
> # <<<target>>> No longer creates a link - 'C-c C-c can do nothing useful at this location'
>
> #+test <<<target>>> Works within org for some reason, but then the line will be exported...
>
> I was curious if this was intentional,

This is intentional. No Org syntax is recognized in a comment anymore.
On the other hand, all targets (not radio targets) are invisible now.
Therefore, you can write:

  Some text<<invsible>> in a paragraph.

And "invisible" (note the double brackets) will not appear during
export.

"#+test <<<target>>>" has wrong syntax since the colons are mandatory:
"#+test: <<<target>>>". It will not be exported (as a keyword), but it
cannot hold radio targets (or targets) either.

> because I have many (now broken) links of the first kind in my org
> files, and because of this line in the org FAQ: "The usual way of
> turning radio links invisible is to comment them,"

FAQ is not up-to-date. Also, note that there is a confusion between
targets (double brackets) and radio targets (triple brackets). There is
no point in making radio targets invisible. There is also no need for
the (INVISIBLE) hack anymore.

Patches welcome wrt the FAQ.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-08-22  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 23:05 Radio targets in comment lines Steen Hoyer
2013-08-22  8:56 ` Nicolas Goaziou [this message]
2013-08-22 14:16   ` Steen Hoyer
2013-08-22 18:40     ` 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=87ioyyxfw6.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=j.s.hoyer@wustl.edu \
    /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).