On 7 Nov 2008, at 19:58, Xavier de Gaye wrote:

>
> On Fri, Nov 7, 2008 at 6:56 PM, Andrew Long <[EMAIL PROTECTED]>  
> wrote:
>>
<snip lots/>
>
> Hello Andy
>
> This is not an issue with --nofork as pyclewn runs gvim with '-es' and
> gvim does not fork in this case.
> Can you check gvim file type on your system, is it the gvim binary or
> a script ?

It's a script.

/usr/bin/gvim: Bourne shell script text executable

Here's the credits at the top:-
#!/bin/sh
#
# This shell script passes all its arguments to the binary inside the  
Vim.app
# application bundle.  If you make links to this script as view, gvim,  
etc.,
# then it will peek at the name used to call it and set options  
appropriately.
#
# Based on a script by Wout Mertens and suggestions from Laurent  
Bihanic.
# This version is the fault of Benji Fisher, 16 May 2005.

and here's the bit at the end that talks about forcing it to run in the
background when invoked as 'gvim'

# Last step:  fire up vim.
# GUI mode will always create a new Vim instance, because Vim can't have
# more than one graphic window yet.
# The program should fork by default when started in GUI mode, but it  
does
# not; we work around this when this script is invoked as "gvim" or  
"rgview"
# etc., but not when it is invoked as "vim -g".
if [ "$gui" ]; then
# Note: this isn't perfect, because any error output goes to the
# terminal instead of the console log.
# But if you use open instead, you will need to fully qualify the
# path names for any filenames you specify, which is hard.
exec "$binary" -g $opts ${1:+"$@"} &
else
exec "$binary" $opts ${1:+"$@"}
fi

The version of console vim that ships with leopard in /usr/bin IS a
binary

/usr/bin/vim.old: Mach-O universal binary with 2 architectures
/usr/bin/vim.old (for architecture i386):       Mach-O executable i386
/usr/bin/vim.old (for architecture ppc7400):    Mach-O executable ppc

(I moved this version out of the way so I could try invoking the gvim
script as 'vim -g')

However, it seems that the biggest obstacle to my using pyclewn on my
Mac was the absence of netbeans integration in the default vim
programs that come with OS X leopard.

As of now, I've got pyclewn installed using a copy of vim built by
macports using gtk2. I shall have a go at building macvim with netbeans
in the near future and try that (I like the interface of macvim bette
than gtk2)

Regards, Andy
-- 
Andrew Long
andrew dot long at mac dot com


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to