>>Sorry, deleted the original email, gotta reply to something else...
>You couldn't just create a new thread?
Mmmmmmm, no.
>>What about just plain 'vim *' on the command line? Some reason that
>>doesn't work?
>That works fine for simple cases where the file names match some
>pattern, but it doesn't work for cases where you want to edit the
>files that result from some complicated search pipeline such as this
>one:
> find include src -name \*.[ch] -mtime -3 -print
Unno, he specified 'ls somefile |...', which to me would simply return
"somefile" on its own line, to be passed along to 'xargs'. So either
just use the given filename, or something like '*' for everything in the
directory, if "somefile" [sic] would actually be a directory-name.
'foo' == file:
> ls foo
foo
> _
'foo' == directory:
> ls foo
file1
file2
file3
...
fileN
> _
I just suggested a wildcard would be easier than going the roundabout
way through 'ls' and 'xargs'.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
