From: Nicolas Graves via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: guix-devel@gnu.org
Subject: Tempel snippets
Date: Sun, 07 Aug 2022 01:53:24 +0200 [thread overview]
Message-ID: <878ro10w0b.fsf@ngraves.fr> (raw)
Hi guix!
I'm translating the snippets used in the snippets dir so that we can
provide an alternative (here tempel) for snippets in the Perfect Setup.
I have two practical questions about where to put that code.
1) For reproducible development purposes (e.g. rde), it would
be great to have snippets shipped with guix itself (the snippets
directory is not in the store of the guix package), or alternatively in
a package, instead of in a possibly moving directory. WDYT? Which
alternative is the best?
2) Where should I add tempel-ready snippets? The etc/snippets dir can't
be used directly because it's the one used by yasnippet. Or in the
option of packages, I can rather make one.
3) I'll send a first series with basic working templates, but in the
process have seen that there may be some refactoring / snippets
improvements, but I'm not yet emacs-fluent enough to get that done
easily. Will probably send a mail with the series with some ideas for
refactoring and where I'm stuck. Also I think that we can add a snippet
for license: completion, include an alternative snippet for copyright
(since we must be at the right spot to insert anyway), and have an
option to compute base32 hash during template completion (if possible,
I'll see what I can do).
--
Best regards,
Nicolas Graves
next reply other threads:[~2022-08-06 23:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 23:53 Nicolas Graves via Development of GNU Guix and the GNU System distribution. [this message]
2022-08-07 7:33 ` Tempel snippets Liliana Marie Prikler
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=878ro10w0b.fsf@ngraves.fr \
--to=guix-devel@gnu.org \
--cc=ngraves@ngraves.fr \
/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).