[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The e(macs)lephant in the room and the Guix Bang
From: |
Ricardo Wurmus |
Subject: |
Re: The e(macs)lephant in the room and the Guix Bang |
Date: |
Wed, 20 Sep 2023 16:03:34 +0200 |
User-agent: |
mu4e 1.10.7; emacs 29.0.92 |
MSavoritias <email@msavoritias.me> writes:
> On 9/20/23 11:45, Nguyễn Gia Phong via Development of GNU Guix and the
> GNU System distribution. wrote:
>> On 2023-09-20 at 10:21+02:00, Csepp wrote:
>>> It's better if we have at least one *well documented* developer setup,
>>> than if we have a bunch of (sometimes conflicting) partial docs
>>> for setting up certain subsystems.
>>>
>>> Emacs can be pretty good, once you do (setq make-defaults-not-suck 1)
>>> a bunch of times.
>> Or even more outrageous, an overriden Emacs package
>> with all the good stuff for Guix development.
>> We already have guix shell that spawns a shell
>> and guix edit that spawns an editor, why no guix boot
>> that spawns an OS^W^W Emacs with appropriate defaults?
>>
>> Disclaimer: I use the devil editor that goes by the number
>> of VI VI VI, so take this suggestion with a grain of salt.
>>
>
> Can't the guile editor be that?
>
> It kind of tries to be already. We just need to promote it and dogfood
> it more.
Do you mean Guile Studio?[1]
It was really only intended to be a pre-configured editor for new
Guilers, which is why it includes the picture language and Geiser with
picture display.
But as I wrote there
There are many more things that can be done to make Emacs less
confusing for people who use it just as a Guile IDE. I would be happy
to hear your suggestions or apply patches to improve Guile Studio!
This is still true today.
[1]: https://elephly.net/guile-studio/
--
Ricardo
- Re: How can we decrease the cognitive overhead for contributors?, (continued)
- Re: How can we decrease the cognitive overhead for contributors?, Ekaitz Zarraga, 2023/09/13
- Re: How can we decrease the cognitive overhead for contributors?, MSavoritias, 2023/09/17
- Re: How can we decrease the cognitive overhead for contributors?, Simon Tournier, 2023/09/18
- contribute with content in our official help pages?, Giovanni Biscuolo, 2023/09/19
- The elephant in the room and the Guix Bang., Giovanni Biscuolo, 2023/09/19
- Re: The elephant in the room and the Guix Bang., Simon Tournier, 2023/09/20
- Re: The elephant in the room and the Guix Bang., Giovanni Biscuolo, 2023/09/20
- Re: The elephant in the room and the Guix Bang., Csepp, 2023/09/20
- Re: The e(macs)lephant in the room and the Guix Bang, Nguyễn Gia Phong, 2023/09/20
- Re: The e(macs)lephant in the room and the Guix Bang, MSavoritias, 2023/09/20
- Re: The e(macs)lephant in the room and the Guix Bang,
Ricardo Wurmus <=
- Re: The e(macs)lephant in the room and the Guix Bang, MSavoritias, 2023/09/20
- Re: How can we decrease the cognitive overhead for contributors?, Ricardo Wurmus, 2023/09/14
- Re: How can we decrease the cognitive overhead for contributors?, MSavoritias, 2023/09/18
- Re: How can we decrease the cognitive overhead for contributors?, Sarthak Shah, 2023/09/14
- Re: How can we decrease the cognitive overhead for contributors?, Simon Tournier, 2023/09/15
- Re: How can we decrease the cognitive overhead for contributors?, MSavoritias, 2023/09/13
- Re: How can we decrease the cognitive overhead for contributors?, Imran Iqbal, 2023/09/22
- Re: How can we decrease the cognitive overhead for contributors?, Katherine Cox-Buday, 2023/09/22
- Re: How can we decrease the cognitive overhead for contributors?, Ekaitz Zarraga, 2023/09/22
- Re: How can we decrease the cognitive overhead for contributors?, MSavoritias, 2023/09/22