On Wed, Feb 8, 2012 at 11:59 AM, Nazri Ramliy <[email protected]> wrote: > On Wed, Feb 8, 2012 at 11:50 AM, Nazri Ramliy <[email protected]> wrote: >> On Wed, Feb 8, 2012 at 9:59 AM, Nazri Ramliy <[email protected]> wrote: >>> I'd like to report that the behavior does not exist outside of $HOME: >> >> One more detail: >> >> The bug is triggered only when '**' is right under $HOME. >> >> It does not appear for this case: >> >> cd $HOME >> $ mkdir -p 'a/**/xxx/yyy' >> $ cd 'a/**' >> $ vim -u NONE >> :cd xxx <-- works fine > > But strangely: > > $ cd $HOME > $ mkdir -p 'tmp/**/xxx/yyy' > $ cd 'tmp/**' > $ vim -u NONE > :cd xxx <-- gives error??? > > Nazri
Here's a little shell script that I use to test this behavior: --->8--- #!/bin/sh base=$HOME/foo # works fine #base=$HOME/bar # works fine #base=$HOME/t # works fine #base=$HOME/tmp # Error! #base=$HOME # Error! mkdir -p $base/'**/xxx/yyy' cd $base/'**' vim -u NONE -c 'cd xxx' -c pwd ---8<--- Nazri (Careful with the scissors!) -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
