rxvt-unicode/doc/rxvtc.1.txt

NAME
    urxvtc - control the urxvtd daemon

SYNOPSIS
    urxvtc [same options as for urxvt]

DESCRIPTION
    This manpage describes the urxvtc client program. It connects to the
    urxvtd daemon and requests a new terminal window. It takes the same
    arguments as the urxvt program. The environment will also be respected.
    Currently, it always returns immediately after contacting the daemon.

OPTIONS
    All options that are valid for urxvt are valid for urxvtc, 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.

EXIT STATUS
    If everything went well, urxvtc 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 "urxvtd -f -q" and retrying the call to
    urxvtc, like this:

       #!/bin/sh
       urxvtc "$@"
       if [ $? -eq 2 ]; then
          urxvtd -q -o -f
          urxvtc "$@"
       fi

ENVIRONMENT
    All environment variables of the current process will be made available
    to the new instance, and will be interpreted as if urxvt were started
    directly.

    RXVT_SOCKET
        Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to
        create a listening socket and to contact the urxvtd, respectively.
        If the variable is missing, $HOME/.rxvt-unicode-*<nodename>* is
        used. The variable must specify the absolute path of the socket to
        create.

SEE ALSO
    urxvt(7), urxvtd(1)

Revision:	1.7
Committed:	Sat Oct 27 12:09:02 2007 UTC (16 years, 8 months ago) by root
Content type:	text/plain
Branch:	MAIN
CVS Tags:	rel-8_5a, rel-8_4, rel-8_6, rel-8_7
Changes since 1.6:	+19 -18 lines
Log Message:	* empty log message *
#	Content
1	NAME
2	urxvtc - control the urxvtd daemon
3
4	SYNOPSIS
5	urxvtc [same options as for urxvt]
6
7	DESCRIPTION
8	This manpage describes the urxvtc client program. It connects to the
9	urxvtd daemon and requests a new terminal window. It takes the same
10	arguments as the urxvt program. The environment will also be respected.
11	Currently, it always returns immediately after contacting the daemon.
12
13	OPTIONS
14	All options that are valid for urxvt are valid for urxvtc, too. Please
15	note that options are interpreted in the context of the daemon process.
16	However, as current working directory, process environment and any file
17	descriptor (e.g. for "-pty-fd") are preserved, this rarely makes a
18	difference.
19
20	EXIT STATUS
21	If everything went well, urxvtc returns with an exit status of 0. If
22	contacting the daemon fails, it exits with the exit status 2. In all
23	other error cases it returns with status 1.
24
25	This can be used to implement auto-starting behaviour, by checking for
26	an exit status of 2, running "urxvtd -f -q" and retrying the call to
27	urxvtc, like this:
28
29	#!/bin/sh
30	urxvtc "$@"
31	if [ $? -eq 2 ]; then
32	urxvtd -q -o -f
33	urxvtc "$@"
34	fi
35
36	ENVIRONMENT
37	All environment variables of the current process will be made available
38	to the new instance, and will be interpreted as if urxvt were started
39	directly.
40
41	RXVT_SOCKET
42	Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to
43	create a listening socket and to contact the urxvtd, respectively.
44	If the variable is missing, $HOME/.rxvt-unicode-<nodename> is
45	used. The variable must specify the absolute path of the socket to
46	create.
47
48	SEE ALSO
49	urxvt(7), urxvtd(1)
50