Tony Mechelynck wrote:
> >> It appears it all works fine when 'shell' is "sh", but not when it is
> >> "bash". What is the difference between "sh" and "bash" considering
> >> single quotes?
> >
> > My fault. It has nothing to do with bash itself, just that "bash" is
> > four characters and "sh" is two :-). I'm glad this was tested before
> > sending it out!
> >
> > Here is a replacement patch that should deal with "bash" as with "sh":
> >
> >
> > *** ../vim-7.1.202/src/os_unix.c Thu Jan 3 18:55:21 2008
> > --- src/os_unix.c Fri Jan 4 18:23:04 2008
>
> No patch here for ex_docmd.c
>
> I suppose this patch is a replacement for the part of the previous one
> dealing with os_unix.c but that the part dealing with ex_docmd.c
> should be kept?
Yes, the patch to ex_docmd.c fixes the problem for command line
completion with & in the file name. I'm going to bring them out later
separately, since they really are two different problems. But one of
the file names use for testing requires both patches.
--
WOMAN: King of the who?
ARTHUR: The Britons.
WOMAN: Who are the Britons?
ARTHUR: Well, we all are. we're all Britons and I am your king.
The Quest for the Holy Grail (Monty Python)
/// 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
-~----------~----~----~----~------~----~------~--~---
