| 1 | FREQUENTLY ASKED QUESTIONS |
1 | FREQUENTLY ASKED QUESTIONS |
| 2 | The new selection selects pieces that are too big/too small, can I |
2 | The new selection selects pieces that are too big, how can I select |
| 3 | change this? |
3 | single words? |
| 4 | Yes. For example, if you want to select smaller pieces ("words") you |
4 | Yes. For example, if you want to select alphanumeric words, you can |
| 5 | can use the following resource: |
5 | use the following resource: |
| 6 | |
6 | |
| 7 | URxvt.selection.pattern-0: ([[:word:]]+) |
7 | URxvt.selection.pattern-0: ([[:word:]]+) |
| 8 | |
8 | |
| 9 | If you click more than twice, the selection will be extended more |
9 | If you click more than twice, the selection will be extended more |
| 10 | and more. |
10 | and more. |
| 11 | |
11 | |
| 12 | To get a selection that is very similar to the old code, try this |
12 | To get a selection that is very similar to the old code, try this |
| 13 | pattern: |
13 | pattern: |
| 14 | |
14 | |
| 15 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
15 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
|
|
16 | |
|
|
17 | Please also note that the *LeftClick Shift-LeftClik* combination |
|
|
18 | also selects words like the old code. |
| 16 | |
19 | |
| 17 | I don't like the new selection/popups/hotkeys/perl, how do I |
20 | I don't like the new selection/popups/hotkeys/perl, how do I |
| 18 | change/disable it? |
21 | change/disable it? |
| 19 | You can disable the perl extension completely by setting the |
22 | You can disable the perl extension completely by setting the |
| 20 | perl-ext-common resource to the empty string, which also keeps |
23 | perl-ext-common resource to the empty string, which also keeps |
| … | |
… | |
| 125 | When using the rxvtc client, the version displayed is that of the |
128 | When using the rxvtc client, the version displayed is that of the |
| 126 | daemon. |
129 | daemon. |
| 127 | |
130 | |
| 128 | I am using Debian GNU/Linux and have a problem... |
131 | I am using Debian GNU/Linux and have a problem... |
| 129 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
132 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
| 130 | patches that considerably change the behaviour of rxvt-unicode. |
133 | patches that considerably change the behaviour of rxvt-unicode (but |
| 131 | Before reporting a bug to the original rxvt-unicode author please |
134 | unfortunately this notice has been removed). Before reporting a bug |
| 132 | download and install the genuine version |
135 | to the original rxvt-unicode author please download and install the |
| 133 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
136 | genuine version (<http://software.schmorp.de#rxvt-unicode>) and try |
| 134 | problem. If you cannot, chances are that the problems are specific |
137 | to reproduce the problem. If you cannot, chances are that the |
| 135 | to Debian GNU/Linux, in which case it should be reported via the |
138 | problems are specific to Debian GNU/Linux, in which case it should |
| 136 | Debian Bug Tracking System (use "reportbug" to report the bug). |
139 | be reported via the Debian Bug Tracking System (use "reportbug" to |
|
|
140 | report the bug). |
| 137 | |
141 | |
| 138 | For other problems that also affect the Debian package, you can and |
142 | For other problems that also affect the Debian package, you can and |
| 139 | probably should use the Debian BTS, too, because, after all, it's |
143 | probably should use the Debian BTS, too, because, after all, it's |
| 140 | also a bug in the Debian version and it serves as a reminder for |
144 | also a bug in the Debian version and it serves as a reminder for |
| 141 | other users that might encounter the same issue. |
145 | other users that might encounter the same issue. |
| … | |
… | |
| 162 | of encodings built-in that increase download times and are rarely |
166 | of encodings built-in that increase download times and are rarely |
| 163 | used). |
167 | used). |
| 164 | |
168 | |
| 165 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
169 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
| 166 | safe? |
170 | safe? |
| 167 | Likely not. While I honestly try to make it secure, and am probably |
171 | It should be, starting with release 7.1. You are encouraged to |
| 168 | not bad at it, I think it is simply unreasonable to expect all of |
172 | properly install urxvt with privileges necessary for your OS now. |
| 169 | freetype + fontconfig + xft + xlib + perl + ... + rxvt-unicode |
173 | |
| 170 | itself to all be secure. Also, rxvt-unicode disables some options |
|
|
| 171 | when it detects that it runs setuid or setgid, which is not nice. |
174 | When rxvt-unicode detects that it runs setuid or setgid, it will |
| 172 | Besides, with the embedded perl interpreter the possibility for |
175 | fork into a helper process for privileged operations (pty handling |
| 173 | security problems easily multiplies. |
176 | on some systems, utmp/wtmp/lastlog handling on others) and drop |
|
|
177 | privileges immediately. This is much safer than most other terminals |
|
|
178 | that keep privileges while running (but is more relevant to urxvt, |
|
|
179 | as it contains things as perl interpreters, which might be "helpful" |
|
|
180 | to attackers). |
| 174 | |
181 | |
| 175 | Elevated privileges are only required for utmp and pty operations on |
182 | This forking is done as the very first within main(), which is very |
| 176 | some systems (for example, GNU/Linux doesn't need any extra |
183 | early and reduces possible bugs to initialisation code run before |
| 177 | privileges for ptys, but some need it for utmp support). It is |
184 | main(), or things like the dynamic loader of your system, which |
| 178 | planned to mvoe this into a forked handler process, but this is not |
185 | should result in very little risk. |
| 179 | yet done. |
|
|
| 180 | |
|
|
| 181 | So, while setuid/setgid operation is supported and not a problem on |
|
|
| 182 | your typical single-user-no-other-logins unix desktop, always |
|
|
| 183 | remember that its an awful lot of code, most of which isn't checked |
|
|
| 184 | for security issues regularly. |
|
|
| 185 | |
186 | |
| 186 | When I log-in to another system it tells me about missing terminfo data? |
187 | When I log-in to another system it tells me about missing terminfo data? |
| 187 | The terminal description used by rxvt-unicode is not as widely |
188 | The terminal description used by rxvt-unicode is not as widely |
| 188 | available as that for xterm, or even rxvt (for which the same |
189 | available as that for xterm, or even rxvt (for which the same |
| 189 | problem often arises). |
190 | problem often arises). |
| … | |
… | |
| 577 | |
578 | |
| 578 | My input method wants <some encoding> but I want UTF-8, what can I do? |
579 | My input method wants <some encoding> but I want UTF-8, what can I do? |
| 579 | You can specify separate locales for the input method and the rest |
580 | You can specify separate locales for the input method and the rest |
| 580 | of the terminal, using the resource "imlocale": |
581 | of the terminal, using the resource "imlocale": |
| 581 | |
582 | |
| 582 | URxvt*imlocale: ja_JP.EUC-JP |
583 | URxvt.imlocale: ja_JP.EUC-JP |
| 583 | |
584 | |
| 584 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
585 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and |
| 585 | still use your input method. Please note, however, that you will not |
586 | still use your input method. Please note, however, that you will not |
| 586 | be able to input characters outside "EUC-JP" in a normal way then, |
587 | be able to input characters outside "EUC-JP" in a normal way then, |
| 587 | as your input method limits you. |
588 | as your input method limits you. |
| … | |
… | |
| 630 | Mouse cut/paste suddenly no longer works. |
631 | Mouse cut/paste suddenly no longer works. |
| 631 | Make sure that mouse reporting is actually turned off since killing |
632 | Make sure that mouse reporting is actually turned off since killing |
| 632 | some editors prematurely may leave the mouse in mouse report mode. |
633 | some editors prematurely may leave the mouse in mouse report mode. |
| 633 | I've heard that tcsh may use mouse reporting unless it otherwise |
634 | I've heard that tcsh may use mouse reporting unless it otherwise |
| 634 | specified. A quick check is to see if cut/paste works when the Alt |
635 | specified. A quick check is to see if cut/paste works when the Alt |
| 635 | or Shift keys are depressed. See rxvt(7) |
636 | or Shift keys are depressed. |
| 636 | |
637 | |
| 637 | What's with this bold/blink stuff? |
638 | What's with this bold/blink stuff? |
| 638 | If no bold colour is set via "colorBD:", bold will invert text using |
639 | If no bold colour is set via "colorBD:", bold will invert text using |
| 639 | the standard foreground colour. |
640 | the standard foreground colour. |
| 640 | |
641 | |
| … | |
… | |
| 726 | |
727 | |
| 727 | # use Backspace = ^? |
728 | # use Backspace = ^? |
| 728 | $ stty erase ^? |
729 | $ stty erase ^? |
| 729 | $ rxvt |
730 | $ rxvt |
| 730 | |
731 | |
| 731 | Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7). |
732 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
| 732 | |
733 | |
| 733 | For an existing rxvt-unicode: |
734 | For an existing rxvt-unicode: |
| 734 | |
735 | |
| 735 | # use Backspace = ^H |
736 | # use Backspace = ^H |
| 736 | $ stty erase ^H |
737 | $ stty erase ^H |
