urxvt256c-mlc (1) - Linux Manuals

urxvt256c-mlc: control the urxvt256c-mld daemon


urxvt256c-mlc - control the urxvt256c-mld daemon


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


This manpage describes the urxvt256c-mlc client program. It connects to the urxvt256c-mld daemon and requests a new terminal window. It takes the same arguments as the urxvt256c-ml program. The environment will also be respected. Currently, it always returns immediately after contacting the daemon.


If the first option is -k, urxvt256c-mlc tries to kill the daemon process and returns.

All options that are valid for urxvt256c-ml are valid for urxvt256c-mlc, too. Please note that options are interpreted in the context of the daemon process. However, as current working directory, process environment and any file descriptor (e.g. for "-pty-fd") are preserved, this rarely makes a difference.


If everything went well, urxvt256c-mlc returns with an exit status of 0. If contacting the daemon fails, it exits with the exit status 2. In all other error cases it returns with status 1.

This can be used to implement auto-starting behaviour, by checking for an exit status of 2, running "urxvt256c-mld -f -q" and retrying the call to urxvt256c-mlc, like this:

   urxvt256c-mlc "$@"
   if [ $? -eq 2 ]; then
      urxvt256c-mld -q -o -f
      urxvt256c-mlc "$@"


All environment variables of the current process will be made available to the new instance, and will be interpreted as if urxvt256c-ml were started directly.
Both urxvt256c-mlc and urxvt256c-mld use the environment variable RXVT_SOCKET to create a listening socket and to contact the urxvt256c-mld, respectively. If the variable is missing, $HOME/.urxvt/urxvtd-<nodename> is used. The variable must specify the absolute path of the socket to create.


urxvt256c-ml(7), urxvt256c-mld(1)