PS: I just solved the same problem to avoid the biding Alt Return:fullscreen() \n\, to be able to pass Alt-return to an application.
See the eightBitInput resource for a full discussion.
The metaSendsEscape resource is tested first. The exact action depends on the value of the altSendsEscape and the metaSendsEscape and the eightBitInput resources. If the value is in that range, depending on the resource values, xterm may then do one of the following: add 128 to the value, setting its eighth bit, send an ESC byte before the key, or send the key unaltered. Only single-byte values are treated specially. The term eight-bit is misleading: xterm checks if the key is in the range 128 to 255 (the eighth bit is set). This action inserts an eight-bit (Meta) version of the character or string associated with the key that was pressed. This action inserts the character or string associated with the key that was pressed. stty erase character (H for backspace, for delete). If you are looking for already-binded keys to be passed without xterm handling it, propably you are looking for insert() or insert-eight-bit() actions. Normally it is XTerm, but can be set to another class such as UXTerm to override selected. Perhaps you could make a special translation which used a string action. However, agreeing with StéphaneChazelas, it is unclear how you would effectively use the proposed change because the escape sequences which are passed to the application are constructed inside xterm based on button-events. The program unusable unless you provide a similar definition in Xterm also recognizes "default", but omitting that will make "fullscreen", "scroll-lock", "shift-fonts" or "wheel-mouse". The resource value is a comma-separated list of keywords, which may be abbreviated: Selectively omit one or more parts of xterm's default With that version, the translations table is broken up into more manageable parts which allows somewhat better customization:
That was one of the reasons for adding the omitTranslation resource in patch #269. You can override or augment but not selectively remove a part of a translation table. It works now for me, although I cannot explain why it did not before.As I understand it, there is no function in X Toolkit which can remove a translation. I just removed the xterm entries in ~/.Xresources:Īnd appended the lines below to '/usr/share/X11/app-defaults/XTerm' (as root):Īnd there it is: a xterm window with green background and orange text. I had a look into /usr/share/X11/app-defaults/ for that, but it does not work for me I spent the better part of yesterday's evening and this afternoon on this, but I am still stuck.īack on topic: I would like my xterm to have a dark background and light foreground colors. I am a litte bit confused, because I think I must make a mistake here, but I cannot figure out where. Posted: Mon 4:09 pm Post subject: XTerm customize background/foreground color does not workĪgain, I need your help folks.
Gentoo Forums Forum Index Desktop Environments
XTerm customize background/foreground color does not work Gentoo Forums :: View topic - XTerm customize background/foreground color does not work