From: jgart <jgart@dismail.de>
To: jbranso@dismail.de
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: How can I step through this code?
Date: Mon, 10 Oct 2022 17:40:36 -0500 [thread overview]
Message-ID: <20221010174036.GB32209@dismail.de> (raw)
In-Reply-To: <345658a93e588f806851c59dd51ffae4@dismail.de>
On Mon, 10 Oct 2022 19:49:23 +0000 jbranso@dismail.de wrote:
> October 9, 2022 12:30 PM, "jgart" <jgart@dismail.de> wrote:
>
> > On Sun, 09 Oct 2022 00:14:23 +0000 jbranso@dismail.de wrote:
> >
> >> A debugger stepping through the code would have been awesome!
> >
> > Yup it would have! You're right!
> >
> >> Right now I am super in love with Guix.
> >
> > Me too, it's more like a passionate love hate relationship for me tbh. I
> > need couples GNUtherapy.
> >
> >> My main squeeze is working
> >> on our existing opensmtpd-service and letting users configure it with
> >> proper scheme records. I don't know if I want to play with common lisp.
> >
> > Ya, it's a rabbit hole although I recommend atleast once, taking a stack
> > stroll in the caddy just so you know what's up ;()
>
> ahaha. I guess there is an OS written in common lisp...
ya anything rust can do CL could do better jk (not jk)
next prev parent reply other threads:[~2022-10-10 22:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 3:05 How can I step through this code? jgart
2022-10-07 18:45 ` jbranso
2022-10-07 19:22 ` jgart
2022-10-07 21:52 ` jbranso
2022-10-08 1:25 ` jgart
2022-10-08 15:03 ` jbranso
2022-10-08 17:23 ` jgart
2022-10-09 0:14 ` jbranso
2022-10-09 16:30 ` jgart
2022-10-10 19:49 ` jbranso
2022-10-10 22:40 ` jgart [this message]
2022-10-10 16:04 ` Ludovic Courtès
2022-10-10 17:00 ` jgart
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=20221010174036.GB32209@dismail.de \
--to=jgart@dismail.de \
--cc=help-guix@gnu.org \
--cc=jbranso@dismail.de \
/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.
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).