From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, Jess Balint <jbalint@gmail.com>
Subject: Re: Bug: HTML Export doesn't handle internal link with spaces [8.0.7 (8.0.7-6-g13cb28-elpa @ /home/jbalint/.emacs.d/elpa/org-20130812/)]
Date: Sun, 05 Jan 2014 07:45:18 +0100 [thread overview]
Message-ID: <874n5jvse9.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87r48nmh0i.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 05 Jan 2014 01:03:41 +0100")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> I'm not sure to understand. IIUC, one reason for url-hexification is to
> avoid forbidden characters in Org links, i.e., Org hexifies links to
> escape characters like brackets.
>
> Do you mean using another escape mechanism?
No, I mean to url-hexify URLs that correspond to a link type (through
org-link-types) and for internal links, to escape only [ and ], which
are the only two problematic characters (aren't they?)
> If so, I think the problem
> would be the same as before (impossible to know if link at point was
> escaped or not in the first place).
Yes...
> Another idea would be to get rid of automatic hexification in all cases,
> and have more tolerant regexps for links.
This seems incertain.
Or maybe we can just live with the current problem.
--
Bastien
next prev parent reply other threads:[~2014-01-05 6:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 20:48 Bug: HTML Export doesn't handle internal link with spaces [8.0.7 (8.0.7-6-g13cb28-elpa @ /home/jbalint/.emacs.d/elpa/org-20130812/)] Jess Balint
2013-12-20 21:47 ` Nicolas Goaziou
2014-01-03 14:48 ` Bastien
2014-01-03 15:05 ` Nicolas Goaziou
2014-01-04 14:35 ` Bastien
2014-01-05 0:03 ` Nicolas Goaziou
2014-01-05 6:45 ` Bastien [this message]
2014-01-06 11:32 ` Nicolas Goaziou
2014-01-06 16:36 ` Bastien
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=874n5jvse9.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=jbalint@gmail.com \
--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).