From: Simon Josefsson <jas@extundo.com>
Subject: Re: upgrade from Debian's 5.10.6-0.CVS.20050317-1 to 5.11+v0.4.dfsg-1 breaks outbox on imap
Date: Tue, 16 May 2006 15:43:23 +0200 [thread overview]
Message-ID: <87wtcm3x1g.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87psieur5p.fsf@myxomop.com> (Alexander Kotelnikov's message of "Tue, 16 May 2006 15:48:18 +0400")
Alexander Kotelnikov <sacha@myxomop.com> writes:
>>>>>> On Tue, 16 May 2006 13:05:52 +0200
>>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
> SJ>
> SJ>
> SJ> Maybe imap-server-eol has to be "\n" too? Otherwise, I think imap.el
> SJ> will wait for the continuation line terminated with a \r\n, but that
> SJ> won't happen.
> SJ>
> SJ> If that doesn't work either, you'll have to debug imap.el to find out
> SJ> what it is looking for, and comparing that with what's in the "
> SJ> *nnimap* foo" buffer.
>
> Can you give me some hints how do I start, assuming that I have some
> emacs/elisp knowledge, but being entered to elisp debugger I mostly
> was inclined to exit it... And I am not familiar with imap.el
See the Gnus manual on troubleshooting, and especially on using
edebug. You'll probably want to instrument imap-arrival-filter and
chaise it, or possibly imap-wait-for-tag. Be prepared to single step
a lot until you find the proper function, and don't forget to look at
the " *nnimap* foo" buffer to see what the parser should be parsing.
prev parent reply other threads:[~2006-05-16 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 9:22 Alexander Kotelnikov
2006-05-15 11:46 ` Simon Josefsson
2006-05-15 12:40 ` Alexander Kotelnikov
2006-05-15 14:25 ` Simon Josefsson
2006-05-16 10:37 ` Alexander Kotelnikov
2006-05-16 11:05 ` Simon Josefsson
2006-05-16 11:48 ` Alexander Kotelnikov
2006-05-16 13:43 ` Simon Josefsson [this message]
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=87wtcm3x1g.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).