>> Unfortunately, I am not completely right. >> User-defined bindings may be buggy. > > Well, I only know they are confusing. It isn't just about an order of > precedence as you seem to assume. Please, notice that X translations > and accelerator shortcuts are two different binding mechanisms. You > can see the difference already by noting that shortcuts can be changed > on the fly, while X translations cannot. Moreover, shortcuts defined > for the editing area are also executed when the incremental search bar > is in focus, whereas X translations are valid there, too. (Shortcuts > are Motif stuff, X translations X stuff.) > > Adding to the confusion is the fact that the built-in menu accelerator > shortcuts are implemented in a way the user can redefine them > (including the menu description) in the X resource file, but not as X > translation, ie, nedit*text.Translations: #override, but as > nedit*[file/edit/...].Menu.[...].accelerator[Text] > > J�rg
The bug is the difference in behavior of combinations X-resouces + Background menu and X-resouces + Shell or Macro menu. The last works correctly: only one of bound macro is executed. The first is buggy: both function bound via X-resources and macro bound in menu are executed when the key is used! In both cases shortcuts are Motif stuff, X translations are X stuff. An interesting question. Does the combination X-resources + Smart Indent work correctly? Alexey -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
