From: Chris Marusich <cmmarusich@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Snippets for working on Guix
Date: Sat, 16 Dec 2017 01:03:45 -0800 [thread overview]
Message-ID: <87r2rvhwni.fsf@gmail.com> (raw)
In-Reply-To: <87mv2jnj4y.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 16 Dec 2017 09:59:09 +0100")
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Chris Marusich <cmmarusich@gmail.com> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> to avoid the need to type out boilerplate I wrote a couple of snippets
>>> that can be used with yasnippet in Emacs, and I thought I should share
>>> them with you.
>>
>> Thank you very much!
>>
>>> I hope this is useful for some of you!
>>
>> I am very interested in trying this out. However, as someone who has
>> never used yasnippet, I think it would be extremely helpful if you could
>> provide a simple example of what to do in the manual somewhere under the
>> "Contributing" section. And that way, it's more likely people will
>> discover and use these snippets.
>
> It’s already there, but due to a bug, the manual won’t be rebuilt when
> “contributing.texi” has changed. As a work-around just touch
> “doc/guix.texi” and then run “make info”.
Oh, awesome! I will check it out.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-12-16 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 23:48 Snippets for working on Guix Ricardo Wurmus
2017-12-15 14:58 ` Ludovic Courtès
2017-12-15 16:20 ` Ricardo Wurmus
2017-12-16 6:14 ` Arun Isaac
2017-12-16 10:21 ` Ricardo Wurmus
2017-12-16 15:58 ` Arun Isaac
2017-12-16 3:17 ` Maxim Cournoyer
2017-12-16 8:15 ` Chris Marusich
2017-12-16 8:59 ` Ricardo Wurmus
2017-12-16 9:03 ` Chris Marusich [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
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=87r2rvhwni.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).