[ViewVC] Diff of: cvs/rxvt-unicode/README.FAQ

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.67 by root, Sun Sep 9 12:21:25 2012 UTC vs.
Revision 1.75 by root, Sun Nov 14 17:59:19 2021 UTC

 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS
   Meta, Features & Commandline Issues
    My question isn't answered here, can I ask a human?
-    Before sending me mail, you could go to IRC: "irc.freenode.net", channel
+    Before sending me mail, you could go to IRC: "irc.libera.chat", channel
     "#rxvt-unicode" has some rxvt-unicode enthusiasts that might be
     interested in learning about new and exciting problems (but not FAQs :).
    I use Gentoo, and I have a problem...
-    There are three big problems with Gentoo Linux: first of all, most if
+    There are two big problems with Gentoo Linux: first, most if not all
-    not all Gentoo systems are completely broken (missing or mismatched
+    Gentoo systems are completely broken (missing or mismatched header
-    header files, broken compiler etc. are just the tip of the iceberg);
+    files, broken compiler etc. are just the tip of the iceberg); secondly,
-    secondly, the Gentoo maintainer thinks it is a good idea to add broken
+    it should be called Gentoo GNU/Linux.
-    patches to the code; and lastly, it should be called Gentoo GNU/Linux.
     For these reasons, it is impossible to support rxvt-unicode on Gentoo.
     Problems appearing on Gentoo systems will usually simply be ignored
     unless they can be reproduced on non-Gentoo systems.
     This tries to create a new terminal, and if fails with exit status 2,
     meaning it couldn't connect to the daemon, it will start the daemon and
     re-run the command. Subsequent invocations of the script will re-use the
     existing daemon.
+    Another option is to use systemd socket-based activation (see
+    systemd.socket(5)). Here is an example of a service unit file and of a
+    socket unit file for the default socket path:
+    urxvtd.service
+          [Unit]
+          Description=urxvt terminal daemon
+          Requires=urxvtd.socket
+          [Service]
+          ExecStart=/usr/bin/urxvtd -o
+    urxvtd.socket
+          [Unit]
+          Description=urxvt terminal daemon socket
+          [Socket]
+          ListenStream=%h/.urxvt/urxvtd-%H
+          [Install]
+          WantedBy=sockets.target
    How do I distinguish whether I'm running rxvt-unicode or a regular
 xterm? I need this to decide about setting colours 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
     rite of passage: ... and you failed.
     Here are four ways to get transparency. Do read the manpage and option
     descriptions for the programs mentioned and rxvt-unicode. Really, do it!
-    1. Use transparent mode:
+    1. Use pseudo-transparency:
        Esetroot wallpaper.jpg
        urxvt -tr -tint red -sh 40
     That works. If you think it doesn't, you lack transparency and tinting
     3. Use an ARGB visual:
        urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
     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
+    doesn't work for you, find a working composite manager or window
-    there yet, no matter what they claim. Rxvt-Unicode contains the
+    manager, both are required to support ARGB visuals for client windows.
-    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:
       xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
             -set _NET_WM_WINDOW_OPACITY 0xc0000000
     We are working on it, in the meantime, as a workaround, use something
     like:
        urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...'
+   Why is the cursor now blinking in emacs/vi/...?
+    This is likely caused by your editor/program's use of the "cvvis"
+    terminfo capability. Emacs uses it by default, as well as some versions
+    of vi and possibly other programs.
+    In emacs, you can switch that off by adding this to your ".emacs" file:
+       (setq visible-cursor nil)
+    For other programs, if they do not have an option, your have to remove
+    the "cvvis" capability from the terminfo description.
+    When urxvt first added the blinking cursor option, it didn't add a
+    "cvvis" capability, which served no purpose before. Version 9.21
+    introduced "cvvis" (and the ability to control blinking independent of
+    cursor shape) for compatibility with other terminals, which
+    traditionally use a blinking cursor for "cvvis". This also reflects the
+    intent of programs such as emacs, who expect "cvvis" to enable a
+    blinking cursor.
   Keyboard, Mouse & User Interaction
    The new selection selects pieces that are too big, how can I select single words?
     If you want to select e.g. alphanumeric words, you can use the following
     setting:
        URxvt.perl-ext-common: default,-selection-popup,-option-popup
     This will keep the default extensions, but disable the two popup
     extensions. Some extensions can also be configured, for example,
     scrollback search mode is triggered by M-s. You can move it to any other
-    combination either by setting the searchable-scrollback resource:
+    combination by adding a keysym resource that binds the desired
+    combination to the "start" action of "searchable-scrollback" and another
+    one that binds M-s to the "builtin:" action:
-       URxvt.searchable-scrollback: CM-s
+       URxvt.keysym.CM-s: searchable-scrollback:start
+       URxvt.keysym.M-s: builtin:
    The cursor moves when selecting text in the current input line, how do I switch this off?
     See next entry.
    During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?
     You can permanently switch this feature off by disabling the "readline"
     extension:
        URxvt.perl-ext-common: default,-readline
-   My numerical keypad acts weird and generates differing output?
+   My numeric keypad acts weird and generates differing output?
-    Some Debian GNUL/Linux users seem to have this problem, although no
+    Some Debian GNU/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 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.
    My Compose (Multi_key) key is no longer working.
     The most common causes for this are that either your locale is not set
-    correctly, or you specified a preeditStyle that is not supported by your
+    correctly, or you specified a preeditType that is not supported by your
     input method. For example, if you specified OverTheSpot and your input
     method (e.g. the default input method handling Compose keys) does not
     support this (for instance because it is not visual), then rxvt-unicode
     will continue without an input method.
-    In this case either do not specify a preeditStyle or specify more than
+    In this case either do not specify a preeditType or specify more than
     one pre-edit style, such as OverTheSpot,Root,None.
     If it still doesn't work, then maybe your input method doesn't support
     compose sequences - to fall back to the built-in one, make sure you
     don't specify an input method via "-im" or "XMODIFIERS".
     time into customising your terminal. To get you started, here is the
     author's .Xdefaults entries, with comments on what they do. It's
     certainly not *typical*, but what's typical...
        URxvt.cutchars: "()*,<>[]{}|'
-       URxvt.print-pipe: cat >/tmp/xxx
+       URxvt.print-pipe: cat >/some/path
     These are just for testing stuff.
        URxvt.imLocale: ja_JP.UTF-8
        URxvt.preeditType: OnTheSpot,None
        REMOTE=remotesystem.domain
        infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
     One some systems you might need to set $TERMINFO to the full path of
-    $HOME/.terminfo for this to work. Debian systems have a broken tic which
+    $HOME/.terminfo for this to work.
-    will not be able to overwrite the existing rxvt-unicode terminfo entry -
-    you might have to manually delete all traces of rxvt-unicode* from
-    /etc/terminfo.
     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
     colours and some refresh errors in fullscreen applications. It's a nice
     See next entry.
    I need a termcap file entry.
     One reason you might want this is that some distributions or operating
     systems still compile some programs using the long-obsoleted termcap
-    library (Fedora Core's bash is one example) and rely on a termcap entry
+    library (Fedora's bash is one example) and rely on a termcap entry for
-    for "rxvt-unicode".
+    "rxvt-unicode".
     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:
    Why doesn't vim/emacs etc. make use of italic?
     See next entry.
    Why are the secondary screen-related options not working properly?
     Make sure you are using "TERM=rxvt-unicode". Some pre-packaged
-    distributions (most notably Debian GNU/Linux) break rxvt-unicode by
+    distributions break rxvt-unicode by setting "TERM" to "rxvt", which
-    setting "TERM" to "rxvt", which doesn't have these extra features.
+    doesn't have these extra features. Unfortunately, some of these
-    Unfortunately, some of these (most notably, again, Debian GNU/Linux)
     furthermore fail to even install the "rxvt-unicode" terminfo file, so
     you will need to install it on your own (See the question When I log-in
     to another system it tells me about missing terminfo data? on how to do
     this).
         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 <some encoding> but I want UTF-8, what can I do?
     You can specify separate locales for the input method and the rest of
     the terminal, using the resource "imlocale":
        URxvt.imlocale: ja_JP.EUC-JP
     cannot be completely avoided even if both sides cooperate.
     So the only workaround is not to kill your Input Method Servers.
   Operating Systems / Package Maintaining
-   I am using Debian GNU/Linux and have a problem...
-    The Debian GNU/Linux package of rxvt-unicode in sarge contains large
-    patches that considerably change the behaviour of rxvt-unicode (but
-    unfortunately this notice has been removed). Before reporting a bug to
-    the original rxvt-unicode author please download and install the genuine
-    version (<http://software.schmorp.de/pkg/rxvt-unicode.html>) and try to
-    reproduce the problem. If you cannot, chances are that the problems are
-    specific to Debian GNU/Linux, in which case it should be reported via
-    the Debian Bug Tracking System (use "reportbug" to report the bug).
-    For other problems that also affect the Debian package, you can and
-    probably should use the Debian BTS, too, because, after all, it's also a
-    bug in the Debian version and it serves as a reminder for other users
-    that might encounter the same issue.
    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 enabling
     them, except higher disk and possibly memory usage. The perl interpreter

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing rxvt-unicode/README.FAQ (file contents): Revision 1.67 by root, Sun Sep 9 12:21:25 2012 UTC vs. Revision 1.75 by root, Sun Nov 14 17:59:19 2021 UTC

Diff Legend

Comparing rxvt-unicode/README.FAQ (file contents):
Revision 1.67 by root, Sun Sep 9 12:21:25 2012 UTC vs.
Revision 1.75 by root, Sun Nov 14 17:59:19 2021 UTC