| … | |
… | |
| 113 | |
113 | |
| 114 | No large bloated libraries (of course, none were linked in |
114 | No large bloated libraries (of course, none were linked in |
| 115 | statically), except maybe libX11 :) |
115 | statically), except maybe libX11 :) |
| 116 | |
116 | |
| 117 | Does it support tabs, can I have a tabbed rxvt-unicode? |
117 | Does it support tabs, can I have a tabbed rxvt-unicode? |
| 118 | rxvt-unicode does not directly support tabs. It will work fine with |
118 | Beginning with version 7.3, there is a perl extension that |
| 119 | tabbing functionality of many window managers or similar tabbing |
119 | implements a simple tabbed terminal. It is installed by default, so |
| 120 | programs, and its embedding-features allow it to be embedded into |
120 | any of these should give you tabs: |
| 121 | other programs, as witnessed by doc/rxvt-tabbed or the upcoming |
121 | |
| 122 | "Gtk2::URxvt" perl module, which features a tabbed urxvt (murxvt) |
122 | rxvt -pe tabbed |
| 123 | terminal as an example embedding application. |
123 | |
|
|
124 | URxvt.perl-ext-common: default,tabbed |
|
|
125 | |
|
|
126 | It will also work fine with tabbing functionality of many window |
|
|
127 | managers or similar tabbing programs, and its embedding-features |
|
|
128 | allow it to be embedded into other programs, as witnessed by |
|
|
129 | doc/rxvt-tabbed or the upcoming "Gtk2::URxvt" perl module, which |
|
|
130 | features a tabbed urxvt (murxvt) terminal as an example embedding |
|
|
131 | application. |
| 124 | |
132 | |
| 125 | How do I know which rxvt-unicode version I'm using? |
133 | How do I know which rxvt-unicode version I'm using? |
| 126 | The version number is displayed with the usage (-h). Also the escape |
134 | The version number is displayed with the usage (-h). Also the escape |
| 127 | sequence "ESC [ 8 n" sets the window title to the version number. |
135 | sequence "ESC [ 8 n" sets the window title to the version number. |
| 128 | When using the rxvtc client, the version displayed is that of the |
136 | When using the rxvtc client, the version displayed is that of the |
| 129 | daemon. |
137 | daemon. |
| 130 | |
138 | |
| 131 | I am using Debian GNU/Linux and have a problem... |
139 | I am using Debian GNU/Linux and have a problem... |
| 132 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
140 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
| 133 | patches that considerably change the behaviour of rxvt-unicode. |
141 | patches that considerably change the behaviour of rxvt-unicode (but |
| 134 | Before reporting a bug to the original rxvt-unicode author please |
142 | unfortunately this notice has been removed). Before reporting a bug |
| 135 | download and install the genuine version |
143 | to the original rxvt-unicode author please download and install the |
| 136 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
144 | genuine version (<http://software.schmorp.de#rxvt-unicode>) and try |
| 137 | problem. If you cannot, chances are that the problems are specific |
145 | to reproduce the problem. If you cannot, chances are that the |
| 138 | to Debian GNU/Linux, in which case it should be reported via the |
146 | problems are specific to Debian GNU/Linux, in which case it should |
| 139 | Debian Bug Tracking System (use "reportbug" to report the bug). |
147 | be reported via the Debian Bug Tracking System (use "reportbug" to |
|
|
148 | report the bug). |
| 140 | |
149 | |
| 141 | For other problems that also affect the Debian package, you can and |
150 | For other problems that also affect the Debian package, you can and |
| 142 | probably should use the Debian BTS, too, because, after all, it's |
151 | probably should use the Debian BTS, too, because, after all, it's |
| 143 | also a bug in the Debian version and it serves as a reminder for |
152 | also a bug in the Debian version and it serves as a reminder for |
| 144 | other users that might encounter the same issue. |
153 | other users that might encounter the same issue. |
| … | |
… | |
| 165 | of encodings built-in that increase download times and are rarely |
174 | of encodings built-in that increase download times and are rarely |
| 166 | used). |
175 | used). |
| 167 | |
176 | |
| 168 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
177 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
| 169 | safe? |
178 | safe? |
| 170 | Likely not. While I honestly try to make it secure, and am probably |
179 | It should be, starting with release 7.1. You are encouraged to |
| 171 | not bad at it, I think it is simply unreasonable to expect all of |
180 | properly install urxvt with privileges necessary for your OS now. |
| 172 | freetype + fontconfig + xft + xlib + perl + ... + rxvt-unicode |
181 | |
| 173 | itself to all be secure. Also, rxvt-unicode disables some options |
|
|
| 174 | when it detects that it runs setuid or setgid, which is not nice. |
182 | When rxvt-unicode detects that it runs setuid or setgid, it will |
| 175 | Besides, with the embedded perl interpreter the possibility for |
183 | fork into a helper process for privileged operations (pty handling |
| 176 | security problems easily multiplies. |
184 | on some systems, utmp/wtmp/lastlog handling on others) and drop |
|
|
185 | privileges immediately. This is much safer than most other terminals |
|
|
186 | that keep privileges while running (but is more relevant to urxvt, |
|
|
187 | as it contains things as perl interpreters, which might be "helpful" |
|
|
188 | to attackers). |
| 177 | |
189 | |
| 178 | Elevated privileges are only required for utmp and pty operations on |
190 | This forking is done as the very first within main(), which is very |
| 179 | some systems (for example, GNU/Linux doesn't need any extra |
191 | early and reduces possible bugs to initialisation code run before |
| 180 | privileges for ptys, but some need it for utmp support). It is |
192 | main(), or things like the dynamic loader of your system, which |
| 181 | planned to mvoe this into a forked handler process, but this is not |
193 | should result in very little risk. |
| 182 | yet done. |
|
|
| 183 | |
|
|
| 184 | So, while setuid/setgid operation is supported and not a problem on |
|
|
| 185 | your typical single-user-no-other-logins unix desktop, always |
|
|
| 186 | remember that its an awful lot of code, most of which isn't checked |
|
|
| 187 | for security issues regularly. |
|
|
| 188 | |
194 | |
| 189 | When I log-in to another system it tells me about missing terminfo data? |
195 | When I log-in to another system it tells me about missing terminfo data? |
| 190 | The terminal description used by rxvt-unicode is not as widely |
196 | The terminal description used by rxvt-unicode is not as widely |
| 191 | available as that for xterm, or even rxvt (for which the same |
197 | available as that for xterm, or even rxvt (for which the same |
| 192 | problem often arises). |
198 | problem often arises). |
| … | |
… | |
| 580 | |
586 | |
| 581 | My input method wants <some encoding> but I want UTF-8, what can I do? |
587 | My input method wants <some encoding> but I want UTF-8, what can I do? |
| 582 | You can specify separate locales for the input method and the rest |
588 | You can specify separate locales for the input method and the rest |
| 583 | of the terminal, using the resource "imlocale": |
589 | of the terminal, using the resource "imlocale": |
| 584 | |
590 | |
| 585 | URxvt*imlocale: ja_JP.EUC-JP |
591 | URxvt.imlocale: ja_JP.EUC-JP |
| 586 | |
592 | |
| 587 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
593 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
| 588 | still use your input method. Please note, however, that you will not |
594 | still use your input method. Please note, however, that you will not |
| 589 | be able to input characters outside "EUC-JP" in a normal way then, |
595 | be able to input characters outside "EUC-JP" in a normal way then, |
| 590 | as your input method limits you. |
596 | as your input method limits you. |
