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