From: Emanuel Berg <incal@dataswamp.org>
To: emacs-devel@gnu.org
Subject: Re: [External] : Re: master a7c65fc666: Allow nil value for filter-buffer-substring-function
Date: Wed, 21 Sep 2022 09:06:36 +0200 [thread overview]
Message-ID: <87a66ti4ub.fsf@dataswamp.org> (raw)
In-Reply-To: 87pmfpb4ed.fsf@web.de
Michael Heerdegen wrote:
>> The argument that allowing a nil value for such a variable
>> "breaks" the use of `add-function' is no more than
>> a re-assertion that the variable shouldn't have
>> a nil value.
>
> I don't think this is true. You are missing an, or even the,
> important point IMO.
When fixing something breaks something else this implies
poor modularization.
But as for what to do, well obviously what it breaks must be
fixed as well and everything else connected to it in the
same way.
And interestingly, fixing such issues can be a, or even the,
method to achieve modularization.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-09-21 7:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166359943394.15847.12726646376922950024@vcs2.savannah.gnu.org>
[not found] ` <20220919145714.5036DC00872@vcs2.savannah.gnu.org>
2022-09-19 15:10 ` master a7c65fc666: Allow nil value for filter-buffer-substring-function Robert Pluim
2022-09-19 15:56 ` Stefan Kangas
2022-09-19 20:37 ` Stefan Monnier
2022-09-20 8:08 ` Robert Pluim
2022-09-20 13:23 ` Stefan Monnier
2022-09-19 20:56 ` Stefan Monnier
2022-09-19 21:15 ` Stefan Kangas
2022-09-19 21:58 ` Stefan Monnier
2022-09-20 6:26 ` Stefan Kangas
2022-09-20 15:41 ` [External] : " Drew Adams
2022-09-21 6:58 ` Michael Heerdegen
2022-09-21 7:06 ` Emanuel Berg [this message]
2022-09-21 15:59 ` Drew Adams
2022-09-22 9:59 ` Michael Heerdegen
2022-09-22 15:39 ` Drew Adams
2022-09-23 13:19 ` Stefan Monnier
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=87a66ti4ub.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-devel@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.
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).