Re: non-posix compliant shells

2007-11-17 Fir de Conversatie Matthew Winn
On Fri, 16 Nov 2007 16:10:40 +0100, Vladimir Marek <[EMAIL PROTECTED]> wrote: > I do have > > :set shell=/bin/sh > > This just says to vim, to use /bin/sh for executing external commands. > It does not say which shell I should use for my interactive work. > > Then I run > > :!fish > > Welcom

Re: non-posix compliant shells

2007-11-16 Fir de Conversatie Vladimir Marek
> > Maybe I misunderstood here. If you want to tell vim to use /bin/sh all > > the time, just put "set shell=" unconditionally into your vimrc. > > That's clear, but I'd like to use fish and not /bin/sh as shell. > > You can always run > > > > :!fish > > That's the problem - it does not work -

Re: non-posix compliant shells

2007-11-16 Fir de Conversatie Gour
On Fri, 16 Nov 2007 16:10:40 +0100 Vladimir Marek <[EMAIL PROTECTED]> wrote: > This just says to vim, to use /bin/sh for executing external commands. > It does not say which shell I should use for my interactive work. Hmm, then I must wrongly understood the vim's help: :sh[ell]Th

Re: non-posix compliant shells

2007-11-16 Fir de Conversatie Charles E Campbell Jr
James Vega wrote: >On Fri, Nov 16, 2007 at 10:01:03AM -0500, Charles E Campbell Jr wrote: > > >>gour wrote: >> >> >>>I hit the problem in vim yesterday when I wanted to run fish shell >>>(http://fishshell.org) within vim and soon got informed that the >>>problem is >>> >>> >>Exactly w

Re: non-posix compliant shells

2007-11-16 Fir de Conversatie Gour
On Fri, 16 Nov 2007 17:36:52 +0100 Vladimir Marek <[EMAIL PROTECTED]> wrote: > Sure, what are your exact steps ? chsh and then /usr/bin/fish Sincerely, Gour signature.asc Description: PGP signature

Re: non-posix compliant shells

2007-11-16 Fir de Conversatie James Vega
On Fri, Nov 16, 2007 at 10:31:20AM -0500, James Vega wrote: > Vim is running this command > > /usr/bin/fish -c "(ls /tmp) >/tmp/v244859/1" > > fish doesn't allow you to use a subshell command as the actual command > being run. That is, the above command-line errors out (in an > interactive she

Re: non-posix compliant shells

2007-11-16 Fir de Conversatie James Vega
On Fri, Nov 16, 2007 at 10:01:03AM -0500, Charles E Campbell Jr wrote: > > gour wrote: > > >I hit the problem in vim yesterday when I wanted to run fish shell > >(http://fishshell.org) within vim and soon got informed that the > >problem is > > > > > Exactly what is the problem? Are you trying

Re: non-posix compliant shells

2007-11-16 Fir de Conversatie Vladimir Marek
> Hmm, then I must wrongly understood the vim's help: > > :sh[ell] This command starts a shell. When the shell > exits (after the "exit" command) you return to Vim. The name for the > shell command comes from 'shell' option. No, you understand correctly. I just don't use for fish i

Re: non-posix compliant shells

2007-11-16 Fir de Conversatie Vladimir Marek
Hi, > Googling a bit brought me to this thread http://tinyurl.com/3cgns7 > which provides 'workaround', i.e. putting something like: Snip from the thread: = cut == i still think that the best way would be to teach app developers tha

Re: non-posix compliant shells

2007-11-16 Fir de Conversatie Charles E Campbell Jr
gour wrote: >I hit the problem in vim yesterday when I wanted to run fish shell >(http://fishshell.org) within vim and soon got informed that the >problem is > > Exactly what is the problem? Are you trying to use system(), or filters (:!), or what? Please give an example of something you're

Re: non-posix compliant shells

2007-11-16 Fir de Conversatie Gour
On Fri, 16 Nov 2007 12:13:37 +0100 Vladimir Marek <[EMAIL PROTECTED]> wrote: > Maybe I misunderstood here. If you want to tell vim to use /bin/sh all > the time, just put "set shell=" unconditionally into your vimrc. That's clear, but I'd like to use fish and not /bin/sh as shell. > And what in

non-posix compliant shells

2007-11-16 Fir de Conversatie gour
Hi! I hit the problem in vim yesterday when I wanted to run fish shell (http://fishshell.org) within vim and soon got informed that the problem is that Vim expects to see posix-compliant shell which fish is not. Googling a bit brought me to this thread http://tinyurl.com/3cgns7 which provides 'w