Ben Schmidt wrote:
Ilya Sher wrote:
Zvi Har'El wrote:
I don't think it is worth the trouble insisting to pass % to an external
command instead of passing %.
The big plus here is much less typing:
comparing :e %CR vs :e %CR gives
5 vs 7 characters to type.
Maybe some modifier might be
Ilya Sher wrote:
Zvi Har'El wrote:
I don't think it is worth the trouble insisting to pass % to an external
command instead of passing %.
The big plus here is much less typing:
comparing :e %CR vs :e %CR gives
5 vs 7 characters to type.
Maybe some modifier might be added to % to make
I don't suppose saving 2 characters is a justifiable reason. For
consistency, I suggest to follow the comment in ex_docmd.c which says
/* Need to escape white space et al. with a backslash.
* Don't do this for:
* ...
* - shell commands (may have to use quotes instead).
Zvi Har'El wrote:
I don't think it is worth the trouble insisting to pass % to an external
command instead of passing %.
The big plus here is much less typing:
comparing :e %CR vs :e %CR gives
5 vs 7 characters to type.
Maybe some modifier might be added to % to make
it usable in or ''. I
characters. You don't have to guess
which characters are special for the particular shell. Just give the
original name as you received it.
On 10/11/07 23:28, Bram Moolenaar wrote:
Zvi Har'El wrote:
I feel vim has a bug in the case the name the file contain parentheses
Hi,
I feel vim has a bug in the case the name the file contain parentheses.
The % string contains in this case backslashes. For example:
$ls -l 'JVs America (article).html'
-rw-r--r-- 1 rl gileadweb 31426 2007-11-10 19:16 JVs America (article).htm
$ vi +'!/bin/echo %' +x -e -s 'JVs America
Zvi Har'El wrote:
Hi,
I feel vim has a bug in the case the name the file contain parentheses.
The % string contains in this case backslashes. For example:
[snip]
$ vi +'!/bin/ls %' +x -e -s 'JVs America (article).html'
/bin/ls: JVs America \(article\).html: No such file
: (b): No such file or directory
/bin/ls: cd: No such file or directory
On 10/11/07 19:40, Ilya Sher wrote:
Zvi Har'El wrote:
Hi,
I feel vim has a bug in the case the name the file contain parentheses.
The % string contains in this case backslashes. For example:
[snip]
$ vi
I think you should not escape any characters. You don't have to guess
which characters are special for the particular shell. Just give the
original name as you received it.
On 10/11/07 23:28, Bram Moolenaar wrote:
Zvi Har'El wrote:
I feel vim has a bug in the case the name the file
in the case the name the file contain parentheses.
The % string contains in this case backslashes. For example:
$ls -l 'JVs America (article).html'
-rw-r--r-- 1 rl gileadweb 31426 2007-11-10 19:16 JVs America (article).htm
$ vi +'!/bin/echo %' +x -e -s 'JVs America (article).html'
JVs America
10 matches
Mail list logo
