--- rxvt-unicode/README.FAQ 2006/07/06 19:43:21 1.42 +++ rxvt-unicode/README.FAQ 2007/02/17 20:36:35 1.46 @@ -44,7 +44,7 @@ Try "urxvtd -f -o", which tells urxvtd to open the display, create the listening socket and then fork. - How can I start urxvtd automatically when I run URXVT_NAME@@c? + How can I start urxvtd automatically when I run urxvtc? If you want to start urxvtd automatically whenever you run urxvtc and the daemon isn't running yet, use this script: @@ -60,7 +60,7 @@ re-run the command. Subsequent invocations of the script will re-use the existing daemon. - How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. + How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. The original rxvt and rxvt-unicode always export the variable "COLORTERM", so you can check and see if that is set. Note that several programs, JED, slrn, Midnight Commander automatically check this @@ -110,7 +110,7 @@ When you "--enable-everything" (which *is* unfair, as this involves xft and full locale/XIM support which are quite bloaty inside libX11 and my - libc), the two diverge, but not unreasnobaly so. + libc), the two diverge, but not unreasonably so. text data bss drs rss filename 163431 2152 24 20123 2060 rxvt --enable-everything @@ -164,7 +164,7 @@ libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) - /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) + /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) No large bloated libraries (of course, none were linked in statically), except maybe libX11 :) @@ -204,8 +204,8 @@ This requires XFT support, and the support of your X-server. If that doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't there yet, no matter what they claim. Rxvt-Unicode contains the - neccessary bugfixes and workarounds for Xft and Xlib to make it work, - but that doesn't mean that your WM has the required kludges in place. + necessary bugfixes and workarounds for Xft and Xlib to make it work, but + that doesn't mean that your WM has the required kludges in place. 4. Use xcompmgr and let it do the job: @@ -230,7 +230,7 @@ way is to ask for the character bounding box, which unfortunately is wrong in these cases). - It's not clear (to me at least), wether this is a bug in Xft, freetype, + It's not clear (to me at least), whether this is a bug in Xft, freetype, or the respective font. If you encounter this problem you might try using the "-lsp" option to give the font more height. If that doesn't work, you might be forced to use a different font. @@ -459,7 +459,7 @@ but when running a program that doesn't parse cursor movements or in some cases during rlogin sessions, it fails to detect this properly. - You can permamently switch this feature off by disabling the "readline" + You can permanently switch this feature off by disabling the "readline" extension: URxvt.perl-ext-common: default,-readline @@ -467,7 +467,7 @@ My numerical keypad acts weird and generates differing output? Some Debian GNUL/Linux users seem to have this problem, although no specific details were reported so far. It is possible that this is - caused by the wrong "TERM" setting, although the details of wether and + caused by the wrong "TERM" setting, although the details of whether and how this can happen are unknown, as "TERM=rxvt" should offer a compatible keymap. See the answer to the previous question, and please report if that helped. @@ -498,7 +498,7 @@ depressed. What's with the strange Backspace/Delete key behaviour? - Assuming that the physical Backspace key corresponds to the BackSpace + Assuming that the physical Backspace key corresponds to the Backspace keysym (not likely for Linux ... see the following question) there are two standard values that can be used for Backspace: "^H" and "^?". @@ -630,15 +630,15 @@ write. The selection stuff mainly makes the selection perl-error-message aware - and tells it to convert pelr error mssages into vi-commands to load the + and tells it to convert perl error messages into vi-commands to load the relevant file and go tot he error line number. URxvt.scrollstyle: plain URxvt.secondaryScroll: true As the documentation says: plain is the preferred scrollbar for the - author. The "secondaryScroll" confgiures urxvt to scroll in full-screen - apps, like screen, so lines scorlled out of screen end up in urxvt's + author. The "secondaryScroll" configures urxvt to scroll in full-screen + apps, like screen, so lines scrolled out of screen end up in urxvt's scrollback buffer. URxvt.background: #000000 @@ -699,12 +699,12 @@ urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true I wrote rxvt-unicode to be able to specify fonts exactly. So don't be - overwhelmed. A special note: the "9x15bold" mentioend above is actually + overwhelmed. A special note: the "9x15bold" mentioned above is actually the version from XFree-3.3, as XFree-4 replaced it by a totally different font (different glyphs for ";" and many other harmless characters), while the second font is actually the "9x15bold" from XFree4/XOrg. The bold version has less chars than the medium version, so - I use it for rare characters, too. Whene ditign sources with vim, I use + I use it for rare characters, too. When editing sources with vim, I use italic for comments and other stuff, which looks quite good with Bitstream Vera anti-aliased. @@ -765,8 +765,8 @@ URxvt.resource: value If you want to use another form (there are lots of different ways of - specifying resources), make sure you understand wether and why it works. - If unsure, use the form above. + specifying resources), make sure you understand whether and why it + works. If unsure, use the form above. When I log-in to another system it tells me about missing terminfo data? The terminal description used by rxvt-unicode is not as widely available @@ -774,13 +774,17 @@ arises). The correct solution for this problem is to install the terminfo, this - can be done like this (with ncurses' infocmp): + can be done like this (with ncurses' infocmp and works as user and + admin): REMOTE=remotesystem.domain - infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" + infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" ... or by installing rxvt-unicode normally on the remote system, + One some systems you might need to set $TERMINFO to the full path of + $HOME/.terminfo for this to work. + If you cannot or do not want to do this, then you can simply set "TERM=rxvt" or even "TERM=xterm", and live with the small number of problems arising, which includes wrong keymapping, less and different @@ -809,9 +813,9 @@ library (Fedora Core's bash is one example) and rely on a termcap entry for "rxvt-unicode". - You could use rxvt's termcap entry with resonable results in many cases. - You can also create a termcap entry by using terminfo's infocmp program - like this: + You could use rxvt's termcap entry with reasonable results in many + cases. You can also create a termcap entry by using terminfo's infocmp + program like this: infocmp -C rxvt-unicode @@ -840,7 +844,7 @@ Why does "ls" no longer have coloured output? The "ls" in the GNU coreutils unfortunately doesn't use terminfo to - decide wether a terminal has colour, but uses its own configuration + decide whether a terminal has colour, but uses its own configuration file. Needless to say, "rxvt-unicode" is not in its default file (among with most other terminals supporting colour). Either add: @@ -878,16 +882,16 @@ is subtly garbled, then you should check your locale settings. Rxvt-unicode must be started with the same "LC_CTYPE" setting as the - programs. Often rxvt-unicode is started in the "C" locale, while the - login script running within the rxvt-unicode window changes the locale - to something else, e.g. "en_GB.UTF-8". Needless to say, this is not - going to work. + programs running in it. Often rxvt-unicode is started in the "C" locale, + while the login script running within the rxvt-unicode window changes + the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this + is not going to work, and is the most common cause for problems. The best thing is to fix your startup environment, as you will likely run into other problems. If nothing works you can try this in your .profile. - printf '\33]701;%s\007' "$LC_CTYPE" + printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too If this doesn't work, then maybe you use a "LC_CTYPE" specification not supported on your systems. Some systems have a "locale" command which @@ -978,12 +982,12 @@ - Make sure the "XMODIFIERS" environment variable is set correctly when *starting* rxvt-unicode. When you want to use e.g. kinput2, it must be set to "@im=kinput2". - For scim, use "@im=SCIM". Youc an see what input method servers are + For scim, use "@im=SCIM". You can see what input method servers are running with this command: xprop -root XIM_SERVERS - + * My input method wants but I want UTF-8, what can I do? You can specify separate locales for the input method and the rest of @@ -1025,7 +1029,7 @@ I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? You should build one binary with the default options. configure now enables most useful options, and the trend goes to making them - runtime-switchable, too, so there is usually no drawback to enbaling + runtime-switchable, too, so there is usually no drawback to enabling them, except higher disk and possibly memory usage. The perl interpreter should be enabled, as important functionality (menus, selection, likely more in the future) depends on it. @@ -1067,10 +1071,10 @@ I am on FreeBSD and rxvt-unicode does not seem to work at all. Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in your compile environment, or an implementation that implements it, - wether it defines the symbol or not. "__STDC_ISO_10646__" requires that + whether it defines the symbol or not. "__STDC_ISO_10646__" requires that wchar_t is represented as unicode. - As you might have guessed, FreeBSD does neither define this symobl nor + As you might have guessed, FreeBSD does neither define this symbol nor does it support it. Instead, it uses its own internal representation of wchar_t. This is, of course, completely fine with respect to standards.