Hey there i did couple of modification !

• Added a build.rs file to generate man page of your program using clap_mangen
• Updated your main cause you seems not really liked it
• Refactor the preview function to use format!
• Couple of bugfix if chosen runner is empty
• Added an option to choose a specific config file to load

Add runners that have arguments which are defined at 'choose time' and saved to the cache.

I want to set this up as a templating type thing, probably with {{myvar}} and then a dictionary of variables stored in the toml. We can parse what variables are required at choose time, when a runner is chosen, so this does not incur a significant performance overhead

Hey there i did couple of modification !

• Added a build.rs file to generate man page of your program using clap_mangen
• Updated your main
• Couple of bugfix if chosen runner is empty
• Added an option to choose a specific config file to load

we need this otherwise if the wrong runner gets set, or it just needs changing, we would have to delete the whole cache file which sucks obviously.

Probably overkill to use crate clap right now, but might be worth doing it anyway, for extendability in the future

runfast must remember the last used runner in a particular directory. the previous way of doing this was to put a .quickrun with the name of the runner in it. this is not ideal, as it causes problems for version control tools such as git.

my current plan is to write a file in ~/.config/runfast/cache which contains directories and corresponding commands. The simplest way to do this is just by having a file like this:

.../proj/foo = cargo build; read
.../proj/bar = python main.py

another solution which may be faster with lots of results would be to have a binary dump of a hashmap, with keys as strings for directories, and a struct as its value.

Loading runners from config files makes this usable without touching the internal code theoretically, as this would obviously require recompilation which is not ideal.

Current way i want this to work is by using .toml files to hold information about runners (name, command, whether they accept additional arguments, should they exit instantly after the runner command finishes etc.). We would then load from /etc/runfast.toml and then ~/.config/runfast/runners.toml , overwriting any name clashes, preferring the user-level one.

Example config entries:

[rust run]
cmd = "cargo"
args = [ "run" ]
exit_fast = false

[python]
cmd = "python"
args = [ "main.py" ]

we want to be able to eject unused / stale from the cache upon hitting a user defined limit. This requires timestamping last use of a runner. the point of this is to be able to know the oldest runner in the cache to be able to eject it on making a new runner which puts the total amount over the limit.