emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Fabrice Popineau <fabrice.popineau@gmail.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Links
Date: Tue, 16 Jun 2015 15:32:28 +0200	[thread overview]
Message-ID: <CAFgFV9PkeQZQ=DMGivWj892cQbiL_3LqFbmJ0xcn18JE1o44SQ@mail.gmail.com> (raw)
In-Reply-To: <87wpz3akc4.fsf@selenimh.access.network>

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

2015-06-16 14:50 GMT+02:00 Nicolas Goaziou <mail@nicolasgoaziou.fr>:

> Hello,
>
>
> So, export process doesn't url-decode links, and cannot handle the link
> above.


This is what I was missing :-)


> At this point, it seems that all is left are cheesy approaches. E.g,
> when a path matches "%[A-Za-z0-9]\\{2\\}", decode it during export. This
> leaves pathological cases (e.g., when you really meant, for some very
> good reason, to have a headline called "* %25"), though. That's not
> great either.
>
> WDYT?
>

I don't know what is realistic. I see the tradeoffs are tight.

Ideally, url encoded links should have been prefixed with some kind of uri
syntax.
This way, you could know what to decode and what not.

Now, I guess the heuristic you propose would be fine in most cases.
I don't see that people will put a lot of percentages in their links.

Thanks for the explanations !

Fabrice


> Regards,
>
> --
> Nicolas Goaziou
>

[-- Attachment #2: Type: text/html, Size: 1791 bytes --]

next prev parent reply	other threads:[~2015-06-16 13:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 12:11 Links Fabrice Popineau
2015-06-16 12:50 ` Links Nicolas Goaziou
2015-06-16 13:32   ` Fabrice Popineau [this message]
2015-06-16 21:30     ` Links Nicolas Goaziou
2015-06-17  6:44       ` Links Suvayu Ali
2015-06-17  9:47         ` Links Nicolas Goaziou
2015-06-18 23:41           ` Links Suvayu Ali

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='CAFgFV9PkeQZQ=DMGivWj892cQbiL_3LqFbmJ0xcn18JE1o44SQ@mail.gmail.com' \
    --to=fabrice.popineau@gmail.com \
    --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

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).