Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
Cc: ding@gnus.org, Mats Lidell <Mats.Lidell@contactor.se>
Subject: Re: Imap Problem
Date: 04 Jun 2001 12:06:05 -0400	[thread overview]
Message-ID: <76snhgs00i.fsf@newjersey.ppllc.com> (raw)
In-Reply-To: <ilu1yp24mpb.fsf@barbar.josefsson.org> (Simon Josefsson's message of "02 Jun 2001 23:05:20 +0200")


Simon,

I updated pgnus and, of course, this includes your patch.  It's too early to
tell whether this patch fixed the problem since I have to wait for a timeout
to see if it reconnects properly.  I am having a related problem, however,
and I don't know if it's as a result of your patch or not.

If I start gnus in another frame, a sure way of triggering the bug which
you've hopefully patched, the password prompting is broken.  Instead of
accepting my CR as a end-of-line and passing the password onwards, it eats
my CR and displays it as a '.'.  If I start gnus in the my initial frame, the
password prompting works correctly.  Can this be a result of something else I
may have downloaded when I did my cvs update or might this be as a result of
what you did.

What I will probably do now is back out my cvs update, restore the version I
had been using up until yesterday, and manually apply Matt's version of your
patch. If that works, I'll post a bug report with respect to password
handling.


...Jake


>>>>> "SJ" == Simon Josefsson <simon@josefsson.org> writes:

    SJ> 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.

    SJ> Thanks!  I modified all streams similarily and committed it.

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

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

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

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


-- 
Jake Colman                     

Principia Partners LLC                  Phone: (201) 946-0300
Harborside Financial Center               Fax: (201) 946-0320
902 Plaza II                           Beeper: (800) 928-4640
Jersey City, NJ 07311                  E-mail: colman@ppllc.com
                                       E-mail: jcolman@jnc.com
                                          web: http://www.ppllc.com


  parent reply	other threads:[~2001-06-04 16:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-31 23:55 Jake Colman
2001-06-01  6:41 ` Kai Großjohann
2001-06-01 15:52   ` Jake Colman
2001-06-01  7:00 ` Mats Lidell
2001-06-01 13:22   ` Jake Colman
2001-06-01 15:01     ` Kai Großjohann
2001-06-01 16:00       ` Jake Colman
2001-06-01 15:46     ` Mats Lidell
2001-06-01 16:09       ` Jake Colman
2001-06-01 18:04       ` Jake Colman
2001-06-01 23:24       ` Simon Josefsson
2001-06-02 20:03         ` Mats Lidell
2001-06-02 20:13           ` Mats Lidell
2001-06-02 21:05           ` Simon Josefsson
2001-06-04 15:21             ` Jake Colman
2001-06-05 18:10               ` Simon Josefsson
2001-06-04 16:06             ` Jake Colman [this message]
2001-06-04 16:18             ` Jake Colman
2001-06-05  8:34               ` Mats Lidell
2001-06-05 14:58                 ` Nevin Kapur
2001-06-05 15:20                   ` Jake Colman
2001-06-05 18:20                     ` Simon Josefsson
2001-06-05 19:06                       ` Jake Colman
2001-06-05 19:39                         ` Simon Josefsson
2001-06-05 23:20                           ` Jake Colman
2001-06-05 23:56                           ` Mats Lidell
2001-06-05 18:19               ` Simon Josefsson
2001-06-05 19:07                 ` Jake Colman
2004-10-07 11:36 imap problem walter.franzini-M4bTUdDEyImonA0d6jMUrA

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=76snhgs00i.fsf@newjersey.ppllc.com \
    --to=colman@ppllc.com \
    --cc=Mats.Lidell@contactor.se \
    --cc=ding@gnus.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).