From: Brett Gilio <brettg@gnu.org>
To: Adam Kandur <rndd@tuta.io>
Cc: 42689@debbugs.gnu.org
Subject: [bug#42689] add sbcl-cl-livesupport
Date: Mon, 03 Aug 2020 23:22:00 -0500 [thread overview]
Message-ID: <87a6zbavmf.fsf@gnu.org> (raw)
In-Reply-To: <MDnD_6x--3-2@tuta.io> (Adam Kandur's message of "Mon, 3 Aug 2020 09:30:11 +0200 (CEST)")
Adam Kandur <rndd@tuta.io> writes:
> (define-public sbcl-cl-livesupport
> (let ((commit "71e6e412df9f3759ad8378fabb203913d82e228a")
> (revision "1"))
> (package
> (name "sbcl-livesupport")
> (version (git-version "0.0.0" revision commit))
> (source
> (origin
> (method git-fetch)
> (uri (git-reference
> (url "https://github.com/cbaggers/livesupport")
> (commit commit)))
> (file-name (git-file-name name version))
> (sha256
> (base32 "1rvnl0mncylbx63608pz5llss7y92j7z3ydambk9mcnjg2mjaapg"))))
> (build-system asdf-build-system/sbcl)
> (home-page "https://github.com/cbaggers/livesupport")
> (synopsis "Some helpers that make livecoding at little easier")
> (description "A macro commonly used in livecoding to enable
> continuing when errors are raised. Simply wrap around a chunk of code
> and it provides a restart called 'continue' which ignores the error
> and carrys on from the end of the body. I usually wrap this around the
> code 'step' function in my main loop.")
> (license license:bsd-2))))
Hi again, Adam!
Same situation here, as per my last email :).
next prev parent reply other threads:[~2020-08-04 4:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 7:30 [bug#42689] add sbcl-cl-livesupport Adam Kandur via Guix-patches via
2020-08-04 4:22 ` Brett Gilio [this message]
[not found] ` <MDtvt6v--3-2@tuta.io>
2020-08-04 17:28 ` Brett Gilio
[not found] ` <MDucLhm--3-2@tuta.io>
2020-08-04 18:09 ` Brett Gilio
2020-08-04 18:54 ` [bug#42689] another try Adam Kandur via Guix-patches via
2020-08-05 1:38 ` Brett Gilio
2020-08-05 5:28 ` Alexandru-Sergiu Marton
2020-08-05 7:17 ` [bug#42689] [PATCH] gnu: Add sbcl-livesupport Adam Kandur via Guix-patches via
2020-08-11 20:23 ` Adam Kandur via Guix-patches via
2020-08-12 6:55 ` Adam Kandur via Guix-patches via
2020-08-22 18:23 ` Leo Famulari
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=87a6zbavmf.fsf@gnu.org \
--to=brettg@gnu.org \
--cc=42689@debbugs.gnu.org \
--cc=rndd@tuta.io \
/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).