Re: foobared imap server...

[Simon Josefsson <jas@extundo.com>]

Jody Klymak <jklymak@coas.oregonstate.edu> writes:

> I've attached a new backtrace (and the new imap log) with imap.el no
> longer byte compiled.  

Thanks.

> Thanks for any help you can give.  
>
> Cheers,  Jody
>
> Debugger entered--Lisp error: (error "In imap-parse-flag-list")
>   signal(error ("In imap-parse-flag-list"))
>   error("In imap-parse-flag-list" 10)
>   (or (eq (char-after) 41) (error "In imap-parse-flag-list" (char-after)))
>   (progn (or (eq ... 41) (error "In imap-parse-flag-list" ...)) nil)
>   (assert (eq (char-after) 41) t "In imap-parse-flag-list")
>   (let (flag-list start) (assert (eq ... 40) t "In imap-parse-flag-list") (while (and ... ... ...) (push ... flag-list)) (assert (eq ... 41) t "In imap-parse-flag-list") (imap-forward) (nreverse flag-list))
>   imap-parse-flag-list()

This is weird, it works here.  Can you put the point at '(' in the
following lines and do M-: (imap-parse-flag-list) RET and tell if this
also generate the same backtrace?

* FLAGS (\Answered \Flagged \Draft \Deleted \Seen jklymak	l)
* OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen jklymak	l \*)]

It should, but it doesn't for me.  Perhaps there is some customization
that modify the behaviour.  If it does crash for you too, doing the
same with emacs -q might suggest if something in your environment is
causing this.  Of course, then imap.el should be fixed.