asdf
asdf copied to clipboard
asdf-vm
Add verbose flag to commands that execute plugin callbacks
Is your feature request related to a problem? Please describe.
Sometimes hard to known what a plugin is doing. Sometimes the list-all or install command hangs and it isn't possible to see what is going on.
Describe the solution you'd like
Add a verbose mode to commands that execute plugin callbacks, list-all, install, etc...
Describe similar asdf features and why they are not sufficient Plugins sometimes log messages to STDOUT, but the output isn't always very consistent and some plugins do not write out anything.
Describe workarounds you've considered No known workarounds. Looking at the running processes doesn't really help the user understand what is going on.
Additional context Created based on #526
For plugins I think we may want to define a ASDF_VERBOSE flag to trigger verbose logging and maybe VERBOSE_OUTPUT variable with the destination file for verbose output (which would default to STDOUT). What do you think @kalkwarf?
For plugins I think we may want to define a
ASDF_VERBOSEflag to trigger verbose logging and maybeVERBOSE_OUTPUTvariable with the destination file for verbose output (which would default to STDOUT). What do you think @kalkwarf?
I think that would solve my particular needs, once the plugin(s) I use are updated to respect that flag. I like the idea of being able to (optionally) specify the log file without having to do manual redirection.
If there are no updates in this thread, then it means there are no updates. Posting "no-op comments" doesn't help anyone.
Of course, feedback is appreciated and if you would like this feature, please upvote the original comment so user-interest is properly gauged when we find issues to work on. Note that upvotes on comments do not show up on GitHub's issue filtering system. If people did that (instead of posting bumps or upvoting bumps), then this issue would have been on my radar and perhaps would have already been fixed.
