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

Comparing cvsroot/rxvt-unicode/README.FAQ (file contents):
Revision 1.70 by root, Fri Dec 26 22:52:22 2014 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 two big problems with Gentoo Linux: first, most if not all
     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?
     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
     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:

Diff Legend

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

Comparing cvsroot/rxvt-unicode/README.FAQ (file contents): Revision 1.70 by root, Fri Dec 26 22:52:22 2014 UTC vs. Revision 1.75 by root, Sun Nov 14 17:59:19 2021 UTC

Diff Legend

Comparing cvsroot/rxvt-unicode/README.FAQ (file contents):
Revision 1.70 by root, Fri Dec 26 22:52:22 2014 UTC vs.
Revision 1.75 by root, Sun Nov 14 17:59:19 2021 UTC