Gnus development mailing list
 help / color / mirror / Atom feed
From: hput <hput3@fastmail.fm>
To: ding@gnus.org
Subject: Re: gnus quit slurping mbox files with special [.in] suffix
Date: Fri, 08 Oct 2021 16:31:42 -0400	[thread overview]
Message-ID: <87ily7s1g1.fsf@local.lan> (raw)
In-Reply-To: <877deqfrez.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> reader <hput3@fastmail.fm> writes:
>
>> (setq mail-sources
>>       '((file :path "/var/spool/mail/reader")
>>         (directory :path "/spool/in/"
>>                    :suffix ".in")))
>>
>> In case anyone wonders... you see /spoo/ is at root (/) but the spool
>> directory and its contents has owner:group of my user.  The list of
>> mbox files in there all end `.in' and are chmod 600.
>
> I think that looks like the correct syntax.  mail-source.el hasn't
> changed since January 2021, so it's odd that this suddenly stopped
> working.  Could you perhaps try edebugging through
> mail-source-fetch-directory to see what's happening?

The good news is, I upped my emacs to latest and lo & behold, it began
the sorely missed slurping of *.in groups.

I think it must be that somewhere beyond the upper stratosphere they
knew that larsi was on the case... thanks for your far reaching clout. 



      reply	other threads:[~2021-10-08 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01  1:46 reader
2021-10-06  9:12 ` Lars Ingebrigtsen
2021-10-08 20:31   ` hput [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=87ily7s1g1.fsf@local.lan \
    --to=hput3@fastmail.fm \
    --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).