> 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 -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
