On Sat, Nov 8, 2008 at 9:18 AM, Andrew Long <[EMAIL PROTECTED]> wrote:
> ...
> It's a script.
> ...
> if [ "$gui" ]; then
> ...
> exec "$binary" -g $opts ${1:+"$@"} &
> else
> exec "$binary" $opts ${1:+"$@"}
> fiSo whatever the command line options, the script runs gvim in the background with '&'. This explains why python Popen returns immediatly and pyclewn can't get the result of the command. I will find a workaround, maybe pyclewn should run vim on posix systems and run gvim only on Windows, when it wants to get the results of vim commands. > ... > 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) For information, there is yet another little annoying problem when running pyclewn with gvim 7.2 (but not on older releases): the first gdb command is ignored when you type the command with the initial [NoName] buffer so you must either, edit first a buffer to avoid this, or type the command once again. This will be fixed shortly. Xavier --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
