From: David Wilson <david@daviwil.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "\(" <paren@disroot.org>, 60753@debbugs.gnu.org
Subject: [bug#60753] [PATCH] gnu: home: Add home-emacs-service-type.
Date: Mon, 16 Jan 2023 11:25:29 +0200 [thread overview]
Message-ID: <87h6wqu6ss.fsf@daviwil.com> (raw)
In-Reply-To: <87k01p8086.fsf_-_@gnu.org>
Thanks for the feedback, Ludo!
I'll make the requested changes and send them later today. I may also
try adding some tests to ensure that the output is what we expect.
There seems to be a `tests/services` folder, should I add a
`tests/home-services` folder to match?
Ludovic Courtès <ludo@gnu.org> writes:
> It would be nice if you could start the section with a few sentences
> explaining the rationale and what’s being described here.
Will do, I'll look at other services to get an idea of the best way to
do this.
> What about accepting sexps (or gexps) instead of strings? As in:
>
> (init-file '((require 'whatever) (setq something t)))
>
> Also I find it confusing that it’s either text or files. In the code it
> has type ‘text-config’, which means list of file-like objects IIUC, no?
Yes, this was a misunderstanding on my part!
Regarding using s-expressions for this, it would certainly look cleaner.
Andrew raises a good concern about it in his response, I'll take a look
at what RDE does for this and see if I can adopt a similar approach.
> Nitpick: I think this should be ‘load-path’ (singular), because it’s one
> search path (i.e., a list of directories).
>
> And: s/Additional load paths/Additional directories/
Will change both of these, thanks!
> Would be nice to have a couple of commented examples here, like you had
> in the first message in this thread. :-)
Yep, I'll add examples for all the use cases here.
> Would be nice to have a sentence above, like “This service type can be
> extended with @code{home-emacs-extension} records, described below:”.
Will describe and give an example of how to extend the service!
David
next prev parent reply other threads:[~2023-01-16 10:13 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
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 [this message]
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=87h6wqu6ss.fsf@daviwil.com \
--to=david@daviwil.com \
--cc=60753@debbugs.gnu.org \
--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 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).