emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bart Bunting <bart@bunting.net.au>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-store-link dired and files with spaces
Date: Tue, 29 Apr 2014 11:29:57 +0200	[thread overview]
Message-ID: <87d2g0pjoq.fsf@gmail.com> (raw)
In-Reply-To: <m2fvkwri8n.fsf@ursys.com.au> (Bart Bunting's message of "Tue, 29 Apr 2014 12:18:16 +1000")

Hello,

Bart Bunting <bart@bunting.net.au> writes:

> I'm having an issue with storing links to files with spaces in their
> names.
>
> If I visit a dired buffer, use c-c l to store the link of the file under
> point and then in an org buffer c-c c-l to insert it.
>
> I find that the file can not be opened from within the org buffer as org
> appears to not recognize spaces in the file name and only sees the
> filename as the part up until the first space.
>
> An example of a link that does not work:
>
> [[file:resumes/Sandeep%20Salwan%20Satellite%20network%20engineer%20Cover%20Letter.doc][file:resumes/Sandeep
> Salwan Satellite network engineer Cover Letter.doc]]

What Org version are you using? I cannot reproduce it with master.

> I don't quite understand why the first part of the link (the
> description) is url encoded but not the latter part?

The description is for human consumption. It doesn't need to be encoded.
To tell the truth, it can be troublesome if the file name contains
square brackets, but I don't think we need to impede readability to work
around this.


Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2014-04-29  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29  2:18 org-store-link dired and files with spaces Bart Bunting
2014-04-29  9:29 ` 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

  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=87d2g0pjoq.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=bart@bunting.net.au \
    --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).