emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: [POLL] Do you need special entities in radio target?
Date: Sun, 23 Mar 2014 08:26:49 +0100	[thread overview]
Message-ID: <m2k3blwf2e.fsf@uio.no> (raw)
In-Reply-To: <87bnwyo5jm.fsf@gmail.com>


Nicolas Goaziou writes:
> Christian Moe <...> writes:
>
>> But is this only about special entities, or about all Org syntax,
>
> the latter.

Thanks for clarifying.

>> including subscripts/superscripts, emphasis...? That would be
>> limiting. As long as radio targets are visible parts of the text, I'd
>> like them to continue supporting such markup.
>
> So far, radio targets only support entities, subscript and superscript.
> Emphasis is not supported. I don't think it's a limitation, though,
> because radio targets can be contained within emphasis markup.

Sorry, I overlooked that. So both under the status quo and under the
proposed change, emphasis is possible. Mixed emphasis/non-emphasis
within the target (e.g. <<<creation /ex nihilo/>>>) is not supported in
either case, so the change would not further limit use of emphasis.

It would be nice to keep support for subscripts and superscripts,
though. One might want to use, say, "CO_2" in a radio target.

But this is not a pressing concern on my part, since I don't rely on
radio targets for anything very important anyway.

Yours,
Christian

      reply	other threads:[~2014-03-23  7:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 21:38 [POLL] Do you need special entities in radio target? Bastien
2014-03-21 21:41 ` Samuel Wales
2014-03-22  9:31 ` Christian Moe
2014-03-22 11:07   ` Nicolas Goaziou
2014-03-23  7:26     ` Christian Moe [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

  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=m2k3blwf2e.fsf@uio.no \
    --to=mail@christianmoe.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@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).