It seems a bit misleading to call the autogenerated file to which lem saves its serialized settings config.lisp.
When I see a config file, in my ~/.config folder I assume that I am meant to edit it to configure my application, but no, in order to edit lem's config you need to create a ~/.config/init.lisp file to put your actual lisp configuration code into.
Additionally, the contents of config.lisp is not lisp source code, it is unevaluated S-Expressions. So perhaps some better names would be:
saved-settings.sexprsettings.sexprsaved-variables.sexpr
At the very least, adding a comment to the top of the config.lisp file that states that the file is not for putting evaluated lisp code, and that code should instead be put into an init.lisp file would be helpful.
It seems a bit misleading to call the autogenerated file to which lem saves its serialized settings
config.lisp.When I see a config file, in my
~/.configfolder I assume that I am meant to edit it to configure my application, but no, in order to edit lem's config you need to create a~/.config/init.lispfile to put your actual lisp configuration code into.Additionally, the contents of
config.lispis not lisp source code, it is unevaluated S-Expressions. So perhaps some better names would be:saved-settings.sexprsettings.sexprsaved-variables.sexprAt the very least, adding a comment to the top of the
config.lispfile that states that the file is not for putting evaluated lisp code, and that code should instead be put into aninit.lispfile would be helpful.