Dasn wrote:
> 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.
I tested on FreeBSD and it worked then. But now it doesn't...
> As this line should be ignored, what about in a descriptive manner? e.g:
>
> #!/real-path-to-vim/vim -S
> echo "this is a Vim script"
> quit
Not really a nice way to give an example, it works for nobody as-is.
My "env" command supports the -S argument. So this works:
#!/usr/bin/env -S vim -S
echo "this is a Vim script"
quit
How about other systems? The man page for "env" suggests that it's a
FreeBSD specific extension and added recently.
--
CART DRIVER: Bring out your dead!
There are legs stick out of windows and doors. Two MEN are fighting in the
mud - covered from head to foot in it. Another MAN is on his hands in
knees shovelling mud into his mouth. We just catch sight of a MAN falling
into a well.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
