From: Sergiu Ivanov <sivanov@colimite.fr>
To: Joshua Branson <jbranso@dismail.de>
Cc: Help-Guix <help-guix@gnu.org>
Subject: Re: Emacs Guix and channels
Date: Fri, 22 Jan 2021 10:29:26 +0100 [thread overview]
Message-ID: <87h7n9fhft.fsf@colimite.fr> (raw)
In-Reply-To: <87tura11qh.fsf@dismail.de>
Thus quoth Joshua Branson on Thu Jan 21 2021 at 21:20 (+0100):
> Sergiu Ivanov <sivanov@colimite.fr> writes:
>
>> Hi John,
>> Tell me how I can help.
>>
>> I picked up Guix a couple of weeks ago and my Elisp programming
>> experience is quite limited, but I may still be useful :-)
>>
>
> I think emacs-guix has been broken for a while. There is a new effort
> to fix it.
Ah, that's good news. My impression from hanging around the Guix
ecosystem for a little while is that Emacs integration is a popular
selling point, so it would be nice to have it working :-)
> The new home for emacs-guix is at savannah.
>
> http://git.savannah.gnu.org/cgit/guix/emacs-guix.git
>
> #+BEGIN_SRC sh
> git clone https://git.savannah.gnu.org/git/guix/emacs-guix.git
> #+END_SRC
Thanks a lot, I wasn't aware of this recent migration! I'll check later
today which version of Emacs-Guix I am using.
I will not be available for contributions immediately, but I should be
good to go in a couple of weeks, and Emacs-Guix seems like a nice first
target. (Unless John and the other contributors fix all the issues in
the meantime :D)
> Other relevant links:
>
> http://savannah.gnu.org/projects/guix
>
> https://lists.gnu.org/archive/html/guix-devel/2021-01/msg00170.html
Thank you for all these links! Very helpful.
-
Sergiu
next prev parent reply other threads:[~2021-01-22 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 19:32 Emacs Guix and channels Sergiu Ivanov
2021-01-21 16:12 ` John Soo
2021-01-21 17:34 ` Sergiu Ivanov
2021-01-21 20:20 ` jbranso--- via
2021-01-22 9:29 ` Sergiu Ivanov [this message]
2021-01-25 12:47 ` zimoun
2021-01-25 20:59 ` Sergiu Ivanov
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=87h7n9fhft.fsf@colimite.fr \
--to=sivanov@colimite.fr \
--cc=help-guix@gnu.org \
--cc=jbranso@dismail.de \
/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.
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).