unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 16:59:16 +0100	[thread overview]
Message-ID: <875z68x73f.fsf@ambrevar.xyz> (raw)
In-Reply-To: <867dqoyu34.fsf@tournier.info>

[-- Attachment #1: Type: text/plain, Size: 2063 bytes --]

Hi Simon!

zimoun <zimon.toutoune@gmail.com> writes:

> Is it possible to currently build the packages using Emacs-Guix?
>
> And if you talk about ‘guix-devel-build-package-source‘, it needs before
> to ’run-geiser’, I guess.

Yes, using guix-devel-build-package-source, or even building by writing
Scheme code in the Guix REPL.

>> - https://gitlab.com/emacs-geiser/geiser/-/issues/9
>
> 8 months is bunch of time but not a while. :-)

Actually 9 months, but the issue has been there forever.

The problem is the Schemers are just painfully dealing with the status
quo.  I believe we need to address this.  Geiser is lagging behind by
far, compared to what SLIME, SLY, racket-mode and CIDER can offer.

>> - https://gitlab.com/emacs-geiser/geiser/-/issues/11
>
> 3 weeks is not a while, neither. ;-)

Which 3 weeks?  I think you looked at Maxim's comment :p  The issue was
also opened 9 months ago.

>> I'd like insist: in the current state of Geiser, we cannot leverage it
>> reliably in Emacs-Guix.  We need to talk to Guix directly, e.g. with
>> `guix repl` like I've done in Nyxt.
>
> For all what “guix-popup” does, maybe pipe to “guix repl” should
> simplify.  But I do not see how one could work interactively without
> Geiser; for example piping to “guix repl” can not fix your concern about
> “Traces are not interactive”, fixing Geiser can.

Yes, but my point is that since traces are mostly useless as it is now,
we don't lose any benefit by using `guix repl'.

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.

We can always go back to Geiser at some point in the future when it gets
more reliable.

Cheers!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]

  reply	other threads:[~2020-11-14 15:59 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 [this message]
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
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=875z68x73f.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).