| … | |
… | |
| 62 | worse, as rxvt-unicode then uses 8 bytes per screen cell. |
62 | worse, as rxvt-unicode then uses 8 bytes per screen cell. |
| 63 | |
63 | |
| 64 | How can I start urxvtd in a race-free way? |
64 | How can I start urxvtd in a race-free way? |
| 65 | Try "urxvtd -f -o", which tells urxvtd to open the display, create the |
65 | Try "urxvtd -f -o", which tells urxvtd to open the display, create the |
| 66 | listening socket and then fork. |
66 | listening socket and then fork. |
|
|
67 | |
|
|
68 | How can I start urxvtd automatically when I run URXVT_NAME@@c? |
|
|
69 | If you want to start urxvtd automatically whenever you run urxvtc and |
|
|
70 | the daemon isn't running yet, use this script: |
|
|
71 | |
|
|
72 | #!/bin/sh |
|
|
73 | urxvtc "$@" |
|
|
74 | if [ $? -eq 2 ]; then |
|
|
75 | urxvtd -q -o -f |
|
|
76 | urxvtc "$@" |
|
|
77 | fi |
|
|
78 | |
|
|
79 | This tries to create a new terminal, and if fails with exit status 2, |
|
|
80 | meaning it couldn't connect to the daemon, it will start the daemon and |
|
|
81 | re-run the command. Subsequent invocations of the script will re-use the |
|
|
82 | existing daemon. |
| 67 | |
83 | |
| 68 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
84 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
| 69 | The original rxvt and rxvt-unicode always export the variable |
85 | The original rxvt and rxvt-unicode always export the variable |
| 70 | "COLORTERM", so you can check and see if that is set. Note that several |
86 | "COLORTERM", so you can check and see if that is set. Note that several |
| 71 | programs, JED, slrn, Midnight Commander automatically check this |
87 | programs, JED, slrn, Midnight Commander automatically check this |
