Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Can anyone explain this error message?
Date: Sat, 29 Jul 2017 11:08:49 -0400	[thread overview]
Message-ID: <86379fz3em.fsf@local.lan> (raw)
In-Reply-To: <87vamdzyrn.fsf@gmail.com>

Robert Pluim <rpluim@gmail.com> writes:

> Harry Putnam <reader@newsguy.com> writes:
>
>> When I start gnus, or scan for news/mail
>>
>> I get this error in echo area (wrapped for mail):
>>
>>   Mail source (directory :path /home/reader/spool/in/ :suffix .in
>>   :predicate #[(file) \301\b!\302\230\207 [file file-name-nondirectory
>>   cron_tr.in] 2]) error (Searching for program).  Continue? (y or n) y
>>
>
> If you do (setq debug-on-error t), then you should get a better
> backtrace telling you what's going on.
>

I've worked around for now. So don't have the same setup now, I'll
have to set it up in a sandbox to recreate.

But as I recall I did set debug on error (as an old time gnus user I
knew to try that).  As I recall it produced no back-trace... It might
not be considered a gnus error.  Or probably more likely I screwed
up the attempt somehow.


The problem produces a yes or no question and claims the error is in
not finding an un-named program.  But it has got to be involved with the
way gnus slurps *.in mbox files and sends them to like named (minus
the *.in part) nnml directories.

I'm running debian in a vbox vm on an `openindian' OS (an open source
branch of solaris 11).  I had inadvertently rm'ed my git branch of
emacs and some of its installed files I keep on a test area. Replaced
them with files from a zfs filesytem snapshot.

Hopefully it has something to do with me having screwed that up
somehow.

I'm going to try again from a clean start ... Maybe it will just go away.




      reply	other threads:[~2017-07-29 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 14:58 Harry Putnam
2017-07-27 15:26 ` Robert Pluim
2017-07-29 15:08   ` Harry Putnam [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=86379fz3em.fsf@local.lan \
    --to=reader@newsguy.com \
    --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).