From: Jeremy Hankins <nowan@nowan.org>
To: info-gnus-english@gnu.org
Subject: Re: Mail source problem (?)
Date: Sat, 26 Jan 2019 18:42:12 -0500 [thread overview]
Message-ID: <87fttf3s17.fsf@opal.nowan.org> (raw)
In-Reply-To: <875zubqj64.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Jeremy Hankins <nowan@nowan.org> writes:
>
>> Recently (after an update to emacs about a month ago, debian unstable) I
>> started getting a message when checking mail about a mail source error:
>>
>> Mail source (file :path /var/mail/nowan) error (Searching for program). Continue? (yes or no)
>>
>> This is apparently from my secondary select method meant to pull in
>> localhost mail, and it doesn't seem to be anything obvious like a
>> permissions problem. It doesn't make any difference whether I respond
>> yes or no, either way mail out of /var/mail is ignored and the rest of
>> my mail is fetched successfully.
>>
>> It's clearly some sort of compatibility issue and I figured I needed to
>> sort through my gnus file and figure out where it was coming from --
>> annoying but no big deal. And since it's only a small minority of my
>> mail affected it hasn't bugged me enough to pursue it till now.
>>
>> But the annoying thing, apart from the fact that the error is a bit
>> obscure (what program?), is that if I turn debug-on-quit on so as to
>> figure out where the bug is being triggered and why, the message goes
>> away removing my chance to trigger the debugger.
>>
>> Any ideas either a) what the problem fetching local mail is, or b) why
>> debug-on-quit makes the message go away?
>
> Are you sure it isn't `debug-on-error' you want? Unless you're getting a
> hang when checking mail, and then trying to C-g out of the hang, you
> won't trigger `debug-on-quit'. Maybe try the former?
I tried that but it doesn't trigger debug-on-error, it's just a prompt
that pops up in the minibuffer. Normally, I'd wait for the message to
pop up and hit C-G, triggering the debugger. But with debug-on-quit
toggled on, the message never shows up and gnus silently fails to load
mail from that source. There is mail in the mail spool, and I also
tried deleting and recreating the spool in case something was corrupted
and causing gnus to choke.
--
Jeremy Hankins <nowan@nowan.org>
next prev parent reply other threads:[~2019-01-26 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 17:44 Jeremy Hankins
2019-01-26 20:05 ` Eric Abrahamsen
2019-01-26 23:42 ` Jeremy Hankins [this message]
2019-01-27 0:08 ` Jeremy Hankins
2019-01-29 20:24 ` Eric Abrahamsen
2019-01-30 13:28 ` Jeremy Hankins
2019-02-02 16:29 ` Eric Abrahamsen
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=87fttf3s17.fsf@opal.nowan.org \
--to=nowan@nowan.org \
--cc=info-gnus-english@gnu.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).