On Wed, 25 Mar 2026 15:15:57 -0400 Olivier Dion <[email protected]> wrote:
> On Sat, 21 Mar 2026, "James K. Lowden" <[email protected]> > wrote: > > libguile and module/ice-9: Introduce %quiet-auto-compile > > > > This patch uses a new value for GUILE_AUTO_COMPILE to suppress > > compilation announcements. By setting > > > > GUILE_AUTO_COMPILE=quiet > > How does that work wrt to other values? e.g., it's not possible to > combine `fresh' and `quiet' that way. > > What about allowing bundle of options instead? > > GUILE_AUTO_COMPILE=fresh:quiet > GUILE_AUTO_COMPILE=0:quiet:1 # Same as: GUILE_AUTO_COMPILE=quiet:1 > > that way we keep backward compatibility and we can add new behaviors > in the future. I would have preferred to add a command-line option. Coming from GCC, where nothing in the environment affects the compiler, I would have added --quiet or similar. I submitted this patch as-is because it's one way to skin the cat, and has the merits of being a way I could figure out. > The `--auto-compile' option could probably start taking an optional > argument. > > `--auto-compile[=SPEC] compile source files automatically given SPEC > (default: 1) > > Example: > > guile --auto-compile=fresh:quiet Agreed that --auto-compile and GUILE_AUTO_COMPILE should have the same "grammar". But I would say the Unix idiom (ps(1), for instance) is a comma-delimited list: guile --auto-compile=fresh,quiet Half in jest, the Scheme idiom obviously would be guile --auto-compile='(fresh quiet)' but perhaps that's too clever by half. --jkl
