From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: ding <ding@gnus.org>
Subject: Re: Moving mail generates 'quit' signal
Date: Thu, 19 Mar 2020 00:03:53 -0700 [thread overview]
Message-ID: <87r1xox1uu.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <871rpoubi8.fsf@emailmessageidheader.nil> (Bob Newell's message of "Wed, 18 Mar 2020 20:03:43 -1000")
Bob Newell <bobnewell@bobnewell.net> writes:
> Aloha,
>
> I've started to fetch mail from two secondary sources. One is
> an IMAP server and all is well. The other is POP only and I've
> run into an odd issue.
>
> I have a function that I call after fetching to move mail from
> the inbox of the secondary source to my gmail inbox, so
> everything will be in the same place in the end. For the
> secondary IMAP server this works but for the POP server, I get
> a 'quit' condition, which I'm unable to completely trace thus
> far.
>
> Here's the operative code in question.
>
> First the POP server setup, pretty standard.
>
> (add-to-list 'gnus-secondary-select-methods '(nnml "pop.netzero.com"))
> (setq mail-sources '((pop :server "pop.netzero.com"
> :user "thatwouldbeme"
> :password "highlysecret"
> :port 110
> )
> ))
>
> Now the move mail stuff. This is a little long but the quit
> condition arises below in gnus-group-read-group
This will end up calling `gnus-summary-read-group', which calls
`gnus-summary-read-group-1', which up top calls `gnus-select-newsgroup',
and puts its return value into the let-bound variable `did-select'.
If `gnus-select-newsgroup' can't find any articles to read, it returns
the symbol `quit'. Then gnus-summary-read-group-1' sees that (in line
4037), and ends up signalling a quit error.
It's my bed time, but I'm guessing you should be using a function other
than `gnus-group-read-group'. All you want to be doing is checking the
group for new messages, right? This function is for interactively
entering the group, so the `quit' makes more sense in that situation.
If you haven't resolved this by morning my time, I can take another look
:)
Eric
next prev parent reply other threads:[~2020-03-19 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 6:03 Bob Newell
2020-03-19 7:03 ` Eric Abrahamsen [this message]
2020-03-19 18:34 ` Bob Newell
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=87r1xox1uu.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=bobnewell@bobnewell.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).