If you don't know what translations are, you probably don't need to do
this. However, it is possible to attach certain actions within xlincks to
particular keyboard sequences. For example, the default keyboard
sequence for expanding an item in a new window is
Ctrl<Btn1Down>
and the default for expanding in the same window
is Ctrl<Btn2Down>
. If, instead, you wish to switch these,
you can put the following in your .Xdefaults file:
! This line, begun with ! is a comment line ! switch the normal translations xlincks*Contents.?.Translations: #override\ Ctrl<Btn2Down>: exp-in-new()\n\ Ctrl<Btn1Down>: exp-in-place()
! bind these actions to L? buttons to make them easier to use xlincks*Contents.?.Translations: \#override\ <Key>L1: pop-in-place()\n\ <Key>L2: pop-in-new()\n\ <Key>L4: exp-in-new()\n\ <Key>L3: exp-in-place()
! bind these in a really strange place xlincks*Contents.?.Translations: \#override\ Meta<Key>1: store-window()\n\ Meta<Key>2: close-window()\n\ Meta<Key>3: insert-plural()\n\ Meta<Key>4: delete-plural()