From: Arun Isaac <arunisaac@systemreboot.net>
To: guix-devel@gnu.org
Subject: Re: Snippets for working on Guix
Date: Sat, 16 Dec 2017 11:44:45 +0530 [thread overview]
Message-ID: <cu7wp1n2o8a.fsf@systemreboot.net> (raw)
In-Reply-To: <87efnwghs3.fsf@gnu.org>
>> 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.
>>
>> These snippets are available:
>>
>> ./scheme-mode/guix-package
>> ./scheme-mode/guix-origin
>> ./scheme-mode/guix-git-reference
>> ./scheme-mode/guix-hg-reference
>> ./scheme-mode/guix-cvs-reference
>> ./scheme-mode/guix-svn-reference
>> ./text-mode/guix-commit-message-add-package
>> ./text-mode/guix-commit-message-update-package
>
> That looks really useful!
Indeed, this is very useful! :-)
> Do you think we could add them under etc/emacs in the repo, and somehow
> have them automatically available? Or should it be in Emacs-Guix?
It would be nice if this was available automatically through emacs-guix.
Apart from the snippets, it would also be nice to somehow automatically
update a package definition -- that is, change the version number,
download the new source, and update the hash. I was trying to work this
out. I was able to get the Guix REPL to download the new source tarball,
but couldn't figure out how to retrieve the new hash from the Guix
REPL. Any pointers?
next prev parent reply other threads:[~2017-12-16 6:15 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 [this message]
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
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=cu7wp1n2o8a.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.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).