Re: Bug in recent Win32 snapshots
Hi, Marcus -
On Wed, Jan 25, 2012 at 4:11 PM, Marcus Harnisch wrote:
With the two recent XEmacs Win32 binaries, I experience strange
behavior
when exiting Gnus (a snapshot that claims to be "No Gnus v0.18"): At the
end of #'gnus-clear-system, all Gnus buffers will be killed with
#'gnus-kill-buffer. When it comes to killing my IMAP buffer (#<buffer
"*nnimap imap.example.com nil *nntpd**">), XEmacs remains completely
unresponsive and must be killed. The error could be traced down to
#'kill-buffer but not further since I can't debug on my Win32 machine. I
don't seem to be able to reproduce the issue on Linux.
With the exact same start-up and package environment, an older Win32
binary works absolutely fine.
These break:
XEmacs-21.5-2012-01-17 "21.5 (beta31) \"ginger\" XEmacs
Lucid"
XEmacs-21.5-2011-11-28 "21.5 (beta31) \"ginger\" XEmacs
Lucid"
This one is OK:
XEmacs-21.5-test-2010-09-21 "21.5 (beta29) \"garbanzo\" XEmacs
Lucid"
Well, other than the XEmacs 21.5 source code and the build environment
I use for making the kits, nothing much has changed between those
kits.:-)
The problem probably has something to do with kill the connection to
the imap server. How is that done? Is there a hook that you can
debug? Alternatively, can you try to terminate the imap connection
first? There must be an imap trace buffer, right?
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta