bug#62511: Acknowledgement ([PATCH] docs: Add example clarifying how syntax-case renames symbols)

Close as dupe

bug#62511: [PATCH] docs: Add example clarifying how syntax-case renames symbols

I encountered these renamed symbols in the wild, and it took quite a while for me to figure out what was going on. I'm glad to have learned a lot about syntax-case in the process, all the way through to Primer for the Mildly Insane, but I think it would spare future learners some trouble to have an

bug#62510: [PATCH] docs: Add example clarifying how syntax-case renames symbols

I encountered these renamed symbols in the wild, and it took quite a while for me to figure out what was going on. I'm glad to have learned a lot about syntax-case in the process, all the way through to Primer for the Mildly Insane, but I think it would spare future learners some trouble to have an

bug#61095: possible misuse of posix_spawn API on non-linux OSes

Hi Ludo, Ludovic Courtès writes: > - posix_spawn_file_actions_addclose (actions, fd); > + /* Adding invalid file descriptors to an 'addclose' action leads > + to 'posix_spawn' failures on some operating systems: > + . Hence the extra check.

bug#61095: possible misuse of posix_spawn API on non-linux OSes

Hi Omar, Apologies for the late reply. Omar Polo skribis: > I've noticed that test-system-cmds fails on OpenBSD-CURRENT while > testing the update to guile 3.0.9: > > test-system-cmds: system* exit status was 127 rather than 42 > FAIL: test-system-cmds We’re seeing the same failure on

bug#62501: [3.0.9] ‘spawn’ test fails on GNU/Hurd, due to $LD_ORIGIN_PATH

On GNU/Hurd, the ‘exec’ server always sets ‘LD_ORIGIN_PATH’ in the environment of programs it executes—see ‘do_exec’ in ‘exec/exec.c’. Consequently, the ‘spawn’ test that checks environment variables fails: --8<---cut here---start->8--- Running posix.test UNRESO