>>>> "Ben" == Ben Wing <ben(a)xemacs.org>
writes:
Ben> Uwe Brauer wrote:
>
>
Ben> it would be very nice to know where the problem is.
Ben> sometimes typing Control-Shift-G in XEmacs will break out
Ben> and give you a backtrace. (it should always do that but
Ben> maybe sometimes doesn't ...) If not, try setting
Ben> Options->Troubleshooting->Debug on Quit, then manually do
Ben> `kill -INT ###', where ### is the process id of
Ben> XEmacs. (maybe it's `kill -SIGINT ###', i forget)
Ok, I continued with the testing:
- the problem does not occur when copying a large amount of
msg between nnml servers! Xemacs is as fast as gnu emacs
- the problem seem to be connected with `large' msg: msg with
an attachment >0.5 Mega. I tried this with xemacs -vanilla
either nognus-0.3 or the actual xemacs pkg release. Now
xemacs does not really get stack, after some Control g key
strokes I can continue typing (and even with
debug-on-signal t no useful backtrace is produced). However the
nnimap command got *stacked*. I can not leave neither the group
not the server
The command
lisp-process
lists me the imap command
imap open *nnimap* ucimap.ucm.es (none) network stream
connection 143(a)ucimap.ucm.es
could please somebody confirm this?
But I don't know how to kill that process, ps ux does not list that
process.
Again that problem does not occur in gnu emacs and now I begin to
understand why me complains about the slowness of the nnimap command
were ignored on the gnus list: it seems to be more of a xemacs
problem.
If someone could suggest me how to enhance the testing in order to
localise the problem...
Regards
Uwe Brauer