all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Nathan Dehnel <ncdehnel@gmail.com>,
	Janneke Nieuwenhuizen <janneke@gnu.org>,
	 guix-devel@gnu.org
Subject: Re: The e(macs)lephant in the room and the Guix Bang
Date: Sun, 24 Sep 2023 10:51:03 +0200	[thread overview]
Message-ID: <6f17bef4d03310c9a46d2a54db385d44533119d4.camel@gmail.com> (raw)
In-Reply-To: <CAEEhgEsfc0gXWMJ99VDYBy6saC7xhJz4kU6L96Ynvo+=NdTD3Q@mail.gmail.com>

Am Sonntag, dem 24.09.2023 um 02:37 -0500 schrieb Nathan Dehnel:
> > I'm sorry if my tone was too harsh, I now realise this is still
> > triggering old pain.
> 
> > Why is it still OK to for people to keep spreading negative
> > anecdotes about Emacs, and problematic to refute them or counter
> > them with positive anecdotes?
> 
> It was a mistake to say that. I felt the reflexive need to justify
> why I don't use emacs, or else people would just tell me to use it
> anyways as a result of talking about not knowing of a decent
> (alternative) lisp editor.
I mean, you could try using it anyways, whether it's vanilla emacs,
customized emacs, guile studio, or the heavily popularized spacemacs,
doom, etc. variants.  On the Guix side, it doesn't really matter, our
configuration works with packages based on Emacs.

It's fine if you prefer another editor, but don't count on us to write
documentation for every editor out there, especially when it almost
always turns out to be invoking "guix edit" followed by "git commit …"
or perhaps using that editor's built-in VC integration to do so.  I'm
also not convinced you need to bring the big guns of lisp editing to
the table.  From personal experience, an editor that autocompletes the
closing bracket and has parentheses matching capabilities suffices. 
The latter is even implemented by crude tools such as gnome-text-
editor.

> > It's been me believing exactly such lies that scared me away from
> > starting with Emacs for years, lost years in a way; something I
> > deeply regret: this has to stop.
> 
> I want to clarify that I'm not just repeating rumors and I actually
> have tried to use emacs.
There is a wide span of "tried emacs".  I personally wouldn't say I've
"tried" vi after hitting ESC :q once and being done or even that I've
tried using ed after vaguely figuring out how you can make it actually
change the contents of a file.

Now whether you want to qualify your experience further or not is up to
you, and even if you do, your personal choice of a suitable editor
remains personal.  However, I don't think that repeating the age old
jokes of "herp derp, me no likes defaults" as has happened in other
branches of this topic is helpful.  *The defaults in Emacs do not
matter.*  You don't need to be happy with the editor you get out of the
box.  You can change it into the editor you want and there's ample
documentation on how to do so.  Coming full circle, this is why we
reference Emacs in the manual, enough people collaborated to suggest a
workflow that works for them or at least goes in the right direction. 
However, I think it's fair to say that most folks' setup will differ
ever so slightly from what is presented there.

Cheers



  reply	other threads:[~2023-09-24  9:00 UTC|newest]

Thread overview: 31+ 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 [this message]
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     ` The Giraffe; the Pelican et al (was Re: The e(macs)lephant in the room and the Guix Bang) indieterminacy
2023-09-25 11:13       ` 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
  -- strict thread matches above, loose matches on Subject: below --
2023-09-20 18:00 Andy Tai
2023-10-02 14:56 ` Ludovic Courtès
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6f17bef4d03310c9a46d2a54db385d44533119d4.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --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.