ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.man.in
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.25 by root, Tue Oct 25 20:04:59 2005 UTC vs.
Revision 1.29 by root, Sat Dec 24 12:55:17 2005 UTC

127.\} 127.\}
128.rm #[ #] #H #V #F C 128.rm #[ #] #H #V #F C
129.\" ======================================================================== 129.\" ========================================================================
130.\" 130.\"
131.IX Title "rxvt 7" 131.IX Title "rxvt 7"
132.TH rxvt 7 "2005-10-25" "5.8" "RXVT-UNICODE" 132.TH rxvt 7 "2005-12-24" "6.0" "RXVT-UNICODE"
133.SH "NAME" 133.SH "NAME"
134RXVT REFERENCE \- FAQ, command sequences and other background information 134RXVT REFERENCE \- FAQ, command sequences and other background information
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137.Vb 2 137.Vb 2
156The newest version of this document is 156The newest version of this document is
157also available on the World Wide Web at 157also available on the World Wide Web at
158<http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>. 158<http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>.
159.SH "FREQUENTLY ASKED QUESTIONS" 159.SH "FREQUENTLY ASKED QUESTIONS"
160.IX Header "FREQUENTLY ASKED QUESTIONS" 160.IX Header "FREQUENTLY ASKED QUESTIONS"
161.IP "Isn't rxvt supposed to be small? Don't all those features bloat?" 4
162.IX Item "Isn't rxvt supposed to be small? Don't all those features bloat?"
163I often get asked about this, and I think, no, they didn't cause extra
164bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
165that the urxvt binary is larger (due to some encoding tables always being
166compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even
167with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many
168features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
169already in use in this mode.
170.Sp
171.Vb 3
172\& text data bss drs rss filename
173\& 98398 1664 24 15695 1824 rxvt --disable-everything
174\& 188985 9048 66616 18222 1788 urxvt --disable-everything
175.Ve
176.Sp
177When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft
178and full locale/XIM support which are quite bloaty inside libX11 and my
179libc), the two diverge, but not unreasnobaly so.
180.Sp
181.Vb 3
182\& text data bss drs rss filename
183\& 163431 2152 24 20123 2060 rxvt --enable-everything
184\& 1035683 49680 66648 29096 3680 urxvt --enable-everything
185.Ve
186.Sp
187The very large size of the text section is explained by the east-asian
188encoding tables, which, if unused, take up disk space but nothing else
189and can be compiled out unless you rely on X11 core fonts that use those
190encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++
191compiler allocates (but of course doesn't use unless you are out of
192memory). Also, using an xft font instead of a core font immediately adds a
193few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when
194not used.
195.Sp
196Of course, due to every character using two or four bytes instead of one,
197a large scrollback buffer will ultimately make rxvt-unicode use more
198memory.
199.Sp
200Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
201still fares rather well. And compared to some monsters like gnome-terminal
202(21152k + extra 4204k in separate processes) or konsole (22200k + extra
20343180k in daemons that stay around after exit, plus half aminute of
204startup time, including the hundreds of warnings it spits out), it fares
205extremely well *g*.
206.IP "Why \*(C+, isn't that unportable/bloated/uncool?" 4
207.IX Item "Why , isn't that unportable/bloated/uncool?"
208Is this a question? :) It comes up very often. The simple answer is: I had
209to write it, and \*(C+ allowed me to write and maintain it in a fraction
210of the time and effort (which is a scarce resource for me). Put even
211shorter: It simply wouldn't exist without \*(C+.
212.Sp
213My personal stance on this is that \*(C+ is less portable than C, but in
214the case of rxvt-unicode this hardly matters, as its portability limits
215are defined by things like X11, pseudo terminals, locale support and unix
216domain sockets, which are all less portable than \*(C+ itself.
217.Sp
218Regarding the bloat, see the above question: It's easy to write programs
219in C that use gobs of memory, an certainly possible to write programs in
220\&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is
221not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my
222system with a minimal config:
223.Sp
224.Vb 4
225\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
226\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
227\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
228\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
229.Ve
230.Sp
231And here is rxvt\-unicode:
232.Sp
233.Vb 5
234\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
235\& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
236\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
237\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
238\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
239.Ve
240.Sp
241No large bloated libraries (of course, none were linked in statically),
242except maybe libX11 :)
243.IP "Does it support tabs, can I have a tabbed rxvt\-unicode?" 4
244.IX Item "Does it support tabs, can I have a tabbed rxvt-unicode?"
245rxvt-unicode does not directly support tabs. It will work fine with
246tabbing functionality of many window managers or similar tabbing programs,
247and its embedding-features allow it to be embedded into other programs,
248as witnessed by \fIdoc/rxvt\-tabbed\fR or the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl
249module, which features a tabbed urxvt (murxvt) terminal as an example
250embedding application.
161.IP "How do I know which rxvt-unicode version I'm using?" 4 251.IP "How do I know which rxvt-unicode version I'm using?" 4
162.IX Item "How do I know which rxvt-unicode version I'm using?" 252.IX Item "How do I know which rxvt-unicode version I'm using?"
163The version number is displayed with the usage (\-h). Also the escape 253The version number is displayed with the usage (\-h). Also the escape
164sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. 254sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When
255using the @@RXVT_NAME@@c client, the version displayed is that of the
256daemon.
165.IP "I am using Debian GNU/Linux and have a problem..." 4 257.IP "I am using Debian GNU/Linux and have a problem..." 4
166.IX Item "I am using Debian GNU/Linux and have a problem..." 258.IX Item "I am using Debian GNU/Linux and have a problem..."
167The Debian GNU/Linux package of rxvt-unicode in sarge contains large 259The Debian GNU/Linux package of rxvt-unicode in sarge contains large
168patches that considerably change the behaviour of rxvt\-unicode. Before 260patches that considerably change the behaviour of rxvt\-unicode. Before
169reporting a bug to the original rxvt-unicode author please download and 261reporting a bug to the original rxvt-unicode author please download and
2388\& window op and some xterm/OSC escape sequences 2480\& window op and some xterm/OSC escape sequences
2389\& tripleclickwords 2481\& tripleclickwords
2390\& settable insecure mode 2482\& settable insecure mode
2391\& keysym remapping support 2483\& keysym remapping support
2392\& cursor blinking and underline cursor 2484\& cursor blinking and underline cursor
2393\& -embed and -pty-fd options 2485\& -embed, -pty-fd and -hold options
2394.Ve 2486.Ve
2395.IP "\-\-enable\-iso14755 (default: on)" 4 2487.IP "\-\-enable\-iso14755 (default: on)" 4
2396.IX Item "--enable-iso14755 (default: on)" 2488.IX Item "--enable-iso14755 (default: on)"
2397Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or 2489Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or
2398\&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by 2490\&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by
2426.IX Item "--enable-dlmalloc (default: off)" 2518.IX Item "--enable-dlmalloc (default: off)"
2427Use Doug Lea's malloc \- which is good for a production version 2519Use Doug Lea's malloc \- which is good for a production version
2428See <http://g.oswego.edu/dl/html/malloc.html> for details. 2520See <http://g.oswego.edu/dl/html/malloc.html> for details.
2429.IP "\-\-enable\-smart\-resize (default: on)" 4 2521.IP "\-\-enable\-smart\-resize (default: on)" 4
2430.IX Item "--enable-smart-resize (default: on)" 2522.IX Item "--enable-smart-resize (default: on)"
2431Add smart growth/shrink behaviour when changing font size via from hot 2523Add smart growth/shrink behaviour when changing font size via hot
2432keys. This should keep in a fixed position the rxvt corner which is 2524keys. This should keep the window corner which is closest to a corner of
2433closest to a corner of the screen. 2525the screen in a fixed position.
2434.IP "\-\-enable\-pointer\-blank (default: on)" 4 2526.IP "\-\-enable\-pointer\-blank (default: on)" 4
2435.IX Item "--enable-pointer-blank (default: on)" 2527.IX Item "--enable-pointer-blank (default: on)"
2436Add support to have the pointer disappear when typing or inactive. 2528Add support to have the pointer disappear when typing or inactive.
2437.IP "\-\-with\-name=NAME (default: urxvt)" 4 2529.IP "\-\-with\-name=NAME (default: urxvt)" 4
2438.IX Item "--with-name=NAME (default: urxvt)" 2530.IX Item "--with-name=NAME (default: urxvt)"

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines