Neat I guess, but doing it all manually seems to be the only option? Feels like a chore just looking at it.
How about wrapping each PS1 (?) in the "mq" command and automatically look for stuff?
Or even just running some "mq auto" after each command that looks at the previous command - and if it hits certain things like "git commit" or whatever it would automatically complete that quest or however it works.
Comments
Neat I guess, but doing it all manually seems to be the only option? Feels like a chore just looking at it.
How about wrapping each PS1 (?) in the "mq" command and automatically look for stuff?
Or even just running some "mq auto" after each command that looks at the previous command - and if it hits certain things like "git commit" or whatever it would automatically complete that quest or however it works.
see an example here: https://github.com/trqx/microquest/tree/master/contrib/bash-...
it is not pretty, and slows down the prompt but it shows it's doable with a wrapper.
well first, thank you for your suggestions :)
The idea is that microquest could be used for anything, even outside the shell, so I'll keep mq as simple as possible.
Users can contribute wrappers, quests, files, scripts, but I don't think I will change microquest much besides what is in the todo list.
Turning the module into a library (all print() functions will be delegated to the mq.py cli) is also on my todo list.