From: David Maus <dmaus@ictsoc.de>
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: "'emacs-orgmode@gnu.org'" <emacs-orgmode@gnu.org>
Subject: Re: link export confused when URL parameter is another URL
Date: Thu, 21 Oct 2010 06:35:42 +0200 [thread overview]
Message-ID: <87mxq888o1.wl%dmaus@ictsoc.de> (raw)
In-Reply-To: <BD62CBAC4395B94096109020651BE2EC138628DD3E@EXCHMB-02.stowers-institute.org>
[-- Attachment #1.1: Type: text/plain, Size: 942 bytes --]
At Thu, 30 Sep 2010 15:17:00 -0500,
Cook, Malcolm wrote:
>
>
> If find that this orgtext
>
> [[http://www.foo.com/foo?URL=http://www.bar.com][test]]
>
> exports to html incorrectly as
>
> [[http://www.foo.com/foo?URL=[[http://www.bar.com][test][http://www.bar.com][test]]]
>
> using today's fresh git pull make install
>
> Any pointers?
The problem here is that Org's (legacy) support for plain links
(i.e. without square brackets) kicks in and transforms the fragment
part to a normal square bracket link.
My regexp-foo is not as it should be, but I am on this one to fix it;
What we need to express in `org-export-normalize-link' is, that a
plain link is something that looks like a hyperlink but not preceded
directly by a square or angle bracket and not after a question mark
followed by zero or more no-whitespace-characters.
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de
[-- Attachment #1.2: Type: application/pgp-signature, Size: 230 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-10-21 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 20:17 link export confused when URL parameter is another URL Cook, Malcolm
2010-10-21 4:35 ` David Maus [this message]
2010-10-21 13:37 ` Cook, Malcolm
2010-10-21 17:38 ` Carsten Dominik
2010-10-22 4:28 ` David Maus
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=87mxq888o1.wl%dmaus@ictsoc.de \
--to=dmaus@ictsoc.de \
--cc=MEC@stowers.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).