Thank you for creating this project. I have needed a tool like this since last year.
My suggestion is to implement a -d (debug/verbose) flag for the CLI. This would be helpful because some processes can take a long time, and without feedback, it's difficult to tell if the program is still working or if it has frozen.
For instance, downloading a Docker image can be a lengthy process, and I would like to see the current status or progress.
You can find an example of how to implement this at the link below. Instead of a "quiet" mode as described in the example, we could introduce a verbose -d flag.
https://stackoverflow.com/questions/36002654/create-quiet-mode-by-supress-stdout-bash-script
WDYT?
Thank you for creating this project. I have needed a tool like this since last year.
My suggestion is to implement a
-d(debug/verbose) flag for the CLI. This would be helpful because some processes can take a long time, and without feedback, it's difficult to tell if the program is still working or if it has frozen.For instance, downloading a Docker image can be a lengthy process, and I would like to see the current status or progress.
You can find an example of how to implement this at the link below. Instead of a "quiet" mode as described in the example, we could introduce a verbose
-dflag.https://stackoverflow.com/questions/36002654/create-quiet-mode-by-supress-stdout-bash-script
WDYT?