On Fri, Aug 06, 2010 at 05:48:24PM +0200, Emilio Pozuelo Monfort wrote:
> On 06/08/10 17:28, Moritz Muehlenhoff wrote:
> > 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?
>
> It keeps hanging. When it hangs, looking at ps I've noticed that there's a
> defunct gvim process:
>
> emi...@saturno:~$ ps aux | egrep "vim|pida"
> emilio 13595 0.9 1.7 137200 36336 pts/7 Sl+ 17:46 0:00 python
> /usr/bin/pida
> emilio 13598 0.1 0.0 0 0 pts/7 Z+ 17:46 0:00 [gvim]
> <defunct>
> emilio 13608 0.0 0.4 46420 9192 ? Ss 17:46 0:00 gvim
> --servername PIDA_EMBEDDED_1281109578.9 --cmd let PIDA_EMBEDDED=1 --cmd so
> /home/emilio/.pida2/pida_vim_init.vim --socketid 117440699
>
> Do you get a defunct process too? If not, that could be related.
I also get the defunct gvim process, but the integration of gvim itself
works fine functionality-wise.
Current stable upstream 0.6.2 has rewritten the integration of external
editors properly with subprocess, maybe updating the package is is the
best course of action.
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
