all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: David Wilson <david@daviwil.com>, 62549@debbugs.gnu.org
Subject: [bug#62549] [PATCH] gnu: home: Add home-emacs-service-type.
Date: Sun, 02 Apr 2023 12:42:38 +0100	[thread overview]
Message-ID: <CRM8RDYP4YWO.2P7XHIHG8TTJ1@guix-framework> (raw)
In-Reply-To: <87a5zrfsms.fsf@gnu.org>

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

Hi Ludo,

On Sat Apr 1, 2023 at 5:56 PM BST, Ludovic Courtès wrote:
> Could you check out David Wilson’s proposal?
>
>   https://issues.guix.gnu.org/60753

I've looked at that before, yeah.

> There were good ideas and interesting discussions there; it would be
> nice to take the best of each proposal.  We desperately need this
> service!  :-)

Here's my take:

- That proposal doesn't seem to include a Shepherd service, so we could definitely
  take that from mine.
- I like David's version's LOAD-PATH field; I'd include that, too.
- I don't think we should try to generate Emacs Lisp code from Scheme s-expressions;
  personally I find that unclean since there isn't a one-to-one correspondence.
- I'm actually not really sure whether it's worth doing the whole thing with the
  Emacs package profile.  It's definitely neat, but would it be better to simply
  add the (transformed) packages to the HOME-PROFILE-SERVICE-TYPE extension?

    -- (

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

      reply	other threads:[~2023-04-02 11:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 19:00 [bug#62549] [PATCH] gnu: home: Add home-emacs-service-type ( via Guix-patches via
2023-04-01 16:56 ` Ludovic Courtès
2023-04-02 11:42   ` ( via Guix-patches via [this message]

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=CRM8RDYP4YWO.2P7XHIHG8TTJ1@guix-framework \
    --to=guix-patches@gnu.org \
    --cc=62549@debbugs.gnu.org \
    --cc=david@daviwil.com \
    --cc=ludo@gnu.org \
    --cc=paren@disroot.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.