Tony Mechelynck wrote:
> Ben Schmidt wrote:
>>> The filenames were the strings above without the double quotes. 
>>> Backslash-escaping looked OK: I could edit the files and save them. Then 
>>> "ls 
>>> t*" in bash didn't show spurious filenames, and these files' lengths 
>>> weren't 
>>> zero anymore. If you have other cases in mind, I'm ready to check.
>> I will try at some later stage when I have time/will to copy and apply the 
>> patch, 
>> but I always had problems when a partially completed filename contained a 
>> single 
>> quote where it wouldn't complete further. With
>>
>> wildmode=longest,list,full
>>
>> and files with names
>>
>> It's good
>> It's bad
>> It's ugly
>>
>> the completion would always fail. I would type I<Tab> which would yield 
>> "It\'s\ " 
>> typing g<Tab> then would fail with a beep.
>>
>> Also, it was somewhat odd to obtain, for these files
>>
>> It is odd
>> It's odd
>>
>> If I give I<Tab> the result is "It\". Kinda fair enough as whatever 
>> character 
>> comes next does need to be escaped, but still, seems a little strange.
>>
>> At any rate, those are my experiences and it would be interesting to know if 
>> they're fixed. It is really the quotes that caused problems. Completing 
>> works fine 
>> for a set of files like
>>
>> It is good
>> It is bad
>> It is ugly
>>
>> Cheers,
>>
>> Ben.
> 
> Looks OK here with the patch: after (in bash)
> 
>       touch "It's good"
>       touch "It's bad"
>       touch "It's ugly"
> 
> the command ":new I<Tab>" followed by other hits of the tab key, gives 
> successively
> 
>       :new It\'s\ _
>       :new It\'s\ bad_
>       :new It\'s\ good_
>       :new It\'s\ ugly_
>       :new I_
>       :new It\'s\ bad_
> 
> etc., where _ represents the cursor and 'wildmode' was set to 
> longest:full,full -- IOW, I got the expected results.
> 
> Best regards,
> Tony.

Oops, I misread:

        :new It\'s\ g<Tab>

still fails with a beep.


Best regards,
Tony.
-- 
Lie, n.:
        A very poor substitute for the truth, but the only one
discovered to date.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Raspunde prin e-mail lui