emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Cannot export a raw link
Date: Mon, 14 Apr 2014 22:06:55 +0200	[thread overview]
Message-ID: <877g6rhe00.fsf@gmail.com> (raw)
In-Reply-To: <87ha5vra6p.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 14 Apr 2014 21:19:10 +0200")

Achim Gratz <Stromeko@nexgo.de> writes:

> groff has this snippet:
>                   (if (file-name-absolute-p raw-path)
>                       (concat "file://" (expand-file-name raw-path))
>                     (concat "file://" raw-path)))

This needs to be fixed, along with ox-man.el. Anyway, that wasn't
introduced with the patch being discussed.

> Well, there's the option of correctly parsing into scheme, authority,
> path, query and fragment...  But that is probably not going into 8.2.6
> in any case.

I don't think we need to completely parse the URI because:

  - we are not going to consume it,
  - Org syntax is not completely compatible with RFC3986 (e.g., search
    options like [[file:test.org::* My headline]]).

I think we need scheme, authority, path+query+fragment, and search
options. At the moment, the parser handles scheme,
authority+path+query+fragment and search options.
`url-generic-parse-url' may help, too.

We also need a function to build back the link, in order to make life of
back-end developers easier. This is why authority is needed.

>> Another one is to drop the whole thing, return to previous state, and
>> implement ad-hoc rules to fix "file:", which is probably the only scheme
>> introducing problems.
> I forgot what the previous state was, but trying to fix file: URIs
> without correctly parsing them sounds like a losing proposition.

Previous state was, in a nutshell, to recognize scheme:blob, which leads
to the same kind of problem since blob may or may not contain the
authority part.


Nicolas Goaziou

  reply	other threads:[~2014-04-14 20:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14  9:18 [BUG] Cannot export a raw link Bastien
2014-04-14 11:16 ` Nicolas Goaziou
2014-04-14 17:07   ` Achim Gratz
2014-04-14 19:10     ` Nicolas Goaziou
2014-04-14 19:19       ` Achim Gratz
2014-04-14 20:06         ` Nicolas Goaziou [this message]
2014-04-16  7:15           ` Nicolas Goaziou
2014-04-16 18:38             ` Achim Gratz
2014-04-17  6:35             ` Bastien
2014-04-17 11:06               ` Nicolas Goaziou
2014-04-17 11:26                 ` Bastien
2014-04-17 19:51                   ` Nicolas Goaziou
2014-04-17 19:56                     ` Bastien
2014-05-03 18:21             ` Michael Brand
2014-05-04 19:43               ` Nicolas Goaziou

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:

  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=877g6rhe00.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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