[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Cannot connect to X server
From: |
Stenuit, Pascal |
Subject: |
RE: Cannot connect to X server |
Date: |
Thu, 11 Dec 2003 10:20:31 -0500 |
There are no such calls in the version of emacs we use.
BTW, this is emacs 21.1.3, configured with
./configure rs6000-ibm-aix5.1 --with-gcc=no
--prefix=/home/pstenuit/emacs-21/emacs-21.3/rel
The same happens with 21.1.1.
I didnt notice these turn_on_timer calls, hence the
sigblock(sigmask(SIGALRM)) or somesuch.
thanks,
pascal
-----Original Message-----
From: Richard Stallman [mailto:address@hidden
Sent: Thursday, December 11, 2003 3:47 PM
To: Stenuit, Pascal
Cc: address@hidden
Subject: Re: Cannot connect to X server
As a quick and dirty hack, we've blocked SIGALRM just around the call to
XOpenDisplay and XtOpenDisplay and the problem went away. We didnt log a
call to IBM, though.
Why don't the calls to turn_on_atimers do this job?
turn_on_atimers (0);
dpy = XtOpenDisplay (Xt_app_con, SDATA (display_name),
resource_name, EMACS_CLASS,
emacs_options, XtNumber (emacs_options),
&argc, argv);
turn_on_atimers (1);
Are those calls present in your version?
-----------------------------------------
This email may contain confidential and privileged material for the sole use of
the intended recipient(s). Any review, use, retention, distribution or
disclosure by others is strictly prohibited. If you are not the intended
recipient (or authorized to receive for the recipient), please contact the
sender by reply email and delete all copies of this message. Also, email is
susceptible to data corruption, interception, tampering, unauthorized amendment
and viruses. We only send and receive emails on the basis that we are not
liable for any such corruption, interception, tampering, amendment or viruses
or any consequence thereof.