From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: Psionic K <psionik@positron.solutions>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Strategies for Composable Modular Configuration?
Date: Thu, 23 Nov 2023 14:19:03 +0300 [thread overview]
Message-ID: <30a1af86-ec8f-4371-95fa-2246bdf955da@gmail.com> (raw)
In-Reply-To: <CADQMGAS6TyszQrgCqjFYEZ3=iO0-meFTpJ0-LhgLgZeAvwTHXQ@mail.gmail.com>
I'm not sure that I fully understand what you're suggesting... I've been
a casual Nixos user for years and even contribute from time to time, but
nothing made me really care about flakes. So to try and explain this in
a more practical manner, it's something like this:
There's a portal lets say emacs-tweaks.gnu.org. It operates much the
same way as a package repository, but the contents of it are not
features(packages), but tweaks(flakes, pedals, whatever). The difference
between a feature and a tweak is roughly that features implement new
behavior, while tweaks just modify existing features to some requirement.
Your definition of tweaks also does not allow for composition. Which
means that most of them are limited to a single feature, which IMHO is
not going to provide much ROI either. Because most of those tweaks are
going to be isolated single variable tweaks and that's not where the
problem lies. It's also not going to fully take over most of the
configuration needs because you can't re-implement Spacemacs(on Doom,
whatever) using such a limited system.
Correct me if I misunderstood anything.
next prev parent reply other threads:[~2023-11-23 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 7:25 Strategies for Composable Modular Configuration? Psionic K
2023-11-22 12:58 ` Nikolay Kudryavtsev
2023-11-22 13:58 ` Psionic K
2023-11-23 11:19 ` Nikolay Kudryavtsev [this message]
2023-11-24 1:52 ` Psionic K
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=30a1af86-ec8f-4371-95fa-2246bdf955da@gmail.com \
--to=nikolay.kudryavtsev@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=psionik@positron.solutions \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.