1urxvt-ml(1) RXVT-UNICODE urxvt-ml(1)
2
3
4
6 urxvt-mlc - control the urxvt-mld daemon
7
9 urxvt-mlc [same options as for urxvt-ml]
10
12 This manpage describes the urxvt-mlc client program. It connects to the
13 urxvt-mld daemon and requests a new terminal window. It takes the same
14 arguments as the urxvt-ml program. The environment will also be
15 respected. Currently, it always returns immediately after contacting
16 the daemon.
17
19 All options that are valid for urxvt-ml are valid for urxvt-mlc, too.
20 Please note that options are interpreted in the context of the daemon
21 process. However, as current working directory, process environment and
22 any file descriptor (e.g. for "-pty-fd") are preserved, this rarely
23 makes a difference.
24
26 If everything went well, urxvt-mlc returns with an exit status of 0.
27 If contacting the daemon fails, it exits with the exit status 2. In all
28 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 "urxvt-mld -f -q" and retrying the call to
32 urxvt-mlc, like this:
33
34 #!/bin/sh
35 urxvt-mlc "$@"
36 if [ $? -eq 2 ]; then
37 urxvt-mld -q -o -f
38 urxvt-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 urxvt-ml were
44 started directly.
45
46 RXVT_SOCKET
47 Both urxvt-mlc and urxvt-mld use the environment variable
48 RXVT_SOCKET to create a listening socket and to contact the urxvt-
49 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 urxvt-ml(7), urxvt-mld(1)
55
56
57
589.12 2011-06-29 urxvt-ml(1)