1urxvt256c-ml(1)                  RXVT-UNICODE                  urxvt256c-ml(1)
2
3
4

NAME

6       urxvt256c-mlc - control the urxvt256c-mld daemon
7

SYNOPSIS

9       urxvt256c-mlc [same options as for urxvt256c-ml]
10

DESCRIPTION

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

OPTIONS

19       If the first option is -k, urxvt256c-mlc tries to kill the daemon
20       process and returns.
21
22       All options that are valid for urxvt256c-ml are valid for urxvt256c-
23       mlc, too. Please note that options are interpreted in the context of
24       the daemon process. However, as current working directory, process
25       environment and any file descriptor (e.g. for "-pty-fd") are preserved,
26       this rarely makes a difference.
27

EXIT STATUS

29       If everything went well, urxvt256c-mlc returns with an exit status of
30       0.  If contacting the daemon fails, it exits with the exit status 2. In
31       all 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 "urxvt256c-mld -f -q" and retrying the
35       call to urxvt256c-mlc, like this:
36
37          #!/bin/sh
38          urxvt256c-mlc "$@"
39          if [ $? -eq 2 ]; then
40             urxvt256c-mld -q -o -f
41             urxvt256c-mlc "$@"
42          fi
43

ENVIRONMENT

45       All environment variables of the current process will be made available
46       to the new instance, and will be interpreted as if urxvt256c-ml were
47       started directly.
48
49       RXVT_SOCKET
50           Both urxvt256c-mlc and urxvt256c-mld use the environment variable
51           RXVT_SOCKET to create a listening socket and to contact the
52           urxvt256c-mld, 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

SEE ALSO

57       urxvt256c-ml(7), urxvt256c-mld(1)
58
59
60
619.22                              2016-01-23                   urxvt256c-ml(1)
Impressum