From: Carsten Dominik <carsten.dominik@gmail.com>
To: David Maus <dmaus@ictsoc.de>
Cc: "Cook, Malcolm" <MEC@stowers.org>,
"'emacs-orgmode@gnu.org'" <emacs-orgmode@gnu.org>
Subject: Re: link export confused when URL parameter is another URL
Date: Thu, 21 Oct 2010 19:38:17 +0200 [thread overview]
Message-ID: <57618952-F767-4DCC-8C75-E71DE28FF254@gmail.com> (raw)
In-Reply-To: <87mxq888o1.wl%dmaus@ictsoc.de>
On Oct 21, 2010, at 6:35 AM, David Maus wrote:
> 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.
This is a bit hard without lookbehind assertions as they are available
in perl. For something like this it is somtimes easier to just to
the normal match you wanted to use anyway and then confirm by
taking a separate look at the text before the match
which is, for example,
(buffer-substring (point-at-bol) (match-beginning 0))
HTH
- Carsten
next prev parent reply other threads:[~2010-10-21 17:38 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
2010-10-21 13:37 ` Cook, Malcolm
2010-10-21 17:38 ` Carsten Dominik [this message]
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=57618952-F767-4DCC-8C75-E71DE28FF254@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=MEC@stowers.org \
--cc=dmaus@ictsoc.de \
--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).