Installation has become easier because of the wheel, but Macleod still doesn't, "Just Work" immediately after install. This could be simplified by setting some safe cross-platform defaults in the configuration and then adopting a setup where a user-supplied config file overrides the default behaviour if needed.
Change how Macleod searches for and uses the provers
Search for the application name on the PATH environment variable
If the name is found then assume it is active by default
Default some values, using minimal system resources, for each application
Change how Macleod resolves imports relative to other files
Standard search paths
Documented standard search order people can reference (e.g. cmake) and build their workflow around
Begin search for imports relative to current file or current working directory
Continually search folders higher in filesystem until some stopping point (e.g. marker file, max_limit, etc)
Configuration values accept HINTS of directories to search first prior to the tiered search upwards
Configuration accepts additional URIs for import parsing
Allow users to manually override each setting via their own config file given by some file following some standard location (maybe ~/.macleod, %APPDATA%, XDG standard, etc)
Both CLI entrypoints and the GUI should accept a config file as an optional argument and/or support overriding individual parameters via the command line.
Installation has become easier because of the wheel, but Macleod still doesn't, "Just Work" immediately after install. This could be simplified by setting some safe cross-platform defaults in the configuration and then adopting a setup where a user-supplied config file overrides the default behaviour if needed.
PATHenvironment variable~/.macleod,%APPDATA%, XDG standard, etc)