From: Alan E. <ala...@gm...> - 2012-09-29 14:35:37
|
On Sat, Sep 29, 2012 at 1:42 AM, Vampire <Va...@je...> wrote: > ** > The problem with 1. is, prior to 5.0 there were no conflicts by default, > now there are for almost all localizations. > This is not only about german (A+d, A+l, A+a), it is the same for French > (A+a), Japanese (A+o), Czech (A+z, A+o, A+a) and EVEN FOR English (A+o). > The only localization we ship with that doesn't have this problem by > default is the russian one, because it doesn't actually provide any > mnemonics. > The problem of conflicts is not solved at all by your patch. > We would have to remove all A+[a-z] shortcuts from the jEdit keymap (And > the "German keyboard" keymap as it is derived from it) to make sure not to > conflict with any localization. > That's not an option for the emacs keymap. Some alt-keys have to remain that way. > It would of course be sufficient to remove the conflicting ones, but as > soon as localizations are added or changed, this has to be revisted and > rechecked and this WILL BE forgotten for sure. > that is not sufficient or desireable. > Even if we would do this, it would only serve the initial user experience > when first installing and starting jEdit. > You can still introduce those conflicts that are hard to figure out what > happened without manually remapping keys. > You can use a localization that is not shipped with jEdit and introduces > conflicts. > You can add and / or switch to a Keymap that uses conflicting bindings. > An unwary change in the jEdit Keymap can introduce a conflicting binding. > I don't care if switching keymaps results in a conflict. What I care about is that if I bind a key from shortcut options, that it works after that. If a side-effect of binding a key is to undefine a accelerator, then I would be satisfied with such a fix. But as things stand, your change introduces a bug that I want you to roll back. Prior to your change, things worked even if there was a conflict. Now they don't. |