From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: rpluim@gmail.com, emacs-devel@gnu.org, stefankangas@gmail.com,
rms@gnu.org
Subject: Re: Always-true predicate?
Date: Fri, 19 Feb 2021 15:53:26 +0200 [thread overview]
Message-ID: <83eehc2mg9.fsf@gnu.org> (raw)
In-Reply-To: <87lfbkrx9r.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 19 Feb 2021 14:40:32 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Stefan Kangas <stefankangas@gmail.com>, rpluim@gmail.com, rms@gnu.org,
> emacs-devel@gnu.org
> Date: Fri, 19 Feb 2021 14:40:32 +0100
>
> I think using function values in user options is fine -- the Emacs
> developers can never get cover all behavioural permutations that people
> would like to see, so allowing them to supply their own code is helpful.
Allowing a function as _one_ of the values is okay-ish, provided that
we don't do that too willy-nilly, where atoms could do the job. One
example of what I'd like NOT to see is using 'ignore as such a
function value -- we should use nil instead. (And likewise for the
always-true predicate being discussed here.)
But my main gripe is about options whose values can only be functions,
and nothing else. No one will convince me that Emacs developers
cannot come up with meaningful values that aren't functions for some
option.
next prev parent reply other threads:[~2021-02-19 13:53 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 12:01 Always-true predicate? Lars Ingebrigtsen
2021-02-17 12:31 ` Andrea Corallo via Emacs development discussions.
2021-02-17 12:40 ` Lars Ingebrigtsen
2021-02-17 16:59 ` Barry Fishman
2021-02-19 15:24 ` Stefan Kangas
2021-02-17 13:16 ` Basil L. Contovounesios
2021-02-17 18:56 ` Pip Cet
2021-02-17 19:19 ` Lars Ingebrigtsen
2021-02-17 19:31 ` Pip Cet
2021-02-17 19:37 ` Lars Ingebrigtsen
2021-02-17 20:18 ` Teemu Likonen
2021-02-17 22:25 ` [External] : " Drew Adams
2021-02-17 23:04 ` Basil L. Contovounesios
2021-02-17 23:13 ` Drew Adams
2021-02-17 23:01 ` Stefan Monnier
2021-02-19 11:27 ` Pip Cet
2021-02-19 15:07 ` Stefan Monnier
2021-02-19 19:04 ` Pip Cet
2021-02-19 20:11 ` Stefan Monnier
2021-02-20 9:40 ` Pip Cet
2021-02-20 13:58 ` Stefan Monnier
2021-02-19 5:39 ` Richard Stallman
2021-02-19 8:52 ` Robert Pluim
2021-02-19 9:10 ` Eli Zaretskii
2021-02-19 12:12 ` Eli Zaretskii
2021-02-19 12:52 ` Stefan Kangas
2021-02-19 13:00 ` Lars Ingebrigtsen
2021-02-19 13:34 ` Eli Zaretskii
2021-02-19 13:40 ` Lars Ingebrigtsen
2021-02-19 13:53 ` Eli Zaretskii [this message]
2021-02-19 14:05 ` Lars Ingebrigtsen
2021-02-19 18:04 ` [External] : " Drew Adams
2021-02-19 14:42 ` Stefan Monnier
2021-02-20 12:47 ` Lars Ingebrigtsen
2021-02-20 12:49 ` Lars Ingebrigtsen
2021-02-20 14:03 ` Stefan Monnier
2021-02-20 14:20 ` Lars Ingebrigtsen
2021-02-20 14:55 ` Stefan Monnier
2021-02-20 15:05 ` Lars Ingebrigtsen
2021-02-20 15:21 ` Stefan Monnier
2021-02-21 12:50 ` Robert Pluim
2021-02-21 13:04 ` Lars Ingebrigtsen
2021-02-19 15:09 ` Stefan Kangas
2021-02-19 15:22 ` Eli Zaretskii
2021-02-19 18:17 ` [External] : " Drew Adams
2021-02-19 18:41 ` Eli Zaretskii
2021-02-22 5:02 ` chad
2021-02-22 15:20 ` Eli Zaretskii
2021-02-22 23:07 ` chad
2021-02-21 6:12 ` Richard Stallman
2021-02-21 15:12 ` Eli Zaretskii
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=83eehc2mg9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
--cc=rpluim@gmail.com \
--cc=stefankangas@gmail.com \
/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).