[O] Possible bug in org-open-at-point when filename includes ampersand

2012-12-11 Thread Johnny 
Hi,

When working with org-capture and inserting links to files, I noticed
that some files do not open properly and found out that the filename
contains  which causes this issue. 

To replicate:
- Create a file test__file.txt
- In dired, locate the file and capture the link C-c l
- In an org file, insert link by C-c C-l
- Place point at file and C-c C-o (org-open-at-point)

The link org stores is e.g ~/test__file.txt.

This cannot be opened in a shell, but escaping the ampersand, the file
is opened fine, e.g. 

evince ~/test_\_file.txt

I inserted the escape character in the org link, but this to my dismay
still doesn't work.

Any ideas?

(except the obvious change of ampersand in filenames)

Thanks,

Johnny


-- 
Johnny

Re: [O] Possible bug in org-open-at-point when filename includes ampersand

2012-12-11 Thread Memnon Anon 
Johnny yggdra...@gmx.co.uk writes:

 To replicate:
 - Create a file test__file.txt
 - In dired, locate the file and capture the link C-c l
 - In an org file, insert link by C-c C-l
 - Place point at file and C-c C-o (org-open-at-point)

 The link org stores is e.g ~/test__file.txt.

 This cannot be opened in a shell, but escaping the ampersand, the file
 is opened fine, e.g. 

It does open here with
,
| ELISP (emacs-version)
| GNU Emacs 24.3.50.1 (i486-pc-linux-gnu, GTK+ Version 3.4.2)\n of
| 2012-12-09 on dex, modified by Debian
| ELISP (org-version t t)
| Org-mode version 7.9.2 (release_7.9.2-661-g66c664 @
| /home/kyilma/bin/elisp/org-latest/lisp/)
`

Memnon