emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ken Williams <Ken.Williams@windlogics.com>
To: Bastien <bzg@gnu.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Subscripts in URLs
Date: Tue, 7 Aug 2012 10:05:38 -0500	[thread overview]
Message-ID: <21A5E1E970CD46459ECBE86D6CC4B28C6732335B@spexch01.WindLogics.local> (raw)
In-Reply-To: <877gtbiqfb.fsf@gnu.org>



From: Bastien Guerry [mailto:bastienguerry@googlemail.com]
>
> Ken Williams <Ken.Williams@windlogics.com> writes:
>
> > and export to HTML, I get a link with anchor text
> >
> http://www.mmm.ucar.edu/events/ISP/presentations/JNTforecastevaluati
> on
> > concepts.pdf, where "forecastevaluationconcepts" is subscripted.  The
> > link *target* is correct, though.
>
> Maybe you have (setq org-export-with-sub-superscripts t) or ^:t in your
> buffer?

Indeed, that seems to be the case.  I do want to be able to use subscripts and other markup in general though, but in a URL like this it seems misplaced.

Maybe we could patch the core code to only process link markup when the author has explicitly given the anchor text?  Otherwise, if I'm linking to an external resource, I don't have control over whatever crazy stuff appears in the URL, and underscores are quite common.

 -Ken


CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of any kind is strictly prohibited. If you are not the intended recipient, please contact the sender via reply e-mail and destroy all copies of the original message. Thank you.

      reply	other threads:[~2012-08-07 15:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 15:58 Subscripts in URLs Ken Williams
2012-08-06 22:52 ` Bastien
2012-08-07 15:05   ` Ken Williams [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=21A5E1E970CD46459ECBE86D6CC4B28C6732335B@spexch01.WindLogics.local \
    --to=ken.williams@windlogics.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    /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).