From: "Ludovic Courtès" <ludo@gnu.org>
To: Andy Tai <atai@atai.org>
Cc: guix-devel@gnu.org
Subject: Re: The e(macs)lephant in the room and the Guix Bang
Date: Mon, 02 Oct 2023 16:56:39 +0200 [thread overview]
Message-ID: <87leclhy3c.fsf@gnu.org> (raw)
In-Reply-To: <CAJsg1E8FhCaXGJk5Dss9NGNWn0qsaT5PNrMKhGtC_q2CV1wATQ@mail.gmail.com> (Andy Tai's message of "Wed, 20 Sep 2023 11:00:56 -0700")
Hi Andy,
Andy Tai <atai@atai.org> skribis:
> Regardless of one's opinion of emacs, I just want to add that this is
> itself strange. I have contributed some (package definition) patches
> to guix, all without using emacs.
>
> I am not an emacs user, so emacs is not necessary for contributing to guix.
> For what it's worth, the emacs-motif package in Guix was my addition.
> I don't use it myself.
I agree. It’s great that some of us are so passionate about Emacs (and
I’m certainly one of them), but I think we should make sure not to
spread the idea that one *has* to master Emacs to contribute to Guix.
Quite a few long-time contributors do not use Emacs; the tooling (‘guix
edit’, ‘guix refresh’, ‘guix style’) is also there to provide a good
experience whether or not one uses Emacs.
Ludo’.
next prev parent reply other threads:[~2023-10-02 14:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 18:00 The e(macs)lephant in the room and the Guix Bang Andy Tai
2023-10-02 14:56 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-23 5:19 Nathan Dehnel
2023-09-23 7:37 ` Janneke Nieuwenhuizen
2023-09-23 8:58 ` paul
2023-09-23 10:00 ` Janneke Nieuwenhuizen
2023-09-24 7:37 ` Nathan Dehnel
2023-09-24 8:51 ` Liliana Marie Prikler
2023-09-25 11:19 ` MSavoritias
2023-09-25 18:54 ` Liliana Marie Prikler
2023-09-25 19:21 ` Simon Tournier
2023-09-25 11:09 ` MSavoritias
2023-10-02 11:23 ` Munyoki Kilyungi
2023-09-23 9:56 ` Ricardo Wurmus
2023-09-23 10:25 ` Ricardo Wurmus
2023-09-23 12:29 ` Ricardo Wurmus
2023-09-24 7:11 ` Nathan Dehnel
2023-09-24 20:19 ` Csepp
2023-09-24 21:46 ` Ricardo Wurmus
2023-09-27 18:38 ` Christine Lemmer-Webber
2023-09-28 6:12 ` Nathan Dehnel
2023-08-23 16:25 How can we decrease the cognitive overhead for contributors? Katherine Cox-Buday
2023-08-24 6:33 ` (
2023-08-26 0:39 ` Katherine Cox-Buday
2023-08-27 3:22 ` Maxim Cournoyer
2023-08-27 7:39 ` 宋文武
2023-08-28 11:42 ` Giovanni Biscuolo
2023-09-01 19:12 ` Imran Iqbal
2023-09-03 17:45 ` Ekaitz Zarraga
2023-09-03 21:05 ` indieterminacy
2023-09-03 21:16 ` Ekaitz Zarraga
2023-09-13 12:20 ` Fannys
2023-09-13 15:42 ` Maxim Cournoyer
2023-09-17 11:29 ` MSavoritias
2023-09-18 10:09 ` Simon Tournier
2023-09-19 16:35 ` The elephant in the room and the Guix Bang Giovanni Biscuolo
2023-09-20 8:21 ` Csepp
2023-09-20 8:45 ` The e(macs)lephant " Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-09-20 9:28 ` MSavoritias
2023-09-20 14:03 ` Ricardo Wurmus
2023-09-20 14:09 ` MSavoritias
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87leclhy3c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=atai@atai.org \
--cc=guix-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/guix.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).