Below is something I played with years ago. I'm not sure kill-opt is up to
date. Try with
> (load "jtd.scm")
> (foo)
[1]> ,loc
;; potluck/jtd - jump to debugger, detour to debugger
;;(define-module (potluck jtd) #:export (kill-opt trap-here foo))
(use-modules (system repl repl))
> Below is something I played with years ago. I'm not sure kill-opt is
> up to date. Try with
>
>
> > (load "jtd.scm")
> > (foo)
> [1]> ,loc
The code seems to evaluate fine, but does not produce useful results:
```
scheme@(guile-user)> ,use (potluck jtd)
scheme@(guile-user)> (foo)
sche
On 10/19/19 12:04 PM, Christopher Howard wrote:
Below is something I played with years ago. I'm not sure kill-opt is
up to date. Try with
> (load "jtd.scm")
> (foo)
[1]> ,loc
The code seems to evaluate fine, but does not produce useful results:
```
scheme@(guile-user)> ,use (po
On Friday, 18 October 2019 17:09, pelzflorian (Florian Pelz)
wrote:
> On Fri, Oct 18, 2019 at 11:29:35AM +, Todor Kondić wrote:
>
> > You know, there is a big IT department within our institution and telling
> > them I will base some serious work on technologies such as GNU Guile and
> > G
On Sun, Oct 20, 2019 at 2:11 AM Todor Kondić wrote:
> But, I doubt any of them would find it natural to take a step further and
> participate in GNU itself (ugh, now I sound like a preacher of a new age
> religion). To my knowledge, interaction within GNU communities is still
> mostly mailing lis
