I've been trying to figure out what's making it so hard for me to get keybindings to stick for Caja scripts I've created. After adding the key-combo to a script's entry in the ~/.config/caja/accels file the effect should be immediate - but this is far from the case. While they will eventually stick - the keyboard shortcuts keep getting removed as accels refreshes itself, and I have to keep adding them back – it can be many hours. It took 2 days of this for the last shortcut to finally get registered, and logging out – even rebooting – had no effect. The time between defining the shortcut and it being available is totally random (from a few minutes to 2 days), and I simply can't make sense of it, since it's not like I am doing anything wrong like trying to define a shortcut with a keybinding that is already used elsewhere. So it's not that I can't get them to work, but that I can't get the effect to be immediate, which logic says it should be, and the delay is driving me nuts.
And, before you ask, I always remove the semi-colon and space at the beginning of the line when adding the key-combo, as apparently that's needed, and sometimes I've done that repeatedly for the same entry. As well as replace the keybinding which keeps getting removed.
I've seen in the forums mention of a can-change-accels option in Dconf at /org/mate/desktop/interface/ but it no longer exists (I guess this was retired?). I'd ask for a command that can add that back, but I suspect its exclusion is by design, probably because that's enabled by default. So does anyone know what is going on here, and how I can fix this? Or does this sound like a bug I should be reporting? Many thanks in advance for your help!