On Fri, Aug 06, 2010 at 05:09:17PM +0200, Emilio Pozuelo Monfort wrote:
> On 06/08/10 16:47, Moritz Muehlenhoff wrote:
> > Pida is executing gvim, though. Which vi package is providing gvim in
> > your installation?
>
> It's vim-gnome, and the alternative points to /usr/bin/vim.gnome. Executing
> 'gvim' fires a graphical vim, but executing 'vim.gnome' fires a terminal-based
> vim.
I have the same setup, but still cannot reproduce it.
> I guess pida is just forking gvim and not following the alternative and
> launching vim.gnome?
Could you try whether attached quick patch fixes the issue for you?
Cheers,
Moritz
--- /usr/share/pyshared/pida/utils/vim/vimcom.py.orig 2010-08-06 11:25:37.000000000 -0400
+++ /usr/share/pyshared/pida/utils/vim/vimcom.py 2010-08-06 11:26:04.000000000 -0400
@@ -144,7 +144,7 @@
if not self.pid:
# Get the console vim executable path
#command = self.prop_main_registry.commands.vim.value()
- command = 'gvim'
+ command = '/etc/alternatives/gvim'
# Fork using pty.fork to prevent Vim taking the terminal
sock = gtk.Socket()
w = gtk.Window()
@@ -154,7 +154,7 @@
pid, fd = pty.fork()
if pid == 0:
# Child, execute Vim with the correct servername argument
- os.execvp(command, ['gvim', '-f', '--servername', self.name,
+ os.execvp(command, ['/etc/alternatives/gvim', '-f', '--servername', self.name,
'--socketid', '%s' % xid])
#'-v'])
# os.system('%s -v --servername %s' % (command, self.name))
