emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] Cannot export a raw link
Date: Mon, 14 Apr 2014 19:07:07 +0200	[thread overview]
Message-ID: <87y4z7rgas.fsf@Rainer.invalid> (raw)
In-Reply-To: 87ob04gnz1.fsf@gmail.com

Nicolas Goaziou writes:
> Correct. It should be fixed.

It still isn't correct.  If you put "//" after a "file:" scheme, then
you need to put an authority there (an empty authority means localhost
in some contexts, but then the path has to start with a slash).  Also,
with the new implementation relative file: links would stop working.  A
relative file link cannot have any slashes after the scheme, while an
absolute path must have three (not going into the vagaries of trying to
use UNC paths and file links that work around the security policies of
various web browsers).

http://www-archive.mozilla.org/quality/networking/testing/filetests.html


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2014-04-14 17:07 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 [this message]
2014-04-14 19:10     ` Nicolas Goaziou
2014-04-14 19:19       ` Achim Gratz
2014-04-14 20:06         ` Nicolas Goaziou
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:
  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=87y4z7rgas.fsf@Rainer.invalid \
    --to=stromeko@nexgo.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).