Future Feature Idea: Make the xdg-utils explain what they are doing
This one is inspired by Debian bug #771941.
When implemented it would make the xdg-utils
explain what they are doing/would do (the debug statements already kind of do this) in addition of an option that will make operations with side effects (modifying files, running commands from desktop files) dry run (writing out in plain English what it would do instead of running the given command).
My idea would result in two additional command line flags: --verbose
and --dry-run
(maybe an --explain
as an alias for both) where --verbose
would turn on the debug output like setting the XDG_UTILS_DEBUG_LEVEL
environment variable would.
Maybe this feature could be used as part of the testing suite?
As there are currently higher priority issues this is just written down to not forget the idea, also there is probably some discussion needed on how some of the details would translate to the existing code and which commands should support such a feature.