From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: org-store-link dired and files with spaces Date: Tue, 29 Apr 2014 11:29:57 +0200 Message-ID: <87d2g0pjoq.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54744) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wf4M2-0002h4-GX for emacs-orgmode@gnu.org; Tue, 29 Apr 2014 05:29:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wf4Lv-0000sY-6L for emacs-orgmode@gnu.org; Tue, 29 Apr 2014 05:29:34 -0400 Received: from mail-we0-x22f.google.com ([2a00:1450:400c:c03::22f]:54945) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wf4Lu-0000sB-W3 for emacs-orgmode@gnu.org; Tue, 29 Apr 2014 05:29:27 -0400 Received: by mail-we0-f175.google.com with SMTP id q58so7379020wes.6 for ; Tue, 29 Apr 2014 02:29:26 -0700 (PDT) In-Reply-To: (Bart Bunting's message of "Tue, 29 Apr 2014 12:18:16 +1000") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bart Bunting Cc: emacs-orgmode@gnu.org Hello, Bart Bunting 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