From 35a413167e323f8b0c9ea40fe7599ffb50e9e321 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Hugo=20H=C3=B6rnquist?= Date: Tue, 31 Mar 2020 16:46:02 +0200 Subject: Attempt at decentralized configuration system. Placing all possible configuration items in a central (parameters) module scales really badly. This idea that any module can register configuration parameters is better. The current implementation however has the drawback that it requires that the module exposing the parameter is loaded before the value can be sat, but that scales even worse. A probable solution would be to abandon binding everything to guile's module system, and instead let (util config) provide a `conf-ref' and a `conf-set!' procedures. A `define-configuration' similar to emacs `defcustom' could be of use, mainly for retroactively type checking parameters. --- module/entry-points/ical.scm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'module/entry-points/ical.scm') diff --git a/module/entry-points/ical.scm b/module/entry-points/ical.scm index 9f7457c3..e2ee7dcf 100644 --- a/module/entry-points/ical.scm +++ b/module/entry-points/ical.scm @@ -3,7 +3,7 @@ :use-module (util) :use-module (output ical) :use-module ((vcomponent) :select (load-calendars*)) - :use-module ((parameters) :select (calendar-files)) + :use-module ((util config all) :select (calendar-files)) :use-module (ice-9 getopt-long) :use-module (datetime) :use-module (datetime util) -- cgit v1.2.3