Re: Imap Problem

[Simon Josefsson <simon@josefsson.org>]

Mats Lidell <Mats.Lidell@contactor.se> writes:

> But the patch gave a hint. If the current buffer is changed without us
> knowing it why not set the buffer back again. Simon tried it but why
> not set it just before calling imap-parse-greeting so we know we are
> looking at the right thing. This lead to the following patch.

Thanks!  I modified all streams similarily and committed it.

> If you feel adventurous you might want to look into the affairs of
> process-status. ;-)

I think it's actually `accept-process-output' that changes the buffer
-- this is why the buffer is correct the first time but changes after
the while loop body has run once.  The code 

Anyway it's an XEmacs bug, but I'm not able to reproduce it so it's
hard to debug.  Maybe you could test the following patch with the old
Gnus imap.el and see if it does anything.

Index: event-stream.c
===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs/src/event-stream.c,v
retrieving revision 1.55
diff -u -u -w -r1.55 event-stream.c
--- event-stream.c	2001/05/31 12:45:36	1.55
+++ event-stream.c	2001/06/02 21:03:58
@@ -2526,7 +2526,7 @@
   int timeout_id = -1;
   int timeout_enabled = 0;
   int done = 0;
-  struct buffer *old_buffer = current_buffer;
+  /*  struct buffer *old_buffer = current_buffer;*/
   int count;
 
   /* We preserve the current buffer but nothing else.  If a focus
@@ -2637,7 +2637,7 @@
 
   Fdeallocate_event (event);
   UNGCPRO;
-  current_buffer = old_buffer;
+  /*  current_buffer = old_buffer;*/
   return result;
 }