From: Pierre Neidhardt <mail@ambrevar.xyz>
To: zimoun <zimon.toutoune@gmail.com>, "Ludovic Courtès" <ludo@gnu.org>
Cc: Development of GNU Guix and the GNU System distribution
<guix-devel@gnu.org>, Ryan Prior <ryanprior@hey.com>
Subject: Re: Reviving Emacs-Guix
Date: Sat, 14 Nov 2020 18:30:50 +0100 [thread overview]
Message-ID: <87h7prx2ut.fsf@ambrevar.xyz> (raw)
In-Reply-To: <86sg9byj07.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3035 bytes --]
To answer all your points: `guix repl` woud only be used for queries,
not for transactions.
For the latter, sending shell crafted commands have worked well for me.
They can be sent to an M-x shell, Vterm or Eshell buffer.
Example: the user wants to build Emacs?
Make a dedicated "M-x shell" buffer and send "guix build emacs" there.
The great benefit is that the user is in a familiar environment and can
do stuff like "C-c C-c"
>> Actually 9 months, but the issue has been there forever.
>
> Yes, as any issue before being reported. ;-)
No, sometimes issue appear after features are implemented, or after
regressions.
It's not the case here: these issues exist since the beginning of
Geiser.
It's important, because it highlights design flaws.
> I do not understand your point. You are mixing 2 topics:
>
> - Emacs front-end for Guix
> - Scheme mode for Emacs
I don't want to mix the 2, emacs-guix does.
I'm suggesting precisely this: don't mix up the Schemer environment with
emacs-guix because of the load of trouble it brings in.
> and then applying kind of transitivity: Geiser is poor (compared to
> SLIME or SLY) so it cannot be used for Guix at all. Applying the same
> trick: the number of packages in Guix is poor (compared to Debian or
> Nix) so Guix cannot be used at all.
This is not what I'm saying ;)
>> We have 2 options:
>>
>> - Fixing Geiser, which might take a long time, leaving us with a broken
>> emacs-guix for the time being.
>> It's not even clear that it can be done without rewriting everything.
>>
>> - Or use `guix repl`, which is known to work, already has working code
>> out there, and can be deployed in a week or two.
>>
>> I find the second option more attractive.
>
> You do not convince me. Because you do not answer to the question: how
> one could work interactively without Geiser? How «pipe to “guix repl”»
> could lead to interactive work?
See above.
> For example, persistence between 2
> calls.
emacs-guix never relies on persistence if I'm not mistaken.
My suggestion indeed lacks persistence, but at least it works for now
until we figure out something better.
> And solving that is somehow inheriting from ’comint-mode’ and so
> more less rewrite ’geiser-repl.el’; but Guix specific only. Maybe I am
> missing the obvious.
Sorry I didn't get this part.
> Maybe «pipe to “guix repl”» could simplify what “guix-popup” does.
> Even, I am not convinced.
Not just that, but listing packages, package details, output listing,
profile listing, generation listing, etc.
Try it out in Nyxt, you'll see for yourself :)
> Today, the real issue with Emacs-Guix is not Geiser, at all.
Emacs-Guix can't install a package a package that needs to be built
because of Geiser. So yes, Geiser is the issue.
> Well, at the end, the only judge is the effective code. ;-)
I have a proof of concept that works :)
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2020-11-14 17:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 5:07 Announcing emacs-guix-packaging Ryan Prior
2020-11-10 13:30 ` Pierre Neidhardt
2020-11-12 20:53 ` Ludovic Courtès
2020-11-13 1:28 ` Ryan Prior
2020-11-13 9:45 ` Pierre Neidhardt
2020-11-13 13:20 ` zimoun
2020-11-13 14:54 ` John Soo
2020-11-13 16:54 ` Reviving Emacs-Guix Ludovic Courtès
2020-11-13 17:13 ` John Soo
2020-11-13 18:42 ` zimoun
2020-11-16 8:56 ` Ludovic Courtès
2020-11-14 9:42 ` Pierre Neidhardt
2020-11-14 12:57 ` zimoun
2020-11-14 15:59 ` Pierre Neidhardt
2020-11-14 16:56 ` zimoun
2020-11-14 17:30 ` Pierre Neidhardt [this message]
2020-11-14 18:40 ` zimoun
2020-11-14 19:15 ` Pierre Neidhardt
2020-11-14 19:52 ` Ricardo Wurmus
2020-11-14 21:29 ` zimoun
2020-11-15 7:37 ` Pierre Neidhardt
2020-11-15 13:15 ` zimoun
2020-11-15 14:11 ` Pierre Neidhardt
2020-11-15 15:23 ` zimoun
2020-11-15 15:45 ` Pierre Neidhardt
2020-11-15 16:05 ` zimoun
2020-11-14 21:11 ` zimoun
2020-11-15 7:53 ` Pierre Neidhardt
2020-11-14 19:49 ` Ricardo Wurmus
2020-11-15 7:36 ` Pierre Neidhardt
2020-11-16 9:02 ` Ludovic Courtès
2020-11-16 9:18 ` Pierre Neidhardt
2020-11-16 12:01 ` zimoun
2020-11-16 12:20 ` Pierre Neidhardt
2020-11-16 12:47 ` zimoun
2020-11-17 7:53 ` Pierre Neidhardt
2020-11-13 12:31 ` Announcing emacs-guix-packaging zimoun
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=87h7prx2ut.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=ryanprior@hey.com \
--cc=zimon.toutoune@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).