In documentation:
:h #!
:#!{anything} Ignored, so that you can start a Vim script with:
#!/usr/bin/env vim -S
echo this is a Vim script
quit
I don't think #!/usr/bin/env vim -S is
On 23/01/2008, Dasn [EMAIL PROTECTED] wrote:
I don't think #!/usr/bin/env vim -S is workable on all platforms.
$ cat test.vim
#!/usr/bin/env vim -S
echo this is a Vim script
quit
$ chmod +x test.vim
$ ./test.vim
env: vim -S: No such file or directory
Which platform are you on?
On SunOS
On Jan 23, 2008 11:15 AM, Erik Falor wrote:
On 23/01/2008, Dasn wrote:
I don't think #!/usr/bin/env vim -S is workable on all platforms.
$ cat test.vim
#!/usr/bin/env vim -S
echo this is a Vim script
quit
$ chmod +x test.vim
$ ./test.vim
env: vim -S: No such file or directory
Dasn wrote:
In documentation:
:h #!
:#!{anything} Ignored, so that you can start a Vim script with:
#!/usr/bin/env vim -S
echo this is a Vim script
quit
I don't think #!/usr/bin/env
On 23/01/08 21:20 +0100, Bram Moolenaar wrote:
It appears to work in more places when leaving out the env command:
#!vim -S
echo this is a Vim script
quit
This will trigger 'not found' error in fbsd, obsd and linux (Arch with
bash) in which I've tested.
As this line
