Gnus development mailing list
 help / color / mirror / Atom feed
From: stephen@xemacs.org (Stephen J. Turnbull)
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: Dave Love <fx@gnu.org>, ding@gnus.org, xemacs-beta@xemacs.org
Subject: Re: IMAP and Exchange 2007 - imap-fetch-safe
Date: Wed, 04 Feb 2009 01:21:23 +0900	[thread overview]
Message-ID: <87r62ffq4c.fsf@xemacs.org> (raw)
In-Reply-To: <878woolk81.fsf@marauder.physik.uni-ulm.de>

Reiner Steib writes:
 > On Mon, Feb 02 2009, Dave Goldberg wrote:
 > 
 > > Unfortunately I cannot report the same success.  I use XEmacs:
 > >
 > > "XEmacs 21.4 (patch 21) \"Educational Television\" [Lucid] (x86_64-unknown-linux, Mule) of Tue Jan  6 2009 on blackbird"
 > 
 > Does anyone have an idea what is different in XEmacs?

I don't know the implementation of Emacs so I'm just guessing, but I
think the difference may be that XEmacs provides a way to debug the
filter function.  You asked for a debugger:

 >       (let ((debug-on-error t))

and you got it:

 > > Debugger entered--Lisp error: (error "Internal error, tag 13 status BAD code nil text The specified message set is invalid.")

(BTW, I really wish you wouldn't use "Internal error" for errors
signaled by application code because some external program is being
persnickety....)

I've never encountered this requirement before, but you could try
binding `debug-on-error' to a list not including the error thrown by
the process filter, or binding `debug-ignored-errors' to a list
including the error thrown by the process filter, whichever is less
likely to give (GNU) Emacs an upset stomach.

I'm not sure that I consider debug-on-error's documentation (which
says that the debugger won't be run if a condition-case handler would
catch the error) to be lying, since process filters are conceptually
run asynchronously (ie, by the event loop), not within the scope of
the condition-case.

  reply	other threads:[~2009-02-03 16:21 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87iqphil5p.fsf@liv.ac.uk>
2008-12-22 22:38 ` imap.el workaround for Exchange 2007 Reiner Steib
2008-12-23 15:41   ` Dave Love
2009-01-01 18:34     ` Reiner Steib
2009-01-02 22:20       ` Ted Zlatanov
2009-01-02 22:38         ` Reiner Steib
2009-01-09 12:00       ` Simon Josefsson
2009-01-01 18:55     ` FIXMEs in imap.el and nnimap.el (was: imap.el workaround for Exchange 2007) Reiner Steib
2009-01-02 22:19       ` FIXMEs in imap.el and nnimap.el Ted Zlatanov
2009-01-02 22:57         ` Reiner Steib
2009-01-04 23:10           ` Dave Love
2009-01-07 21:07             ` Dave Love
2009-01-08 20:42               ` Reiner Steib
2009-01-07 19:25           ` Ted Zlatanov
2009-01-08 21:04             ` Reiner Steib
2009-01-13 10:40               ` Dave Love
2009-01-13 17:00                 ` IMAP and Exchange 2007 - imap-fetch-safe (was: FIXMEs in imap.el and nnimap.el) Reiner Steib
2009-01-13 17:20                   ` IMAP and Exchange 2007 - imap-fetch-safe Simon Josefsson
2009-01-17 20:58                     ` Dave Love
2009-01-28  1:18                       ` Dave Love
2009-01-31 15:27                       ` Reiner Steib
2009-02-01 15:43                         ` Bjorn Solberg
2009-02-02 14:54                           ` Dave Goldberg
2009-02-02 19:19                             ` Reiner Steib
2009-02-03 16:21                               ` Stephen J. Turnbull [this message]
2009-02-08 18:00                               ` Dave Love
2009-02-08 18:38                                 ` Dave Goldberg
2009-02-02 19:15                           ` Reiner Steib
2009-01-13 18:28                   ` Bjorn Solberg
2009-01-13 20:18                     ` Bjorn Solberg
2009-01-17 20:59                     ` Dave Love
2009-01-04 20:08       ` FIXMEs in imap.el and nnimap.el Dave Love
2009-01-05 16:13       ` Dave Love
2009-01-05 20:35         ` Conventions (was: FIXMEs in imap.el and nnimap.el) Reiner Steib
2009-01-06 11:33           ` Conventions Tassilo Horn

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=87r62ffq4c.fsf@xemacs.org \
    --to=stephen@xemacs.org \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=fx@gnu.org \
    --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).