Inavlid arithmetic

[Pipboyguy]

❯ shellm -v "Debug the script behavior."
jq: error (at <stdin>:1): null (null) has no keys
/usr/local/bin/shellm: line 78: TOOLS["$(echo "$tool" | jq -r '.key')"]: bad array subscript
/usr/local/bin/shellm: line 44: [[: Debug the script behavior.: syntax error: invalid arithmetic operator (error token is ".")
/usr/local/bin/shellm: line 45: [[: Debug the script behavior.: syntax error: invalid arithmetic operator (error token is ".")
/usr/local/bin/shellm: line 46: [[: Debug the script behavior.: syntax error: invalid arithmetic operator (error token is ".")
/usr/local/bin/shellm: line 47: [[: Debug the script behavior.: syntax error: invalid arithmetic operator (error token is ".")
/usr/local/bin/shellm: line 44: [[: Debug the script behavior.: syntax error: invalid arithmetic operator (error token is ".")

[Biont]

Hi! The script expects a numeric log level, like -v 3

I probably need to improve the error handling and docs on this

[Pipboyguy]

ahh! Thanks @Biont

[Pipboyguy]

❯ shellm -v 3 "Debug the script behavior."
jq: error (at <stdin>:1): null (null) has no keys
/usr/local/bin/shellm: line 78: TOOLS["$(echo "$tool" | jq -r '.key')"]: bad array subscript

It works now! but still getting the warning

[Biont]

I'll check it out asap. Thanks for your patience. I'm still experimenting a lot here

[Biont]

@Pipboyguy Currently, the README fails to mention that the script now expects the config file to be present. When I created the readme, the config file was only used for customization/overrides, but I have since moved many of the prompts in there to save space.

So it errors if the config is not there. To fix it, you can just download the config YAML and place it in one of the recognized paths

I will try to make the following changes as soon as I find the time:

1. Update the README
2. Bail if no config is found on startup
3. If no file is found, ask if it shall be downloaded from GH (<- this might be a bonus I'm skipping)