From: david.goldberg6@verizon.net (Dave Goldberg)
To: ding@gnus.org
Subject: Re: gcc-mark-as-read sometimes broken on Exchange
Date: Mon, 06 Dec 2010 15:53:58 -0500 [thread overview]
Message-ID: <84d3pehbbt.fsf@davestoy.home> (raw)
In-Reply-To: <m3hbexifdc.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 01 Dec 2010 18:15:27 +0100")
> Dave Goldberg <david.goldberg6@verizon.net> writes:
>> gnus-group-mark-article-read("nnimap+exchange:Sent Items" nil)
>> gnus-inews-do-gcc()
> The only way this could happen, I think, is if
> `nnimap-request-accept-article' returns nil as the article number. It
> would be interesting to find out why or how that happens. And whether
> that is what's happening. :-)
> If you get a raw article buffer (`C-u C-u g'), and put that text in a
> different buffer, and then eval
> (nnimap-request-accept-article "group.name" "server-name")
> what does it return?
Sorry, was away for a few days. Still happens with a git pull this
morning. I must be doing something wrong because when I try the above
I get this backtrace, with either server (cyrus or exchange):
Debugger entered--Lisp error: (wrong-type-argument processp nil)
process-buffer(nil)
proto-stream-get-response(nil 1 "\n")
proto-stream-open-tls("*nnimap*" #<buffer "*nnimap nnimap:cyrus nil *nntpd**<2>"> "nnimap:cyrus" "imaps" (:type ssl :shell-command "ssh %s imapd" :capability-command "1 CAPABILITY\n" :success " OK " :starttls-function #<compiled-function (capabilities) "...(21)" [match-data capabilities regexp string start "STARTTLS" nil match-data ... string-match "1 STARTTLS\n"] 4>))
open-protocol-stream("*nnimap*" #<buffer "*nnimap nnimap:cyrus nil *nntpd**<2>"> "nnimap:cyrus" "imaps" :type ssl :shell-command "ssh %s imapd" :capability-command "1 CAPABILITY\n" :success " OK " :starttls-function #<compiled-function (capabilities) "...(21)" [match-data capabilities regexp string start "STARTTLS" nil match-data (...) string-match "1 STARTTLS\n"] 4>)
nnimap-open-connection-1(#<buffer " *nntpd*">)
nnimap-open-connection(#<buffer " *nntpd*">)
nnimap-open-server("nnimap:cyrus")
nnimap-possibly-change-group(nil "nnimap:cyrus")
nnimap-request-accept-article("INBOX" "nnimap:cyrus")
eval((nnimap-request-accept-article "INBOX" "nnimap:cyrus"))
#<compiled-function (expression &optional eval-expression-insert-value) "...(18)" [eval-expression-insert-value expression values eval prin1 t] 3 824197 (list (read-from-minibuffer "Eval: " nil read-expression-map t ...) current-prefix-arg)>((nnimap-request-accept-article "INBOX" "nnimap:cyrus") nil)
call-interactively(eval-expression)
Thanks,
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2010-12-06 20:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 19:10 Dave Goldberg
2010-12-01 17:15 ` Lars Magne Ingebrigtsen
2010-12-06 20:53 ` Dave Goldberg [this message]
2010-12-06 22:24 ` Lars Magne Ingebrigtsen
2010-12-07 13:32 ` Dave Goldberg
2010-12-07 18:15 ` Dave Goldberg
2010-12-07 18:24 ` Dave Goldberg
2010-12-07 22:11 ` Dave Goldberg
2010-12-08 19:50 ` Dave Goldberg
2010-12-09 22:59 ` Lars Magne Ingebrigtsen
2010-12-10 16:47 ` Dave Goldberg
2010-12-16 16:35 ` Lars Magne Ingebrigtsen
2010-12-16 22:46 ` Dave Goldberg
2010-12-17 0:08 ` Tibor Simko
2010-12-17 16:37 ` Lars Magne Ingebrigtsen
2010-12-21 0:01 ` Tibor Simko
2010-12-17 16:35 ` Lars Magne Ingebrigtsen
2010-12-21 0:12 ` Tibor Simko
2011-01-02 6:59 ` Lars Magne Ingebrigtsen
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=84d3pehbbt.fsf@davestoy.home \
--to=david.goldberg6@verizon.net \
--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).