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: Sun, 15 Nov 2020 08:53:32 +0100 [thread overview]
Message-ID: <87eekv5a4j.fsf@ambrevar.xyz> (raw)
In-Reply-To: <86h7pry77b.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3226 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
>> `guix-popup` is only one of the many functions of emacs-guix. I was not
>> talking about it.
>
> About which one are you talking? Except “build” that we already
> discussed above.
I've raised mostly 2 issues in this conversation, the ones I've
mentioned on GitLab, sorry if that was unclear :)
- https://gitlab.com/emacs-geiser/geiser/-/issues/9
Geiser chokes on big outputs, so guix-devel-build-package-definition
is not usable.
Proposed solution: Use a non-Geiser comint mode like IELM or M-x
shell.
Or Eshell (not a comint-mode though).
- https://gitlab.com/emacs-geiser/geiser/-/issues/11
This one can seriously hang your Emacs when calling
`geiser-mode-switch-to-repl-and-enter` from a .scm of an
not-fully-built Guix.
I remember hitting this issue with emacs-guix, but I can't remember a
recipe.
So maybe this has nothing to do with emacs-guix after all, but let's
keep it in mind in case it comes up again.
Then I remembered another one:
- https://gitlab.com/emacs-guix/emacs-guix/-/issues/8
It's unclear to me whether this one is due to Geiser or not.
I can still reproduce it today.
> That’s a feature as Ludo and Ricardo said. From my opinion too.
>
> What’s wrong with the sequence:
Nothing wrong!
> Ok, but that the same story as ’build’. Right?
Yes.
>> This is not persistence that's needed for the emacs-guix commands.
>
> Wait, you said « emacs-guix never relies on persistence if I'm not
> mistaken. » which is wrong because everything is sent to *Guix REPL*
> (Geiser) reachable with “M-x guix-switch-to-repl“ as shown above.
It does not _rely_ on it, in the sense that it's not necessary, it could
work very well without it.
>>>> My suggestion indeed lacks persistence, but at least it works for now
>>>> until we figure out something better.
>>>
>>> Now you convinced me that Emacs-Guix needs love. Well the “it works” in
>>> « at least it works for now » is meaningless for me
>>
>> Why? A program that works is meaningful I believe.
>
> Which program are you talking about?
Helm-System-Packages and Nyxt are 2 example programs that can talk to
Guix reliably.
Not saying we should use them instead, of course.
But this technique is worth exploring to make Emacs-Guix more reliable.
> Maybe. It should be addressed action by action. Instead of thrashing
> Geiser. IMHO.
I didn't mean to thrash (or did you mean "trash"?) Geiser, sorry if that
came across this way.
I just wanted to highlight some hard-to-fix (design?) issue with Geiser
that come in the way of Emacs-Guix, so _in the context of Emacs Guix_, I
believe that leveraging other means of communicating with Guix can be a
good idea, at least for some operations like building packages.
> What are the « among other things »?
For instance:
- https://gitlab.com/emacs-guix/emacs-guix/-/merge_requests/8
- Channels support
https://gitlab.com/emacs-guix/emacs-guix/-/issues/17
The above has nothing to do with Geiser of course, as you
said, the fix is love! :)
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2020-11-15 7:54 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
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 [this message]
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=87eekv5a4j.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).