From: firstname.lastname@example.org (Diogo F. S. Ramos)
To: Carsten Dominik <email@example.com>
Subject: Re: Bug: Can't follow a link to a relative html filename with a whitespace [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/share/emacs/24.3/lisp/org/)]
Date: Fri, 13 Sep 2013 10:25:48 -0300 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <39B56048-2824-40E0-9CF8-F365454029CF@gmail.com> (Carsten Dominik's message of "Fri, 13 Sep 2013 08:37:00 +0200")
> On 8.9.2013, at 04:54, Diogo F. S. Ramos <email@example.com> wrote:
>> 1. touch a file as `/tmp/bar baz.html'
>> 2. Visit `/tmp/foo.org'
>> 3. Link to the HTML file typing [[file:bar baz.html]]
>> 4. Try following the link with C-c C-o
>> * Expected
>> Open the file inside a browser
>> * Happens
>> Two urls are open inside the browser: <file:///tmp/bar> and
> Hi Ramos,
> first of all, this works out of the box with my current Org version.
Uh. That's odd. Maybe you are not using the same version of me? I'm
using the org-version shipped with Emacs 24.3.1.
> Second, the link should look like this
> [[file:bar%20baz.html][file:bar baz.html]]
> Org makes it look like this when you insert the link using the proper Org commands to do so. It also repairs the link when you put the Cursor on it and press `C-c C-l RET RET'.
You are right.
I was aware of it though so that's why I specifically wrote "typing".
I think the "%20" is added because org-mode thinks this is an url, which
it is not.
But either way, can you open the file using C-c C-o? I suspect that
with the repair it's even harder now to open it.
> Third: I never put spaces into file names :)
That's a sensible thing to do.
prev parent reply other threads:[~2013-09-13 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-08 2:54 Bug: Can't follow a link to a relative html filename with a whitespace [7.9.3f (release_7.9.3f-17-g7524ef @ /usr/share/emacs/24.3/lisp/org/)] Diogo F. S. Ramos
2013-09-13 6:03 ` Carsten Dominik
2013-09-13 6:37 ` Carsten Dominik
2013-09-13 13:25 ` Diogo F. S. Ramos [this message]
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 \
* 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).