>On Thu, Jan 02, 2014 at 11:44:09AM +0000, Zefram wrote:
Thomas Dickey wrote:
>which translation was performing the backspace?
I'm not sure what you mean by this question. The relevant item in the
translations resource is
<Key>BackSpace: string(0x08)
I have other translation items in the same resource, such as
Alt <Key>b: scroll-back(1,page)
which are equally affected by this problem.
I've stored the resource under different keys at different times, as
described in my previous message. In one experiment I had separate
XTerm.vt100.translations and XTerm.vt100.scrollbar.translations,
and for the experiment I put different content in the two resources.
XTerm.vt100.translations applied when focus was on the text, frame,
or titlebar, and XTerm.vt100.scrollbar.translations applied when focus
was on the scrollbar. My permanent setup has only a single translations
resource, under the key "XTerm.vt100*translations".
>As long as the translations merge rather than override, that's a good solution.
I'm not sure what you're imagining merging. As I have only one
translations resource, there's no merging to perform among my resources.
My resource does merge with the default key and mouse bindings, of which
the mouse bindings differ between scrollbar context and other contexts.
-zefram
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140103115043.gz21...@fysh.org
