Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
kdb stash: does not remove errornous config files #2386
Currently we offer the tool
# Add erroneous data printf 'Error' > "$(kdb file user/tests/error)" kdb ls user/tests/error # RET: 5 # Try to remove all configuration data kdb stash # RET: 1 # The configuration data still exists kdb ls user/tests/error # RET: 5
. A command
That is of course another valid option. The advantage of a new command would be that
changed the title
KDB Reset: Create Tool to Reset Key Database to Default State
Feb 9, 2019
This is exactly what
Yes, this was the idea of
Which is not a very nice behavior if you are actually also using Elektra on that system. And of course it is the goal that Elektra devs also use Elektra. Thus we should fix
To fix the bug described here, I think it would be enough if
That might be the case. However, I still think the name “stash” does not make that very clear:
(Source: New Oxford American Dictionary).
I do not think that providing a way to get rid of all custom configuration is bad behavior. A lot of tools even show such options quite prominently. For example, the preferences window of Docker Desktop contains a tab “Reset”:
Like @sanssecours suggested, I think we should implement
This describes it quite well, doesn't it? The only problem is that it is not "something" but "everything". And that "store" only implies "move" on real objects. The name is taken from git terminology.
Better suggestions are always welcomed.
It is not "bad", it is only very against usability. Everything that you remove, format, clear, reset, ... without any way of undo requires a good backup and restore strategy which typical end users often do not have. So if you take usability serious, you try to avoid such functionality (see #898 for how harmful a simple