From: Andrew Tropin <andrew@trop.in>
To: "Christopher Howard" <christopher@librehacker.com>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org,
Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: Re: emacs-guix
Date: Fri, 25 Oct 2024 19:59:13 +0400 [thread overview]
Message-ID: <87seskb2cu.fsf@trop.in> (raw)
In-Reply-To: <87iktiv7e2.fsf@librehacker.com>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
On 2024-10-23 13:25, Christopher Howard wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> For now, you can send patches to guix-patches@gnu.org with “Emacs-Guix”
>> in the subject and I and other committers would be happy to apply them.
>>
>
> Thank you. I have now cloned the repository. My spare time is very limited in this stage of my life, but I am hoping over the winter that I will be able to work on learning the code and patching a few bugs. (It is winter now in Alaska.) Lately I have been busy trying to finish my EmacsConf talks.
>
> Could somebody explain the best approach to running/testing modified
> emacs-guix source from a Guix system? I see emacs-guix is loaded from
> the site-start.el file in the profile, and then this loads
> guix-emacs-autoload-packages, which is critical for running Emacs on a
> Guix system. So, it is not obvious to me the most sensible approach
> for iterative building and testing.
You can basically re-eval the whole .el file or just a part of it with
M-x eval-buffer/defun/whatever and check the updated behavior.
Be aware that guix-emacs is not emacs-guix. It's unrelated
guix-specific machinery. emacs-guix should work completely fine without
it and all usual emacs development approaches will apply for it.
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2024-10-25 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 18:10 emacs-guix Christopher Howard
2024-10-01 17:18 ` emacs-guix Liliana Marie Prikler
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
2024-10-25 15:59 ` Andrew Tropin [this message]
2024-10-25 17:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87seskb2cu.fsf@trop.in \
--to=andrew@trop.in \
--cc=christopher@librehacker.com \
--cc=cox.katherine.e+guix@gmail.com \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.