From: Manuel Giraud <manuel@ledu-giraud.fr>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 53877@debbugs.gnu.org
Subject: bug#53877: 29.0.50; [PATCH] async Gnus/nnml
Date: Wed, 09 Feb 2022 10:52:39 +0100 [thread overview]
Message-ID: <87pmnwcqoo.fsf@elite.giraud> (raw)
In-Reply-To: <877da4pi2h.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 09 Feb 2022 09:20:22 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Manuel Giraud <manuel@ledu-giraud.fr> writes:
>
>> -(defcustom mail-source-crash-box "~/.emacs-mail-crash-box"
>> - "File where mail will be stored while processing it."
>> +(defcustom mail-source-crash-box-prefix "~/.emacs-mail-crash-box-"
>> + "Prefix of files where mail will be stored while processing it."
>> :type 'file)
>
> Is the point here that we want to have several mail-source-fetchers
> going in parallel?
Yes that's the point. After those patches, I've started to work on
moving `mail-source-fetch' from «callback method» to «process+sentinel
method». So far, I have done most simple ones: "file" and "directory"
sources.
>> +(defun mail-source-existing-crash-boxes ()
>> + (let ((directory (file-name-directory mail-source-crash-box-prefix))
>> + (partial (file-name-nondirectory mail-source-crash-box-prefix)))
>> + (mapcar #'(lambda (name) (file-name-concat directory name))
>> + (file-name-all-completions partial directory))))
>
> `directory-files' takes a MATCH parameter, and is the way to get
> matches -- not the completion machinery.
Thanks, I'll change that.
--
Manuel Giraud
next prev parent reply other threads:[~2022-02-09 9:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 14:22 bug#53877: 29.0.50; [PATCH] async Gnus/nnml Manuel Giraud
2022-02-08 20:33 ` Eric Abrahamsen
2022-02-09 9:00 ` Robert Pluim
2022-02-09 8:15 ` Lars Ingebrigtsen
2022-02-09 9:42 ` Manuel Giraud
2022-02-09 9:51 ` Lars Ingebrigtsen
2022-02-09 10:39 ` Manuel Giraud
2022-02-09 10:41 ` Lars Ingebrigtsen
2022-02-09 10:47 ` Manuel Giraud
2022-02-09 10:50 ` Lars Ingebrigtsen
2022-02-09 12:30 ` Manuel Giraud
2022-02-09 16:35 ` Eric Abrahamsen
2022-02-10 9:02 ` Manuel Giraud
2022-02-10 18:11 ` Eric Abrahamsen
2022-02-10 18:25 ` Eric Abrahamsen
2022-02-10 20:25 ` Eli Zaretskii
2022-02-10 20:37 ` Eric Abrahamsen
2022-02-11 10:57 ` Manuel Giraud
2022-02-11 17:53 ` Eric Abrahamsen
2022-02-09 8:20 ` Lars Ingebrigtsen
2022-02-09 9:52 ` Manuel Giraud [this message]
2022-02-09 20:26 ` Lars 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmnwcqoo.fsf@elite.giraud \
--to=manuel@ledu-giraud.fr \
--cc=53877@debbugs.gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).