… | |
… | |
162 | |
162 | |
163 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
163 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
164 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
164 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
165 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
165 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
166 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
166 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
167 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
167 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
168 | |
168 | |
169 | No large bloated libraries (of course, none were linked in statically), |
169 | No large bloated libraries (of course, none were linked in statically), |
170 | except maybe libX11 :) |
170 | except maybe libX11 :) |
171 | |
171 | |
172 | Rendering, Font & Look and Feel Issues |
172 | Rendering, Font & Look and Feel Issues |
… | |
… | |
772 | The terminal description used by rxvt-unicode is not as widely available |
772 | The terminal description used by rxvt-unicode is not as widely available |
773 | as that for xterm, or even rxvt (for which the same problem often |
773 | as that for xterm, or even rxvt (for which the same problem often |
774 | arises). |
774 | arises). |
775 | |
775 | |
776 | The correct solution for this problem is to install the terminfo, this |
776 | The correct solution for this problem is to install the terminfo, this |
777 | can be done like this (with ncurses' infocmp): |
777 | can be done like this (with ncurses' infocmp and works as user and |
|
|
778 | admin): |
778 | |
779 | |
779 | REMOTE=remotesystem.domain |
780 | REMOTE=remotesystem.domain |
780 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
781 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
781 | |
782 | |
782 | ... or by installing rxvt-unicode normally on the remote system, |
783 | ... or by installing rxvt-unicode normally on the remote system, |
|
|
784 | |
|
|
785 | One some systems you might need to set $TERMINFO to the full path of |
|
|
786 | $HOME/.terminfo for this to work. |
783 | |
787 | |
784 | If you cannot or do not want to do this, then you can simply set |
788 | If you cannot or do not want to do this, then you can simply set |
785 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
789 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
786 | problems arising, which includes wrong keymapping, less and different |
790 | problems arising, which includes wrong keymapping, less and different |
787 | colours and some refresh errors in fullscreen applications. It's a nice |
791 | colours and some refresh errors in fullscreen applications. It's a nice |
… | |
… | |
981 | For scim, use "@im=SCIM". You can see what input method servers are |
985 | For scim, use "@im=SCIM". You can see what input method servers are |
982 | running with this command: |
986 | running with this command: |
983 | |
987 | |
984 | xprop -root XIM_SERVERS |
988 | xprop -root XIM_SERVERS |
985 | |
989 | |
986 | |
990 | * |
987 | |
991 | |
988 | My input method wants <some encoding> but I want UTF-8, what can I do? |
992 | My input method wants <some encoding> but I want UTF-8, what can I do? |
989 | You can specify separate locales for the input method and the rest of |
993 | You can specify separate locales for the input method and the rest of |
990 | the terminal, using the resource "imlocale": |
994 | the terminal, using the resource "imlocale": |
991 | |
995 | |