OK, found the issue, had to use url-insert-entities-in-string instead of
shell-quote-argument.
Thanks,
- Marcelo.
On Thu, Sep 6, 2012 at 11:47 PM, Marcelo de Moraes Serpa <
celose...@gmail.com> wrote:
> Nick, it's a custom script... however, it looks like I was using the wrong
> format. Instead
Nick, it's a custom script... however, it looks like I was using the wrong
format. Instead of escaping the space chars, I should uri-encode them it
seems. I'll try that. Thanks!
On Thu, Sep 6, 2012 at 11:03 PM, Nick Dokos wrote:
> Marcelo de Moraes Serpa wrote:
>
> > I have several links that
Marcelo de Moraes Serpa wrote:
> I have several links that use the file protocol to open files indexed in
> org entries. They work fine for entries that point to file whose filenames
> do *not* contain space, but for entries with space in them, it just fails
> silently. I.e:
>
> [[file:/Volume
I'm pretty sure a (") needs to go right after the first (:) and another
needs to be just before the first (]) character. On Thu, 6 Sep 2012,
Marcelo de Moraes Serpa wrote:
> Hi list,
>
> I have several links that use the file protocol to open files indexed in
> org entries. They work fine for e
Hi list,
I have several links that use the file protocol to open files indexed in
org entries. They work fine for entries that point to file whose filenames
do *not* contain space, but for entries with space in them, it just fails
silently. I.e:
[[file:/Volumes/ext-hd/pdfs/Name\ Of\ The-\ 4th\