Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
Cc: xemacs-beta@xemacs.org
Subject: Re: Speed difference in Gnus
Date: Fri, 28 Oct 2005 17:53:09 +0200	[thread overview]
Message-ID: <87oe59tz8a.fsf@mat.ucm.es> (raw)
In-Reply-To: <ilud5lpemrk.fsf@latte.josefsson.org>

>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:

   >> 
   >> Ok that works, however since the process get stacked I don't get any
   >> reasonable backtrace.

   Simon> I don't understand.  Does XEmacs freeze completely?  If so, I don't
   Simon> think there is anything we can do at the Elisp level.  It must be
   Simon> debugged as an XEmacs bug.

No what I say is: I want to copy that msg and xemacs starts to tell me
copying msg, but nothing happens after 2 min after several Control g I
can type again, however it seems that the nnimap command is stacked, I
cannot leave the group nor the server, but I have to do what you told
me.

So for me it not clear who is to blame. However that problem does not
occur in gnu emacs with the same gnus (ngnus 0.3)






  reply	other threads:[~2005-10-28 15:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r7ap899o.fsf@xemacs.org>
2005-10-13 21:17 ` Reiner Steib
     [not found] ` <434EFD44.7030601@xemacs.org>
     [not found]   ` <877jcgub0f.fsf@xemacs.org>
     [not found]     ` <434F3897.3050007@xemacs.org>
     [not found]       ` <873bn4tptq.fsf@xemacs.org>
     [not found]         ` <87d5m89wuf.fsf@tleepslib.sk.tsukuba.ac.jp>
     [not found]           ` <87y84nyuo0.fsf@mat.ucm.es>
     [not found]             ` <873bmulscb.fsf@tleepslib.sk.tsukuba.ac.jp>
     [not found]               ` <87pspypwzv.fsf@mat.ucm.es>
     [not found]                 ` <sluuli82.fsf@smtprelay.t-online.de>
2005-10-24 16:52                   ` Uwe Brauer
2005-10-24 18:24                     ` David Kastrup
2005-10-25  9:50                       ` Uwe Brauer
2005-10-25 10:48                         ` David Kastrup
2005-10-25 17:50                         ` Jesper Harder
2005-10-25 22:07                           ` David Kastrup
2005-10-26  9:32                             ` Uwe Brauer
2005-10-27  1:02                               ` Ben Wing
2005-10-27  9:24                                 ` Uwe Brauer
2005-10-28  9:52                                 ` Uwe Brauer
2005-10-28 11:09                                   ` Simon Josefsson
2005-10-28 11:55                                     ` Uwe Brauer
2005-10-28 12:27                                       ` Simon Josefsson
2005-10-28 12:06                                     ` Uwe Brauer
2005-10-28 12:28                                       ` Simon Josefsson
2005-10-28 14:05                                         ` Uwe Brauer
2005-10-28 14:31                                           ` Simon Josefsson
2005-10-28 15:53                                             ` Uwe Brauer [this message]
2005-10-31  7:05                                               ` Ben Wing
2005-10-28 10:04                                 ` Uwe Brauer
2005-10-24 21:00                     ` Reiner Steib

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oe59tz8a.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=xemacs-beta@xemacs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).