These are tidings of great sorrow and melancholy, for ever since I upgraded
X11 on my Cygwin workstation (about a week ago) I lost my reliable faithful
friend, GNU Emacs, whose X11 version crashes often and unpredictably with
segmentation fault (the "nox" version runs fine).
I run Emacs and X11 se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After a short bliss of Emacs stability under Cygwin/X11, the crashes
are back -- major irritant. The crashes are accompanied by various
messages, not always looking identical. Here's the latest:
$ X protocol error: BadIDChoice (invalid resource
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The X11 version of Emacs (*not* xemacs, mind you) still crashes with
the following message
X protocol error: BadIDChoice (invalid resource ID chosen for this
connection) on protocol request 1
after the latest upgrades to:
cygwin 1.5.18-
in and X11 yesterday only. So, it seems to be Vista
specific.
Another Vista post-install difference: there are no X11 entries in the start
menu.
Happy hacking all,
Zdzislaw Meglicki, OVPIT, Indiana University
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem
e installed the same Cygwin version
only
a day earlier. The Vista cygcheck header is:
Cygwin Configuration Diagnostics
Current System Time: Fri Feb 20 14:29:24 2009
Windows Longhorn/Vista (not yet supported!) Ver 6.0 Build 6001 Service Pack 1
Running under WOW64 on AMD64
Cheers,
Gustav
Zdzislaw Me
ng to
cygwin at cygwin dot com as well.
Perhaps related: in emacs-X11 entering the shell mode (M-x shell) kills the
shell. I just get a prompt, then "exit" and a message
Process shell finished
This does *not* happen in emacs-nox, neither does this happen in xemacs.
I attac
Thank you so much for your help. I'm doing this right now... Perhaps this will
fix my X11 problems (with xterm and emacs-X11) as well... Let's see...
bunzipped... moved... stopped Cygwin servers... renamed /bin/cygwin1.dll...
restarted servers... (they work)... Cygwin shell ... works... sent mai
