emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Killing a frame sometimes kills emacs


From: andres . ramirez
Subject: Re: Killing a frame sometimes kills emacs
Date: Fri, 20 Jan 2012 18:29:37 -0500
User-agent: SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Goj┼Ź) APEL/10.8 Emacs/23.3 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)

Hi.

I have revno 106895. And this problem still persist.

emacs is configured as follows:
In GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 3.2.3)
 of 2012-01-20 on wari
Windowing system distributor `The X.Org Foundation', version 11.0.11103000
configured using `configure  '--prefix=/usr' '--sysconfdir=/etc' 
'--localstatedir=/var' '--libexecdir=/usr/lib' 
'--mandir=/usr/share/man/emacs-24' '--without-sound' 
'--program-suffix=-emacs-24' '--infodir=/usr/share/info/emacs-24' 
'--with-x-toolkit=gtk3' 'CFLAGS=-march=i686 -mtune=generic -O2 -pipe 
-fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2' 
'LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu''

Regards

At Fri, 18 Nov 2011 10:38:39 +0100,
Tassilo Horn wrote:
> 
> Stefan Monnier <address@hidden> writes:
> 
> Hi Stefan,
> 
> > To avoid the risk of reaching 0 via wrap-around (yes, I know that
> > creating a billion frames in the life of a single session is unlikely,
> > but still), you could do:
> >
> >      /* If needed, delete the terminal that this frame was on.
> >         (This must be done after the frame is killed.) */
> >      terminal->reference_count--;
> > #ifdef USE_GTK
> >     /* ... (Use C-style not C++ style comments) ... */
> >     if (terminal->reference_count == 0 && terminal->type == output_x_window)
> >       terminal->reference_count = 1;
> > #endif
> >      if (terminal->reference_count == 0)
> >        {
> >         Lisp_Object tmp;
> 
> I liked this version best and it's committed now.
> 
> Bye,
> Tassilo
> -- 
> (What the world needs (I think) is not
>       (a Lisp (with fewer parentheses))
>       but (an English (with more.)))
> Brian Hayes, http://tinyurl.com/3y9l2kf
> 
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]