1urxvt256c(1) RXVT-UNICODE urxvt256c(1)
2
3
4
6 urxvt256cc - control the urxvt256cd daemon
7
9 urxvt256cc [same options as for urxvt256c]
10
12 This manpage describes the urxvt256cc client program. It connects to
13 the urxvt256cd daemon and requests a new terminal window. It takes the
14 same arguments as the urxvt256c program. The environment will also be
15 respected. Currently, it always returns immediately after contacting
16 the daemon.
17
19 If the first option is -k, urxvt256cc tries to kill the daemon process
20 and returns.
21
22 All options that are valid for urxvt256c are valid for urxvt256cc, too.
23 Please note that options are interpreted in the context of the daemon
24 process. However, as current working directory, process environment and
25 any file descriptor (e.g. for "-pty-fd") are preserved, this rarely
26 makes a difference.
27
29 If everything went well, urxvt256cc returns with an exit status of 0.
30 If contacting the daemon fails, it exits with the exit status 2. In all
31 other error cases it returns with status 1.
32
33 This can be used to implement auto-starting behaviour, by checking for
34 an exit status of 2, running "urxvt256cd -f -q" and retrying the call
35 to urxvt256cc, like this:
36
37 #!/bin/sh
38 urxvt256cc "$@"
39 if [ $? -eq 2 ]; then
40 urxvt256cd -q -o -f
41 urxvt256cc "$@"
42 fi
43
45 All environment variables of the current process will be made available
46 to the new instance, and will be interpreted as if urxvt256c were
47 started directly.
48
49 RXVT_SOCKET
50 Both urxvt256cc and urxvt256cd use the environment variable
51 RXVT_SOCKET to create a listening socket and to contact the
52 urxvt256cd, respectively. If the variable is missing,
53 $HOME/.urxvt/urxvtd-<nodename> is used. The variable must specify
54 the absolute path of the socket to create.
55
57 urxvt256c(7), urxvt256cd(1)
58
59
60
619.22 2016-01-23 urxvt256c(1)