Something like that happened when (already in X) I happened
to clean my /tmp directory, deleting the dirs used by X with it...
Every open of a gtk program needed 5 to 10 sec after that.
Of course, restart of X solved it.
Morale: be careful what you put in your .bashrc ;)
ralf
--
gentoo-user@g
On Sun, 3 Dec 2006, Philip Webb wrote:
So you differ in having "cscope nls -perl": could it be one of those ?
Don't think so, they were there before. The "-perl" is the only
difference from my other box (the one without the gvim problem).
'emerge world' is always a bad idea (grin).
So I've h
061203 Jorge Almeida wrote:
> On Sun, 3 Dec 2006, Philip Webb wrote:
>> Emerge details (this is the latest "unstable"):
>> app-editors/gvim-7.0.174 USE="-acl (-aqua) -bash-completion -cscope
>> -gnome gpm gtk motif -mzscheme -netbeans -nextaw -nls perl python -ruby"
> Mine are:
> app-editors/gvi
On Sun, 3 Dec 2006, Philip Webb wrote:
061203 Jorge Almeida wrote:
My gvim now takes about some 5s to start.
The no-gui vim from Konsole still is as fast as ever.
Vim & Gvim were compiled with the "bash-completion" USE variable,
so I recompiled gvim without it. No difference.
Delay here < 1
061203 Jorge Almeida wrote:
> My gvim now takes about some 5s to start.
> The no-gui vim from Konsole still is as fast as ever.
> Vim & Gvim were compiled with the "bash-completion" USE variable,
> so I recompiled gvim without it. No difference.
Delay here < 1 s from Konsole on KDE 3.5.5 .
Emerg
My gvim now takes about some 5s to start. It started happening after
"emerge -NDu world". revdep-rebuild has no requirements. The no-gui vim
(started from KDE's konsole) still is as fast as ever. The difference
between vim and gvim used to be almost negligible...
I noticed that both were compiled
6 matches
Mail list logo
