Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
Subject: Re: nnimap against Cyrus imapd just stopped working
Date: Thu, 11 Jul 2002 20:17:41 +0200	[thread overview]
Message-ID: <87ptxuku2i.fsf@doohan.bang.priv.no> (raw)
In-Reply-To: <87u1n6kug9.fsf@doohan.bang.priv.no>

>>>>> Steinar Bang <sb@dod.no>:

>>>>> Steinar Bang <sb@dod.no>:
>>>>> Steinar Bang <sb@dod.no>:
>>>>> Steinar Bang <sb@dod.no>:
>>> [snip!]
>>>> Sigh!  Unless someone knows something clever, I guess this means I
>>>> have a *seriously* trashed .newsrc.eld file, and the only way out of
>>>> this is to create a new one from scratch?

>>> Hm... the problem may not be in the ~/.newsrc.eld at all.  I moved
>>> away the existing ~/.newsrc.eld, and the problem still persists.

>>> Below are the contents of the *Messages* buffer after a startup that
>>> ends with emacs displaying the *Group* buffer after the beep.

>> I set (setq debug-on-error t) and started Gnus in a fresh emacs.  This
>> is the backtrace I got:

>> Signaling: (wrong-type-argument stringp nil)
>> intern(nil [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0])
>> imap-mailbox-put(permanentflags nil)
>> imap-parse-resp-text-code()
>> imap-parse-resp-text()
>> imap-parse-response()
>> imap-arrival-filter(#<process imap<1>> "* FLAGS (\\Answered \\Flagged \\Draft \\Deleted \\Seen)\r\n* OK [PERMANENTFLAGS ()]  \r\n* 0 EXISTS\r\n* 0 RECENT\r\n* OK [UIDVALIDITY 1025304220]  \r\n* OK [UIDNEXT 2]  \r\n6 OK [READ-ONLY] Completed\r\n* FLAGS (\\Answered \\Flagged \\Draft \\Deleted \\Seen)\r\n* OK [PERMANENTFLAGS ()]  \r\n* 16071 EXISTS\r\n* 16071 RECENT\r\n* OK [UNSEEN 1]  \r\n* OK [UIDVALIDITY 1]  \r\n* OK [UIDNEXT 16082]  \r\n7 OK [READ-ONLY] Completed\r\n8 NO Mailbox does not exist\r\n* FLAGS (\\Answered \\Flagged \\Draft \\Deleted \\Seen)\r\n* OK [PERMANENTFLAGS ()]  \r\n* 0 EXISTS\r\n* 0 RECENT\r\n* OK [UIDVALIDITY 1026364784]  \r\n* OK [UIDNEXT 1]  \r\n9 OK [READ-ONLY] Completed\r\n* FLAGS (\\Answered \\Flagged \\Draft \\Deleted \\Seen)\r\n* OK [PERMANENTFLAGS ()]  \r\n* 0 EXISTS\r\n* 0 RECENT\r\n* OK [UIDVALIDITY 1026198897]  \r\n* OK [UIDNEXT 1]  \r\n10 OK [READ-ONLY] Completed\r\n11 NO Mailbox does not exist\r\n* FLAGS (\\Answered \\Flagged \\Draft \\Deleted \\Seen)\r\n* OK [PERMANENTFLAGS ()]  \r\n* 385 EXISTS\r\n* 385 RECENT\r\n* OK [UNSEEN 1]  \r\n* OK [UIDVALIDITY 856603065]  \r\n* OK [UIDNEXT 11839]  \r\n12 OK [READ-ONLY] C")

>> Is the second argument to imap-mailbox-put the cause behind the 
>> error in process filter: Wrong type argument: stringp, nil [2 times]
>> message?

>> What is the second argument to imap-mailbox-put?  C-h f imap-mailbox-put RET
>> gives the following message:
>> imap-mailbox-put is a compiled Lisp function in `imap'.
>> (imap-mailbox-put PROPNAME VALUE &optional MAILBOX BUFFER)
>> not documented

>> Not very useful on what VALUE is.

> I tried edebug-defun on imap-mailbox-put, but I got the beep and the
> error message without the debugger being entered.

I have now tried edebug-defun on all functions on the stack about.  I
tried each of them in a fresh emacs.  None of them caused emacs to
enter the debugger.



  reply	other threads:[~2002-07-11 18:17 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09 20:10 Steinar Bang
2002-07-09 20:20 ` Simon Josefsson
2002-07-09 20:34   ` Steinar Bang
2002-07-09 20:38     ` Steinar Bang
2002-07-09 20:44       ` Simon Josefsson
2002-07-09 20:55         ` Steinar Bang
2002-07-09 21:04           ` Simon Josefsson
2002-07-09 21:51             ` Steinar Bang
2002-07-10 11:02               ` Simon Josefsson
2002-07-10 11:12                 ` Steinar Bang
2002-07-09 21:53           ` Steinar Bang
2002-07-10  5:58             ` Steinar Bang
2002-07-09 20:41     ` Simon Josefsson
2002-07-09 20:50       ` Steinar Bang
2002-07-09 21:02         ` Simon Josefsson
2002-07-09 21:43           ` Steinar Bang
2002-07-10 11:05             ` Simon Josefsson
2002-07-10 11:17               ` Steinar Bang
2002-07-10 11:26                 ` Simon Josefsson
2002-07-10 11:43                   ` Steinar Bang
2002-07-10 12:39                   ` Kai Großjohann
2002-07-10 14:21                     ` Reiner Steib
2002-07-11  8:18                       ` Kai Großjohann
2002-07-11 18:34                         ` group and topic parameters (was: nnimap against Cyrus imapd just stopped working) Reiner Steib
2002-07-12  0:49                           ` Janne Rinta-Mänty
2002-07-10 22:34               ` nnimap against Cyrus imapd just stopped working Steinar Bang
2002-07-11 10:37                 ` A .newsrc.eld validator? (Was: nnimap against Cyrus...) Steinar Bang
2002-07-11 16:45                 ` nnimap against Cyrus imapd just stopped working Steinar Bang
2002-07-11 17:56                   ` Steinar Bang
2002-07-11 18:09                     ` Steinar Bang
2002-07-11 18:17                       ` Steinar Bang [this message]
2002-07-11 18:51                         ` Steinar Bang
2002-07-26 12:18                           ` Simon Josefsson
2002-07-27  9:38                             ` Steinar Bang
2002-07-11 20:01               ` Steinar Bang
2002-07-11 22:24                 ` Amos Gouaux
2002-07-11 22:33                   ` Amos Gouaux
2002-07-12  5:54                     ` Steinar Bang
2002-07-10  8:50       ` Kai Großjohann

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=87ptxuku2i.fsf@doohan.bang.priv.no \
    --to=sb@dod.no \
    /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).