unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christine Lemmer-Webber <cwebber@dustycloud.org>
To: Nathan Dehnel <ncdehnel@gmail.com>
Cc: atai@atai.org, guix-devel@gnu.org
Subject: Re: The e(macs)lephant in the room and the Guix Bang
Date: Wed, 27 Sep 2023 14:38:40 -0400	[thread overview]
Message-ID: <87cyy3wj5a.fsf@dustycloud.org> (raw)
In-Reply-To: <CAEEhgEvYwz1VpYSDu3zoB218ujbTCLbKPTA-Zd09ae45nitbQg@mail.gmail.com>

Nathan Dehnel <ncdehnel@gmail.com> writes:

> ________________________________
>
>> Hi, for some reason emacs has become the elephant in the room of the
>> discussion on contributing to guix.
>>
>> 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 don't use emacs either (because it's so impenetrable), so I just use
> kate instead, which isn't a great environment for me either. It has
> rainbow parens, but it doesn't balance them, which is a hassle. I keep
> using it though due to lack of time to browse through alternatives. I
> heard about guile-studio, but it doesn't appear to have a dark mode,
> and I imagine trying to add one would require a bunch of emacs-style
> screwing around with it.
>
> https://archive.fosdem.org/2022/schedule/event/lispforeveryone/
> This is the only setup for coding in lisp that has actually looked
> attractive to me. (Coding in wisp with colored blocks that transpiles
> to s-expressions) Though I haven't had the time (and probably
> expertise) to set it up for myself.

Happy to see this talk get some attention.  It does advocate a variety
of possible approaches, one of them Wisp (and the wisp-mode colored
block stuff is pretty awesome).

If you like that approach and want to not have to do the
parenthesis-balancing as much yourself, there's an interesting overlap
between Wisp and parinfer, which automatically infers the parentheses
from whitespace but keeps them in the actual source.  I have personally
never tried using parinfer for serious tasks though.  It still requires
an editor set up for those features.

Since Spritely is also using Guile heavily, we have also spent a lot of
time talking about possible directions for helping non-emacs-users get
going with our tooling.  Personally I think the biggest path to success
is likely to be seeing Guile support (starting with parenthetical Guile)
also be very strong in mainstream editors.  A lot has changed in the
programming editor world recently: LSP looks like a very promising
direction for this.  (Anyway, there's no decisionmaking yet in terms of
what we're doing, it just has come up quite a bit.)

Has anyone tried using an LSP-like environment and seeing if they can
get something approximating the comfort that Guile and Geiser users in
emacs have, I wonder?  I have seen there are a couple of guile LSP
packages but I have not personally tried them.

 - Christine


  parent reply	other threads:[~2023-09-27 18:45 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
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 [this message]
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

  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=87cyy3wj5a.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=atai@atai.org \
    --cc=guix-devel@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 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).