On 4/7/2012 6:11 PM, Angelo Graziosi wrote:
Il 06/04/2012 21.22, Angelo Graziosi ha scritto:
Any way I will try to follow your recipe to reproduce the problem, but I
am sure it is still there..
No, it isn't!
I have run Emacs for more than 14 hours and I haven't see any problem. I
have done
Ken Brown wrote:
Would you mind sending me your cygcheck output
Attached...
What anti-virus software do you use (if any)?
Microsoft Security Essential (MSE)... I would be glad if someone could
teach me how do not use an AV on Windows... ;-)
Ciao,
Angelo.
cygcheck.out.bz2
Il 06/04/2012 21.22, Angelo Graziosi ha scritto:
Any way I will try to follow your recipe to reproduce the problem, but I
am sure it is still there..
No, it isn't!
I have run Emacs for more than 14 hours and I haven't see any problem. I
have done that strictly following your recipe...
On 4/4/2012 6:12 PM, Yaakov (Cygwin/X) wrote:
On 2012-04-04 09:15, Ken Brown wrote:
Another option is to use gtk3 but to put the GSETTINGS_BACKEND
workaround into the emacs startup code:
setenv (GSETTINGS_BACKEND, memory, 1);
I've been testing this, and it seems to work (but I won't be
Hi Ken,
Ken Brown wrote:
Now I can reproduce the problem with both gtk2 and gtk3
If you remember I flagged this on 24.11.2011 with a private mail. After
the upgrading to GNOME 3.2, not only the gtk3 build was unstable but
also the old gtk2 builds were unstable...
Since then I am using
