| … | |
… | |
| 67 | |
67 | |
| 68 | This tries to create a new terminal, and if fails with exit status 2, |
68 | This tries to create a new terminal, and if fails with exit status 2, |
| 69 | meaning it couldn't connect to the daemon, it will start the daemon and |
69 | meaning it couldn't connect to the daemon, it will start the daemon and |
| 70 | re-run the command. Subsequent invocations of the script will re-use the |
70 | re-run the command. Subsequent invocations of the script will re-use the |
| 71 | existing daemon. |
71 | existing daemon. |
|
|
72 | |
|
|
73 | Another option is to use systemd socket-based activation (see |
|
|
74 | systemd.socket(5)). Here is an example of a service unit file and of a |
|
|
75 | socket unit file for the default socket path: |
|
|
76 | |
|
|
77 | urxvtd.service |
|
|
78 | [Unit] |
|
|
79 | Description=urxvt terminal daemon |
|
|
80 | Requires=urxvtd.socket |
|
|
81 | |
|
|
82 | [Service] |
|
|
83 | ExecStart=/usr/bin/urxvtd -o |
|
|
84 | |
|
|
85 | urxvtd.socket |
|
|
86 | [Unit] |
|
|
87 | Description=urxvt terminal daemon socket |
|
|
88 | |
|
|
89 | [Socket] |
|
|
90 | ListenStream=%h/.urxvt/urxvtd-%H |
|
|
91 | |
|
|
92 | [Install] |
|
|
93 | WantedBy=sockets.target |
| 72 | |
94 | |
| 73 | How do I distinguish whether I'm running rxvt-unicode or a regular |
95 | How do I distinguish whether I'm running rxvt-unicode or a regular |
| 74 | xterm? I need this to decide about setting colours etc. |
96 | xterm? I need this to decide about setting colours etc. |
| 75 | The original rxvt and rxvt-unicode always export the variable |
97 | The original rxvt and rxvt-unicode always export the variable |
| 76 | "COLORTERM", so you can check and see if that is set. Note that several |
98 | "COLORTERM", so you can check and see if that is set. Note that several |
| … | |
… | |
| 482 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
504 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
| 483 | |
505 | |
| 484 | This will keep the default extensions, but disable the two popup |
506 | This will keep the default extensions, but disable the two popup |
| 485 | extensions. Some extensions can also be configured, for example, |
507 | extensions. Some extensions can also be configured, for example, |
| 486 | scrollback search mode is triggered by M-s. You can move it to any other |
508 | scrollback search mode is triggered by M-s. You can move it to any other |
| 487 | combination either by setting the searchable-scrollback resource: |
509 | combination by adding a keysym resource that binds the desired |
|
|
510 | combination to the "start" action of "searchable-scrollback" and another |
|
|
511 | one that binds M-s to the "builtin:" action: |
| 488 | |
512 | |
| 489 | URxvt.searchable-scrollback: CM-s |
513 | URxvt.keysym.CM-s: searchable-scrollback:start |
|
|
514 | URxvt.keysym.M-s: builtin: |
| 490 | |
515 | |
| 491 | The cursor moves when selecting text in the current input line, how do I switch this off? |
516 | The cursor moves when selecting text in the current input line, how do I switch this off? |
| 492 | See next entry. |
517 | See next entry. |
| 493 | |
518 | |
| 494 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
519 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
| … | |
… | |
| 615 | time into customising your terminal. To get you started, here is the |
640 | time into customising your terminal. To get you started, here is the |
| 616 | author's .Xdefaults entries, with comments on what they do. It's |
641 | author's .Xdefaults entries, with comments on what they do. It's |
| 617 | certainly not *typical*, but what's typical... |
642 | certainly not *typical*, but what's typical... |
| 618 | |
643 | |
| 619 | URxvt.cutchars: "()*,<>[]{}|' |
644 | URxvt.cutchars: "()*,<>[]{}|' |
| 620 | URxvt.print-pipe: cat >/tmp/xxx |
645 | URxvt.print-pipe: cat >/some/path |
| 621 | |
646 | |
| 622 | These are just for testing stuff. |
647 | These are just for testing stuff. |
| 623 | |
648 | |
| 624 | URxvt.imLocale: ja_JP.UTF-8 |
649 | URxvt.imLocale: ja_JP.UTF-8 |
| 625 | URxvt.preeditType: OnTheSpot,None |
650 | URxvt.preeditType: OnTheSpot,None |
| … | |
… | |
| 825 | See next entry. |
850 | See next entry. |
| 826 | |
851 | |
| 827 | I need a termcap file entry. |
852 | I need a termcap file entry. |
| 828 | One reason you might want this is that some distributions or operating |
853 | One reason you might want this is that some distributions or operating |
| 829 | systems still compile some programs using the long-obsoleted termcap |
854 | systems still compile some programs using the long-obsoleted termcap |
| 830 | library (Fedora Core's bash is one example) and rely on a termcap entry |
855 | library (Fedora's bash is one example) and rely on a termcap entry for |
| 831 | for "rxvt-unicode". |
856 | "rxvt-unicode". |
| 832 | |
857 | |
| 833 | You could use rxvt's termcap entry with reasonable results in many |
858 | You could use rxvt's termcap entry with reasonable results in many |
| 834 | cases. You can also create a termcap entry by using terminfo's infocmp |
859 | cases. You can also create a termcap entry by using terminfo's infocmp |
| 835 | program like this: |
860 | program like this: |
| 836 | |
861 | |
