… | |
… | |
127 | .\} |
127 | .\} |
128 | .rm #[ #] #H #V #F C |
128 | .rm #[ #] #H #V #F C |
129 | .\" ======================================================================== |
129 | .\" ======================================================================== |
130 | .\" |
130 | .\" |
131 | .IX Title "rxvt 7" |
131 | .IX Title "rxvt 7" |
132 | .TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE" |
132 | .TH rxvt 7 "2006-02-02" "7.5" "RXVT-UNICODE" |
133 | .SH "NAME" |
133 | .SH "NAME" |
134 | RXVT REFERENCE \- FAQ, command sequences and other background information |
134 | RXVT REFERENCE \- FAQ, command sequences and other background information |
135 | .SH "SYNOPSIS" |
135 | .SH "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
137 | .Vb 2 |
137 | .Vb 2 |
… | |
… | |
214 | \fIHow can I start @@URXVT_NAME@@d in a race-free way?\fR |
214 | \fIHow can I start @@URXVT_NAME@@d in a race-free way?\fR |
215 | .IX Subsection "How can I start @@URXVT_NAME@@d in a race-free way?" |
215 | .IX Subsection "How can I start @@URXVT_NAME@@d in a race-free way?" |
216 | .PP |
216 | .PP |
217 | Try \f(CW\*(C`@@URXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@URXVT_NAME@@d to open the |
217 | Try \f(CW\*(C`@@URXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@URXVT_NAME@@d to open the |
218 | display, create the listening socket and then fork. |
218 | display, create the listening socket and then fork. |
|
|
219 | .PP |
|
|
220 | \fIHow can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?\fR |
|
|
221 | .IX Subsection "How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?" |
|
|
222 | .PP |
|
|
223 | If you want to start @@URXVT_NAME@@d automatically whenever you run |
|
|
224 | @@URXVT_NAME@@c and the daemon isn't running yet, use this script: |
|
|
225 | .PP |
|
|
226 | .Vb 6 |
|
|
227 | \& #!/bin/sh |
|
|
228 | \& @@URXVT_NAME@@c "$@" |
|
|
229 | \& if [ $? -eq 2 ]; then |
|
|
230 | \& @@URXVT_NAME@@d -q -o -f |
|
|
231 | \& @@URXVT_NAME@@c "$@" |
|
|
232 | \& fi |
|
|
233 | .Ve |
|
|
234 | .PP |
|
|
235 | This tries to create a new terminal, and if fails with exit status 2, |
|
|
236 | meaning it couldn't connect to the daemon, it will start the daemon and |
|
|
237 | re-run the command. Subsequent invocations of the script will re-use the |
|
|
238 | existing daemon. |
219 | .PP |
239 | .PP |
220 | \fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR |
240 | \fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR |
221 | .IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
241 | .IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
222 | .PP |
242 | .PP |
223 | The original rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", |
243 | The original rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", |