From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Christopher Howard <christopher@librehacker.com>, guix-devel@gnu.org
Cc: Andrew Tropin <andrew@trop.in>,
Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>
Subject: Re: emacs-guix
Date: Tue, 01 Oct 2024 19:18:38 +0200 [thread overview]
Message-ID: <12c9959ae5ef9a6ba18a1d7206a5b5da728411d6.camel@gmail.com> (raw)
In-Reply-To: <877catxbau.fsf@librehacker.com>
Am Montag, dem 30.09.2024 um 10:10 -0800 schrieb Christopher Howard:
> Hi, I was wondering if there is a specific person here who focuses on
> the emacs-guix package — development or maintainence. It seems like
> my bug reports for that don't usually get any responses, so I was
> starting to work on troubleshooting my own bug reports. But was
> wondering if there is somebody who oversees that package, or has
> their own dev branch, or whatever such that it would be important to
> collaborate with them on troubleshooting and patches. I CC'd the e-
> mail address I found for the Emacs Team.
If you wish to update the emacs-guix package (or patching, etc.), then
yeah, CC'ing emacs-team for faster processing is the way to go. That
said, we don't typically know about every emacs package in there, much
less their intrinsics.
Regarding the functionality of emacs-guix, as far as I know, the
derivation mode still works, but the UI etc. has a hard time otherwise.
> I'm not really interesting much in being a guix developer right now,
> but I've gained enough proficiency in Emacs and elisp to at least
> troubleshoot/investigate. The bug I am focusing currently is 73462.
>
> I don't know if the original emacs-guix developer (Alex Kost) is
> still involved and/or wants to be CC'd.
It is a known bug and has been for some time. Sadly, no one's
submitted a fix yet.
Cheers
next prev parent reply other threads:[~2024-10-01 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 18:10 emacs-guix Christopher Howard
2024-10-01 17:18 ` Liliana Marie Prikler [this message]
2024-10-03 13:46 ` emacs-guix Simon Tournier
2024-10-23 16:36 ` emacs-guix Ludovic Courtès
2024-10-23 21:25 ` emacs-guix Christopher Howard
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=12c9959ae5ef9a6ba18a1d7206a5b5da728411d6.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=andrew@trop.in \
--cc=christopher@librehacker.com \
--cc=cox.katherine.e+guix@gmail.com \
--cc=guix-devel@gnu.org \
/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).