From: Fernando de Morais <fernandodemorais.jf@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: info-gnus-english@gnu.org
Subject: Re: Help needed: nnmaildir and expire-group parameter.
Date: Wed, 30 Nov 2022 15:19:30 -0300 [thread overview]
Message-ID: <87tu2g71al.fsf@gmail.com> (raw)
In-Reply-To: <87o7soz7k8.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 30 Nov 2022 09:16:39 -0800")
Hello Eric,
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Apparently it's not using the same parameter names as everyone else,
> because nnmaildir lets the user put arbitrary Lisp expressions in as
> values -- it runs the values through `eval' at Gnus startup time. I
> think the idea is that, because the parameter values are handled
> differently, the parameter names should be different.
>
> This doesn't particularly make sense, and the use of `eval' in regular
> code is pretty heavily discouraged these days. This code seems to have
> been in nnmaildir.el since The Dawn of Time, and I'm sure that at one
> point someone depended heavily on being able to `eval' their parameter
> values.
Understood.
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> It would be relatively simple to fix: we could leave the existing
> handling of nnmaildir's own parameters in place, but also start
> retrieving the normal expiry parameters, using Gnus' regular
> `gnus-group-parameter-*' functions.
I'm glad to know that the implementation would be more or less
simple. I'll check the `gnus-group-parameter-*' functions and try to
play with `nnmaildir' with this idea in mind.
Thanks!
--
Regards,
Fernando de Morais.
prev parent reply other threads:[~2022-11-30 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 22:11 Fernando de Morais
2022-11-29 19:17 ` Eric Abrahamsen
2022-11-29 19:21 ` Emanuel Berg
2022-11-29 21:59 ` Fernando de Morais
2022-11-30 17:16 ` Eric Abrahamsen
2022-11-30 18:19 ` Fernando de Morais [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=87tu2g71al.fsf@gmail.com \
--to=fernandodemorais.jf@gmail.com \
--cc=eric@ericabrahamsen.net \
--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).