From: "Ludovic Courtès" <ludo@gnu.org>
To: David Wilson <david@daviwil.com>
Cc: "\(" <paren@disroot.org>,
60753@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#60753] [PATCH] gnu: home: Add home-emacs-service-type.
Date: Mon, 20 Feb 2023 12:10:07 +0100 [thread overview]
Message-ID: <87a618iods.fsf@gnu.org> (raw)
In-Reply-To: <875ycaq7lx.fsf@daviwil.com> (David Wilson's message of "Fri, 10 Feb 2023 09:50:03 +0200")
Hi David,
David Wilson <david@daviwil.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Now let’s see perhaps what we need to get ‘home-emacs-service-type’
>> merged, and what we can keep as future work. Thoughts?
>
> Sorry for the long delay in getting back to this! To summarize what
> we've discussed so far:
>
> - It's possibly best to use g-expressions for the init.el file contents
> because it gives ultimate flexibility on how one can describe their
> Emacs configuration in Scheme while pulling in files from their local
> configuration folder. Are we concerned whether this may be harder for
> users to understand and adopt?
Ease of use should always be a concern IMO. I’d expect that writing
gexps will feel more convenient than in sexps-in-Scheme-strings for the
target Elisp audience.
> - We'll postpone any work to ensure that comments and #'function
> references can be properly represented so that we can get the basic
> `home-emacs-service' merged for now. Future patches will improve on
> that situation.
>
> Is that accurate? Either way, I'll spend some time today responding to
> the feedback so that we can get this merged.
Sounds good to me!
Ludo’.
next prev parent reply other threads:[~2023-02-20 11:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 14:01 [bug#60753] [PATCH] gnu: home: Add home-emacs-service-type David Wilson
2023-01-12 17:24 ` ( via Guix-patches via
2023-01-12 17:27 ` David Wilson
2023-01-14 18:00 ` Ludovic Courtès
2023-01-15 8:02 ` Andrew Tropin
2023-01-17 9:02 ` Ludovic Courtès
2023-01-17 14:46 ` Andrew Tropin
2023-01-23 10:18 ` Ludovic Courtès
2023-01-26 5:06 ` Andrew Tropin
2023-01-31 16:26 ` Ludovic Courtès
2023-02-01 14:06 ` Andrew Tropin
2023-02-10 7:50 ` David Wilson
2023-02-20 11:10 ` Ludovic Courtès [this message]
2023-02-01 12:59 ` Jelle Licht
2023-02-01 13:46 ` Andrew Tropin
2023-01-26 18:50 ` Reily Siegel
2023-01-16 9:25 ` David Wilson
2023-01-15 0:21 ` [bug#60753] file like parameters not working benoit
2023-01-15 2:07 ` [bug#60753] issue with file-like init file benoit
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=87a618iods.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=60753@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=david@daviwil.com \
--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 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).