The only reason that, sofar, keeps me from switching from ROX to Thunar is the dynamic keybindings that ROX sports.
This may seem trivial, but it is very important for me: My use of the GUI is mostly keyboard-driven, and thus having quick and useable shortcuts to every entry in the menus is crucial. This includes, especially, the custom actions, which would become a lot more useable if one could bind a ket to them.
GNOME, for example, has a can_change_accels entry in gconf that will allow this. ROX requires that you set something similar in some file -- I can't remember where now. The GIMP takes advantage of GNOME's can_change_accels entry, and that is what turns its interface from a hell to a breeze to use (because, in the end, when you end up using an application a lot you just learn the keybindings, and if you can define your own the speed to learn and use them is widely increased).
Another thing that would improve (but is less urgent to me) my experience with thunar is ROXs ability to resize the window by double-clicking on the background. This action has the file browser window adjust automatically to show as much files as possible, which is very handy.
Thunar does that already:
(In reply to comment #1)
> Thunar does that already:
It doesn't work in context menus, and therefore it doesn't work for custom actions (such as 'terminal here').
You cannot currently assign keyboard shortcuts to custom actions.
(In reply to comment #3)
> You cannot currently assign keyboard shortcuts to custom actions.
Exactly. That's my point. :o)
Then you should choose the right component and a subject that matches your request. ;)
*** Bug 2894 has been marked as a duplicate of this bug. ***
Moving this to core instead of uca. Shortcuts for custom actions would be cool but if we make that possible, we probably also want shortcuts for menu items provided by other plugins, not just thunar-uca.
A possible (not 100% finished) solution can be found here:
Unfortunately, the internal names of menu items are unique but not persistent. Thus, reordering the items may result in switched keyboard shortcuts. If we can fix that, we're done.
*** Bug 2959 has been marked as a duplicate of this bug. ***
Custom actions' internal names surely are (or can be made) persistent. They can simply be the <name>s from uca.xml?
*** Bug 9706 has been marked as a duplicate of this bug. ***
Pushed Jannis' code to master in dae9c33 with some small simplifications.