IRC channel logs

<euouae>old: but why don't we need to sign the FSF papers anymore?

<euouae>Adding yourself to the copyright line is not FSF policy -- it means the contributions are owned by multiple people, complicating legal defense of violations; which is why copyright is transferred to FSF with that $1 contract

<apteryx>because the guile maintainers decided against it

<euouae>ah ok, then HACKING needs to be modified

<euouae>it has stale instructions since it's still talking about the necessity of the copyright transfer

<apteryx>euouae: mentioned in 2022 https://lists.gnu.org/archive/html/guile-devel/2022-10/msg00016.html

<euouae>thanks, I will try to update HACKING with that

<apteryx>looks like there was some suggestion to request some form of copyright waiver from contributors' employers to make it easier/possible to defend in case of litigation in https://lists.gnu.org/archive/html/guile-devel/2022-10/msg00079.html

<apteryx>perhaps worth revisiting

<apteryx>or perhaps we could adopt some the same kind of Signed-off-by policy as the linux kernel which comes with this kind of legal declaration "I certify this is my work and I own the copyright on it"

<apteryx>then if there are issues the issues are between the individual and their employer rather than the rproject and the individual's employer, IIUC.

<euouae>I made the PR already <https://codeberg.org/guile/guile/pulls/254> you can add that detail there if you'd like, I'm not sure how relevant it is

<euouae>Signed-off-by is additional policy and I don't know if Guile follows it

<old>The signed-off-by policy will be part of the coding assistant policy

<old>The DCO is what apteryx is mentionning wrt to linux kernel copyright and signed-off

<old>which is why I wanted to add it in the first place

<old>Currently working on making the compiler outputs prettier. Feedbacks welcome! https://codeberg.org/guile/guile/issues/255

<euouae>looks nice

<apteryx>old: that sounds good

<euouae>If you add the DCO and want Signed-off-by trailers then it would be nice to be mentioned in HACKING as mandatory contributor policy.

<apteryx>what's the variable name that the Guile REPL sets to the last returned value? e.g. in Python it's _ IIRC

<apteryx>err, python has no such thing (probably confused with perl), but IPython has an Out dictionary, so you can use the not-too-pretty list(Out)[-1]

<apteryx>ah, no, underscore (_) works in Python. So does Guile has an equivalent?

<apteryx>I can hack my way via the history obarray, but maybe we should expose $0 or $_ as the last returned value

<apteryx>new feature https://paste.guixotic.coop/magit-diff_guile.html

<apteryx>some typos, but after fixing: https://paste.guixotic.coop/_scratch_-669-841.html

<apteryx>trivial PR: https://codeberg.org/guile/guile/pulls/256/files

<euouae>I thought that was a thing already! maybe not

<euouae>apteryx: does it work correctly with `clear-value-history!`?

<apteryx>just found there's already a new feature in that maps the last value to $*, added by old

<euouae>nice

<apteryx>it does, the history variables are all cleared by that, including $0

<euouae>OK just wanted to bring that to your attention

<euouae>got to go

<rogerfarrell>Hi #guile, Is there a de facto standard for setting up geiser-guile in Guix for Guile projects? Link? I have been setting ~geiser-guile-binary~ to ~guix shell -CPm manifest.scm~.

<rogerfarrell>The manifest contains guile, guile modules, geiser, geiser-guile.

IRC channel logs

2026-08-20.log