IRC channel logs

2023-10-21.log

back to list of logs

<daviid>asd
<daviid>sorry :)
<daviid>sneek: later tell tohoyn i am not going to change the upstream naming convention, but you may do so in the 'debian' g-golf configure.ac file
<sneek>Will do.
<daviid>sneek: later tell tohoyn i actually just recently changed the naming convention precisely to adopt the '-alpha-x', '-beta-y' and '-rc-z' naming convention, fwiw
<sneek>Got it.
<sneek>tohoyn: Greetings!
<tohoyn>lloda:ping
<sneek>Welcome back tohoyn, you have 2 messages!
<sneek>tohoyn, daviid says: i am not going to change the upstream naming convention, but you may do so in the 'debian' g-golf configure.ac file
<sneek>tohoyn, daviid says: i actually just recently changed the naming convention precisely to adopt the '-alpha-x', '-beta-y' and '-rc-z' naming convention, fwiw
<tohoyn>lloda: ping
<graywolf>Hello, how can I start a guile program without dropping into the repl? I want to use the -e flag, but I have no -s and it seem I end up in the repl. I cannot provide -s because there is no script to use. Currently I am using guile -e '(@ (foo) main)' -s /dev/null however that does autocompile /dev/null.go. What is the combination of flags I should actually use here?
<tohoyn>graywolf: what about guile -c XXX
<graywolf>How would that look?
<graywolf>Ooooh
<graywolf>guile -c '((@ (foo) main) command-line)'
<graywolf>Yeah I did not realize I just can do what -e does manually
<graywolf>I definitely should wait until coffee kicks in next time
<graywolf>thx
<graywolf>I probably do not understand how to use (backtrace). What am I doing wrong: https://paste.debian.net/plain/1295767 ?
<RhodiumToad>graywolf: you're probably not doing anything wrong, that looks like a known bug