Join GitHub today
Add completion for dconf #3638
I had a few minutes of free time and an itch to write some completions, so I fixed it. Sorry
Anyway, it turns out that
$ dconf read <TAB> $ dconf read /org/<TAB> $ dconf read /org/gnome/<TAB>
and so on just to end up with
Wow, that was fast! Thanks @faho .
I still think though that it makes more sense if the
Consider this scenario: let's say my key which I am looking for is somewhere under
dconf read /org/gnome/<TAB>
I get a lot of keys from
where its (obviously) easier to find the
However, I must say that also the full-path completion style has its benefits - if you know the filename/part of the path you can search much easier:
I can't say I have a strong opinion about this, but I think the dir-by-dir-type completion is more intuitive for users (as it is used for file/dir path completions). Writing long paths is IMHO well covered by suggestions if the user wants to use them more than once.
Maybe it would be best if both completion styles were available. (I'm not sure how.)
It's probably worth noting that I'm not running gnome, so the only thing I have using dconf is gnome-terminal and mate-terminal, which I sometimes use for testing. That means I have a total of 20 keys and don't know how this would feel if I had more. How many keys do you have on gnome?
It's actually even quicker to just type
The main issue I have there is that the first part is almost always "/org/", so you end up typing a lot, since you either do "
Additionally, I actually started out using
This is one of those cases where we should just pick one. If anyone really prefers another, they can override the completion.