ashersyed / macvim

Automatically exported from code.google.com/p/macvim
0 stars 0 forks source link

Apostrophes in filenames do not open correctly #481

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I'm not sure of the exact conditions needed, but the following seems to be 
sufficient: If a file has an apostrophe/single quote in its name, and at least 
one space in its path, then opening it from the OS X dialog box (or from the 
Recent Documents menu) fails to open the file. Instead, it will open several 
new buffers, with names taken from components of the path (i.e. it will do 
something similar to if you type 'mvim [path]' in the terminal without 
correctly escaping/quoting the path.

What steps will reproduce the problem?

mkdir ~/two\ words
echo foo > ~/two\ words/ba\'r.txt

open MacVim, File>Open, navigate to ba'r.txt, and open it

What is the expected output? What do you see instead?

Expected: a buffer for the file ba'r.txt, containing "foo"
Actual: two empty buffers, one at ~/two, and one at ~/words/ba'r.txt

(The actual case which made me notice this bug had several spaces in the path, 
so opened several buffers.)

What version of MacVim and OS X are you using (see "MacVim->About MacVim"
and  "Apple Menu->About This Mac" menu items, e.g. "Snapshot 40, 10.5.6
Intel")?

OSX: 10.8.5
MacVim: Snapshot 71

Please provide any additional information below.

.vim and .vimrc have both been disabled.

Original issue reported on code.google.com by jdapa...@gmail.com on 23 Oct 2013 at 10:16