all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Carsten Dominik <dominik@uva.nl>
Cc: org-mode list <emacs-orgmode@gnu.org>
Subject: Re: Problems with opening a link
Date: Sat, 01 Apr 2017 14:16:16 +0200	[thread overview]
Message-ID: <87lgrkmigf.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CADn3Z2LCROE2qtUP2AX0auhWnxcSyhssGXSWtyLpppnXQWnuVg@mail.gmail.com> (Carsten Dominik's message of "Sat, 1 Apr 2017 10:57:33 +0200")

Hello,

Carsten Dominik <dominik@uva.nl> writes:

> but I think the entire url quoting scheme in Org might deserve another
> look.

It does. I also suggested to think about it some time ago.

Ideally, Org should never quote any URI whatsoever. This is really the
root of all evil, because you never know if characters are escaped, and,
as a consequence, you never really know how many un-escaping turns are
required.

Unfortunately, there are a couple of forbidden characters in link
syntax, namely "[", "]", and multiple consecutive spaces. So, if we want
to allow those in, e.g. file names or labels ("http" URL are not
a problem since you can hex-encode them), we need some kind of escaping
mechanism.

In any case, it should be different than hex-encoding so we can tell if
there is some Org specific escaping involved.

Just some data to keep the ball rolling.

Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2017-04-01 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31  9:39 Problems with opening a link Carsten Dominik
2017-03-31 12:05 ` Peter Davis
2017-03-31 12:22 ` Scott Randby
2017-03-31 12:52   ` Carsten Dominik
2017-03-31 14:30     ` Tim O'Callaghan
2017-03-31 17:02       ` Matt Lundin
2017-03-31 16:04     ` Scott Randby
2017-03-31 17:54 ` Matt Lundin
2017-04-01  8:57   ` Carsten Dominik
2017-04-01 12:16     ` Nicolas Goaziou [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lgrkmigf.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=dominik@uva.nl \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.