From: indieterminacy <indieterminacy@libre.brussels>
To: paul <goodoldpaul@autistici.org>
Cc: Janneke Nieuwenhuizen <janneke@gnu.org>,
Nathan Dehnel <ncdehnel@gmail.com>,
atai@atai.org, guix-devel@gnu.org
Subject: The Giraffe; the Pelican et al (was Re: The e(macs)lephant in the room and the Guix Bang)
Date: Sat, 23 Sep 2023 14:59:45 +0200 [thread overview]
Message-ID: <331eef527aca4c69dc8ffde867cedd6e@libre.brussels> (raw)
In-Reply-To: <2a710ca0-466b-0d6e-9768-60b7904178cc@autistici.org>
I would assume that people who dont use Emacs are entitled to document
their experiences using their weapon(s) of choice within the Guix
knowledge corpus.
Sure, consider and discuss governance and workflows... but people
complaining that Emacs users have documented their techniques to a
better standard than non Emacs users within an operating system's
documentation is bordering on the ridiculous.
On 23-09-2023 10:58, paul wrote:
> Dear Janneke,
>
> On 9/23/23 09:37, Janneke Nieuwenhuizen wrote:
>> Nathan Dehnel writes:
>>
>>> I don't use emacs either (because it's so impenetrable)
>> Emacs might be somewhat different from what you know, but this is
>> utter
>> bollocks.
>
> Thank you for your opinion but it's just that: a subjective judgement
> based on your own episodic experience. Which is definitely valid but
> unrealistically shared by so many to be able to define Nathan's
> experience "utter bollocks".
>
> I think this attitude (in my experience typical of GNU maintainers)
> where their way of doing computation is more blessed or holier or
> better sometimes really ruins the social interactions happening around
> Guix (which is the safest community in the GNU project imho, probably
> also due to the distance they rightfully posed during the whole
> stallman drama).
>
> It's especially problematic when people in power such as maintainers do
> not realize their role in the community. You have more power, probably
> due to your investment you have a clearer vision of where the project
> is going as well. You are supposed to be a role model for new users and
> contributors.
>
>> If he could learn, most anyone should be able to pick it
>> up.
>> People are still indenting their code manually today, etc... it's
>> ridiculous.
> This behavior is not ok. Again, please, stop throwing your judgement on
> people. Potential users or contributors even.
>> Also, magit.
>
> I use Emacs, love magit, I used to use it daily also at $day_job on
> Windows because it's just so good, but I can assure you most of Git
> users never heard of it and live their life pretty happily.
>
> giacomo
--
Jonathan McHugh
indieterminacy@libre.brussels
next prev parent reply other threads:[~2023-09-23 13:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 5:19 The e(macs)lephant in the room and the Guix Bang 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-09-25 20:34 ` Emacs and Guix (was Re: The e(macs)lephant in the room and the Guix Bang) Simon Tournier
2023-09-28 7:19 ` Efraim Flashner
2023-10-02 11:23 ` The e(macs)lephant in the room and the Guix Bang Munyoki Kilyungi
2023-09-23 12:59 ` indieterminacy [this message]
2023-09-25 11:13 ` The Giraffe; the Pelican et al (was Re: The e(macs)lephant in the room and the Guix Bang) MSavoritias
2023-09-25 20:35 ` Simon Tournier
2023-09-26 7:33 ` indieterminacy
2023-09-23 9:56 ` The e(macs)lephant in the room and the Guix Bang 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
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=331eef527aca4c69dc8ffde867cedd6e@libre.brussels \
--to=indieterminacy@libre.brussels \
--cc=atai@atai.org \
--cc=goodoldpaul@autistici.org \
--cc=guix-devel@gnu.org \
--cc=janneke@gnu.org \
--cc=ncdehnel@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 external index
https://git.savannah.gnu.org/cgit/guix.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.