From: Andrew Tropin <andrew@trop.in>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "\(" <paren@disroot.org>, David Wilson <david@daviwil.com>,
60753@debbugs.gnu.org
Subject: [bug#60753] [PATCH] gnu: home: Add home-emacs-service-type.
Date: Tue, 17 Jan 2023 18:46:32 +0400 [thread overview]
Message-ID: <87wn5l8bhz.fsf@trop.in> (raw)
In-Reply-To: <87mt6hjzyx.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
On 2023-01-17 10:02, Ludovic Courtès wrote:
> Hi,
>
> Andrew Tropin <andrew@trop.in> skribis:
>
>>> What about accepting sexps (or gexps) instead of strings? As in:
>>>
>>> (init-file '((require 'whatever) (setq something t)))
>>
>> A quick minor note on this approach: it won't be possible to use
>> #'elisp-function inside such configuration because it will be
>> interpreted by guile reader, but actually rde lives without this
>> functionality completely ok.
>
> Specifically:
>
> (write '#'x)
> |= (syntax x)
>
> But we can use (guix read-print) and ensure that it prints #'.
>
Do you have any links to docs/sample implementations on the topic of
extending guile reader, so we have an example to start with? Does guix
workflow language do something like that?
I think it will be cool to hook up a custom reader, ideally comment
preserving, for emacs lisp inside scheme files.
>> Do we want something like this possible?
>>
>> (init-file `((require 'whatever)
>> (setq something t)
>> (load ,(local-file "old-init.el")))
>
> It’d be nice. In that case, we’ll want it to be a gexp though:
>
> #~((require 'whatever) (load #$(local-file …)))
>
gexps are nice, but do we really need/want them here? Do you have any
thoughts on what are the benifits over quasiquotes in this case? Maybe
some examples?
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2023-01-17 14:47 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn5l8bhz.fsf@trop.in \
--to=andrew@trop.in \
--cc=60753@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.