@Ludovic: I recall you mentioned something about warning ports or inhibition of welcome messages. Not sure if it was also about auto-compilation warnings. Would you mind to take at look of the following with me?
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. > all the usual chatter > > ;;; note: source file foo.scm > ;;; newer than compiled CCACHE/3.0-LE-8-4.7foo.scm.go > ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0 > ;;; or pass the --no-auto-compile argument to disable. > ;;; compiling foo.scm > ;;; compiled CCACHE/3.0-LE-8-4.7foo.scm.go I think it is a nice addition to have indeed. > disappears. I would have used a command-line switch, but this was hard > enough, and -q is already taken. 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 The optional part is important to keep backward compatibility. [...] Thanks, Olivier -- Olivier Dion
