bug#63366: Docs: Revise or delete reference to “benevolent dictators” in Manual Introduction

Hi, Sebastian Carlos skribis: > My suggestion is to delete the sentence altogether. I think the paragraph > still makes sense without it, as the reader gets enough information to > understand how Scheme differs from other programming languages. I’ve (finally) removed that sentence. Thanks! Lu

bug#68507: [PATCH] doc: Fix example in list-transduce example.

Hi, Tomas Volf <~@wolfsden.cz> skribis: > While the `.' might be correct from a grammatical point of view (I do > not know), it turns the example into invalid scheme code, which is not > ideal. New users (like me) might try to copy the whole line and wonder > why it does not work (like I did).

bug#68505: [PATCH v2] Add more detailed instructions into the HACKING file.

Hi, Tomas Volf <~@wolfsden.cz> skribis: > Until now, the ./meta/guile was not mentioned anywhere, and therefore it > was not obvious how to run the locally compiled Guile without installing > it. > > While modifying the file, I took the liberty to also mention a bit about > compiling Guile using

bug#68504: [PATCH] Add copy-on-write support to scm_copy_file.

Hi, Tomas Volf <~@wolfsden.cz> skribis: > On modern file-systems (BTRFS, ZFS) it is possible to copy a file using > copy-on-write method. For large files it has the advantage of being > much faster and saving disk space (since identical extents are not > duplicated). This feature is stable and

bug#68087: Signal handlers not called after ‘primitive-fork’

Ludovic Courtès skribis: > Fixes . > > * libguile/scmsigs.h (scm_i_signals_pre_fork, scm_i_signals_post_fork): > New declarations. > (scm_i_signal_delivery_thread): Change type to SCM.. > * libguile/threads.c (scm_all_threads): Adjust accordingly and exclude > threads

bug#68505: [PATCH v3] Add more detailed instructions into the HACKING file.

Until now, the ./meta/guile was not mentioned anywhere, and therefore it was not obvious how to run the locally compiled Guile without installing it. While modifying the file, I took the liberty to also mention a bit about compiling Guile using Guix. Finally, the header lines where cleaned up, en

bug#68505: [PATCH v2] Add more detailed instructions into the HACKING file.

Thank you for the review. On 2024-01-24 11:18:27 +0100, Ludovic Courtès wrote: > > +You can spawn a shell with all the required dependencies using GNU Guix > > +by running the following command: > > + > > +guix shell -D -f guix.scm --pure > > I would suggest running: > > guix shell -CP > > (

bug#68504: [PATCH v2] Add copy-on-write support to scm_copy_file.

On modern file-systems (BTRFS, ZFS) it is possible to copy a file using copy-on-write method. For large files it has the advantage of being much faster and saving disk space (since identical extents are not duplicated). This feature is stable and for example coreutils' `cp' does use it automatica

bug#68504: [PATCH v3] Add copy-on-write support to scm_copy_file.

On modern file-systems (BTRFS, ZFS) it is possible to copy a file using copy-on-write method. For large files it has the advantage of being much faster and saving disk space (since identical extents are not duplicated). This feature is stable and for example coreutils' `cp' does use it automatica

bug#68504: [PATCH] Add copy-on-write support to scm_copy_file.

On 2024-01-24 11:26:56 +0100, Ludovic Courtès wrote: > > The patch looks great (and very useful) to me, modulo one issue: > > > -SCM_API SCM scm_copy_file (SCM oldfile, SCM newfile); > > +SCM_API SCM scm_copy_file (SCM oldfile, SCM newfile, SCM rest); > > Since this is a public interface, we cannot

bug#68703: update to lightning.texi to work w/ texi2any --pdf (with patch)

The following changes to libguile/lightening/lightning.texi will allow it to be used with texi2any --pdf: --- lightning.texi    2022-06-20 07:44:21.159880656 -0700 +++ lightning.texi-fixed    2024-01-24 12:07:27.621547717 -0800 @@ -83,22 +83,12 @@  @ifnottex  @node Top  @top @lightning{} - -@ift