1 | FREQUENTLY ASKED QUESTIONS |
1 | FREQUENTLY ASKED QUESTIONS |
|
|
2 | The new selection selects pieces that are too big, how can I select |
|
|
3 | single words? |
|
|
4 | Yes. For example, if you want to select alphanumeric words, you can |
|
|
5 | use the following resource: |
|
|
6 | |
|
|
7 | URxvt.selection.pattern-0: ([[:word:]]+) |
|
|
8 | |
|
|
9 | If you click more than twice, the selection will be extended more |
|
|
10 | and more. |
|
|
11 | |
|
|
12 | To get a selection that is very similar to the old code, try this |
|
|
13 | pattern: |
|
|
14 | |
|
|
15 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
|
|
16 | |
|
|
17 | Please also note that the *LeftClick Shift-LeftClik* combination |
|
|
18 | also selects words like the old code. |
|
|
19 | |
|
|
20 | I don't like the new selection/popups/hotkeys/perl, how do I |
|
|
21 | change/disable it? |
|
|
22 | You can disable the perl extension completely by setting the |
|
|
23 | perl-ext-common resource to the empty string, which also keeps |
|
|
24 | rxvt-unicode from initialising perl, saving memory. |
|
|
25 | |
|
|
26 | If you only want to disable specific features, you first have to |
|
|
27 | identify which perl extension is responsible. For this, read the |
|
|
28 | section PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For |
|
|
29 | example, to disable the selection-popup and option-popup, specify |
|
|
30 | this perl-ext-common resource: |
|
|
31 | |
|
|
32 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
|
|
33 | |
|
|
34 | This will keep the default extensions, but disable the two popup |
|
|
35 | extensions. Some extensions can also be configured, for example, |
|
|
36 | scrollback search mode is triggered by M-s. You can move it to any |
|
|
37 | other combination either by setting the searchable-scrollback |
|
|
38 | resource: |
|
|
39 | |
|
|
40 | URxvt.searchable-scrollback: CM-s |
|
|
41 | |
2 | Isn't rxvt supposed to be small? Don't all those features bloat? |
42 | Isn't rxvt supposed to be small? Don't all those features bloat? |
3 | I often get asked about this, and I think, no, they didn't cause |
43 | I often get asked about this, and I think, no, they didn't cause |
4 | extra bloat. If you compare a minimal rxvt and a minimal urxvt, you |
44 | extra bloat. If you compare a minimal rxvt and a minimal urxvt, you |
5 | can see that the urxvt binary is larger (due to some encoding tables |
45 | can see that the urxvt binary is larger (due to some encoding tables |
6 | always being compiled in), but it actually uses less memory (RSS) |
46 | always being compiled in), but it actually uses less memory (RSS) |
… | |
… | |
35 | |
75 | |
36 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), |
76 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), |
37 | this still fares rather well. And compared to some monsters like |
77 | this still fares rather well. And compared to some monsters like |
38 | gnome-terminal (21152k + extra 4204k in separate processes) or |
78 | gnome-terminal (21152k + extra 4204k in separate processes) or |
39 | konsole (22200k + extra 43180k in daemons that stay around after |
79 | konsole (22200k + extra 43180k in daemons that stay around after |
40 | exit, plus half aminute of startup time, including the hundreds of |
80 | exit, plus half a minute of startup time, including the hundreds of |
41 | warnings it spits out), it fares extremely well *g*. |
81 | warnings it spits out), it fares extremely well *g*. |
42 | |
82 | |
43 | Why C++, isn't that unportable/bloated/uncool? |
83 | Why C++, isn't that unportable/bloated/uncool? |
44 | Is this a question? :) It comes up very often. The simple answer is: |
84 | Is this a question? :) It comes up very often. The simple answer is: |
45 | I had to write it, and C++ allowed me to write and maintain it in a |
85 | I had to write it, and C++ allowed me to write and maintain it in a |
… | |
… | |
83 | terminal as an example embedding application. |
123 | terminal as an example embedding application. |
84 | |
124 | |
85 | How do I know which rxvt-unicode version I'm using? |
125 | How do I know which rxvt-unicode version I'm using? |
86 | The version number is displayed with the usage (-h). Also the escape |
126 | The version number is displayed with the usage (-h). Also the escape |
87 | sequence "ESC [ 8 n" sets the window title to the version number. |
127 | sequence "ESC [ 8 n" sets the window title to the version number. |
88 | When using the urxvtc client, the version displayed is that of the |
128 | When using the rxvtc client, the version displayed is that of the |
89 | daemon. |
129 | daemon. |
90 | |
130 | |
91 | I am using Debian GNU/Linux and have a problem... |
131 | I am using Debian GNU/Linux and have a problem... |
92 | 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 |
93 | patches that considerably change the behaviour of rxvt-unicode. |
133 | patches that considerably change the behaviour of rxvt-unicode (but |
94 | Before reporting a bug to the original rxvt-unicode author please |
134 | unfortunately this notice has been removed). Before reporting a bug |
95 | download and install the genuine version |
135 | to the original rxvt-unicode author please download and install the |
96 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
136 | genuine version (<http://software.schmorp.de#rxvt-unicode>) and try |
97 | problem. If you cannot, chances are that the problems are specific |
137 | to reproduce the problem. If you cannot, chances are that the |
98 | 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 |
99 | 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). |
100 | |
141 | |
101 | 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 |
102 | 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 |
103 | 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 |
104 | other users that might encounter the same issue. |
145 | other users that might encounter the same issue. |
|
|
146 | |
|
|
147 | I am maintaining rxvt-unicode for distribution/OS XXX, any |
|
|
148 | recommendation? |
|
|
149 | You should build one binary with the default options. configure now |
|
|
150 | enables most useful options, and the trend goes to making them |
|
|
151 | runtime-switchable, too, so there is usually no drawback to enbaling |
|
|
152 | them, except higher disk and possibly memory usage. The perl |
|
|
153 | interpreter should be enabled, as important functionality (menus, |
|
|
154 | selection, likely more in the future) depends on it. |
|
|
155 | |
|
|
156 | You should not overwrite the "perl-ext-common" snd "perl-ext" |
|
|
157 | resources system-wide (except maybe with "defaults"). This will |
|
|
158 | result in useful behaviour. If your distribution aims at low memory, |
|
|
159 | add an empty "perl-ext-common" resource to the app-defaults file. |
|
|
160 | This will keep the perl interpreter disabled until the user enables |
|
|
161 | it. |
|
|
162 | |
|
|
163 | If you can/want build more binaries, I recommend building a minimal |
|
|
164 | one with "--disable-everything" (very useful) and a maximal one with |
|
|
165 | "--enable-everything" (less useful, it will be very big due to a lot |
|
|
166 | of encodings built-in that increase download times and are rarely |
|
|
167 | used). |
|
|
168 | |
|
|
169 | I need to make it setuid/setgid to support utmp/ptys on my OS, is this |
|
|
170 | safe? |
|
|
171 | It should be, starting with release 7.1. You are encouraged to |
|
|
172 | properly install urxvt with privileges necessary for your OS now. |
|
|
173 | |
|
|
174 | When rxvt-unicode detects that it runs setuid or setgid, it will |
|
|
175 | fork into a helper process for privileged operations (pty handling |
|
|
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). |
|
|
181 | |
|
|
182 | This forking is done as the very first within main(), which is very |
|
|
183 | early and reduces possible bugs to initialisation code run before |
|
|
184 | main(), or things like the dynamic loader of your system, which |
|
|
185 | should result in very little risk. |
105 | |
186 | |
106 | 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? |
107 | The terminal description used by rxvt-unicode is not as widely |
188 | The terminal description used by rxvt-unicode is not as widely |
108 | 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 |
109 | problem often arises). |
190 | problem often arises). |
… | |
… | |
134 | |
215 | |
135 | "tic" outputs some error when compiling the terminfo entry. |
216 | "tic" outputs some error when compiling the terminfo entry. |
136 | Most likely it's the empty definition for "enacs=". Just replace it |
217 | Most likely it's the empty definition for "enacs=". Just replace it |
137 | by "enacs=\E[0@" and try again. |
218 | by "enacs=\E[0@" and try again. |
138 | |
219 | |
139 | "bash"'s readline does not work correctly under urxvt. |
220 | "bash"'s readline does not work correctly under rxvt. |
140 | I need a termcap file entry. |
221 | I need a termcap file entry. |
141 | One reason you might want this is that some distributions or |
222 | One reason you might want this is that some distributions or |
142 | operating systems still compile some programs using the |
223 | operating systems still compile some programs using the |
143 | long-obsoleted termcap library (Fedora Core's bash is one example) |
224 | long-obsoleted termcap library (Fedora Core's bash is one example) |
144 | and rely on a termcap entry for "rxvt-unicode". |
225 | and rely on a termcap entry for "rxvt-unicode". |
… | |
… | |
255 | indeed look correct. |
336 | indeed look correct. |
256 | |
337 | |
257 | In that case, select a font of your taste and add it to the font |
338 | In that case, select a font of your taste and add it to the font |
258 | list, e.g.: |
339 | list, e.g.: |
259 | |
340 | |
260 | urxvt -fn basefont,font2,font3... |
341 | rxvt -fn basefont,font2,font3... |
261 | |
342 | |
262 | When rxvt-unicode sees a character, it will first look at the base |
343 | When rxvt-unicode sees a character, it will first look at the base |
263 | font. If the base font does not contain the character, it will go to |
344 | font. If the base font does not contain the character, it will go to |
264 | the next font, and so on. Specifying your own fonts will also speed |
345 | the next font, and so on. Specifying your own fonts will also speed |
265 | up this search and use less resources within rxvt-unicode and the |
346 | up this search and use less resources within rxvt-unicode and the |
… | |
… | |
497 | |
578 | |
498 | 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? |
499 | 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 |
500 | of the terminal, using the resource "imlocale": |
581 | of the terminal, using the resource "imlocale": |
501 | |
582 | |
502 | URxvt*imlocale: ja_JP.EUC-JP |
583 | URxvt.imlocale: ja_JP.EUC-JP |
503 | |
584 | |
504 | 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 |
505 | 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 |
506 | 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, |
507 | as your input method limits you. |
588 | as your input method limits you. |
… | |
… | |
550 | Mouse cut/paste suddenly no longer works. |
631 | Mouse cut/paste suddenly no longer works. |
551 | Make sure that mouse reporting is actually turned off since killing |
632 | Make sure that mouse reporting is actually turned off since killing |
552 | some editors prematurely may leave the mouse in mouse report mode. |
633 | some editors prematurely may leave the mouse in mouse report mode. |
553 | 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 |
554 | 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 |
555 | or Shift keys are depressed. See urxvt(7) |
636 | or Shift keys are depressed. |
556 | |
637 | |
557 | What's with this bold/blink stuff? |
638 | What's with this bold/blink stuff? |
558 | 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 |
559 | the standard foreground colour. |
640 | the standard foreground colour. |
560 | |
641 | |
… | |
… | |
615 | URxvt.color6: #73f7ff |
696 | URxvt.color6: #73f7ff |
616 | URxvt.color14: #73f7ff |
697 | URxvt.color14: #73f7ff |
617 | URxvt.color7: #e1dddd |
698 | URxvt.color7: #e1dddd |
618 | URxvt.color15: #e1dddd |
699 | URxvt.color15: #e1dddd |
619 | |
700 | |
620 | How can I start urxvtd in a race-free way? |
701 | How can I start rxvtd in a race-free way? |
621 | Try "urxvtd -f -o", which tells urxvtd to open the display, create |
702 | Try "rxvtd -f -o", which tells rxvtd to open the display, create the |
622 | the listening socket and then fork. |
703 | listening socket and then fork. |
623 | |
704 | |
624 | What's with the strange Backspace/Delete key behaviour? |
705 | What's with the strange Backspace/Delete key behaviour? |
625 | Assuming that the physical Backspace key corresponds to the |
706 | Assuming that the physical Backspace key corresponds to the |
626 | BackSpace keysym (not likely for Linux ... see the following |
707 | BackSpace keysym (not likely for Linux ... see the following |
627 | question) there are two standard values that can be used for |
708 | question) there are two standard values that can be used for |
… | |
… | |
640 | |
721 | |
641 | For starting a new rxvt-unicode: |
722 | For starting a new rxvt-unicode: |
642 | |
723 | |
643 | # use Backspace = ^H |
724 | # use Backspace = ^H |
644 | $ stty erase ^H |
725 | $ stty erase ^H |
645 | $ urxvt |
726 | $ rxvt |
646 | |
727 | |
647 | # use Backspace = ^? |
728 | # use Backspace = ^? |
648 | $ stty erase ^? |
729 | $ stty erase ^? |
649 | $ urxvt |
730 | $ rxvt |
650 | |
731 | |
651 | Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in urxvt(7). |
732 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
652 | |
733 | |
653 | For an existing rxvt-unicode: |
734 | For an existing rxvt-unicode: |
654 | |
735 | |
655 | # use Backspace = ^H |
736 | # use Backspace = ^H |
656 | $ stty erase ^H |
737 | $ stty erase ^H |
… | |
… | |
682 | There are some compile-time selections available via configure. |
763 | There are some compile-time selections available via configure. |
683 | Unless you have run "configure" with the "--disable-resources" |
764 | Unless you have run "configure" with the "--disable-resources" |
684 | option you can use the `keysym' resource to alter the keystrings |
765 | option you can use the `keysym' resource to alter the keystrings |
685 | associated with keysyms. |
766 | associated with keysyms. |
686 | |
767 | |
687 | Here's an example for a URxvt session started using "urxvt -name |
768 | Here's an example for a URxvt session started using "rxvt -name |
688 | URxvt" |
769 | URxvt" |
689 | |
770 | |
690 | URxvt.keysym.Home: \033[1~ |
771 | URxvt.keysym.Home: \033[1~ |
691 | URxvt.keysym.End: \033[4~ |
772 | URxvt.keysym.End: \033[4~ |
692 | URxvt.keysym.C-apostrophe: \033<C-'> |
773 | URxvt.keysym.C-apostrophe: \033<C-'> |