rxvt-unicode/doc/rxvtc.1.txt

NAME
    rxvtc - control the rxvtd daemon

SYNOPSIS
    rxvtc [same options as for rxvt]

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

OPTIONS
    All options that are valid for rxvt are valid for rxvtc, too. Please
    note that all options are currently interpreted in the context of the
    daemon process, which makes a difference for options that specify a file
    descriptor (such as -pty-fd).

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

    RXVT_SOCKET
        Both rxvtc and rxvtd use the environment variable RXVT_SOCKET to
        create a listening socket and to contact the rxvtd, 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
    rxvt(7), rxvtd(1)

Revision:	1.2
Committed:	Sat Dec 17 20:55:45 2005 UTC (18 years, 6 months ago) by root
Content type:	text/plain
Branch:	MAIN
CVS Tags:	rel-7_3, rel-7_2, rel-7_1, rel-7_0, rel-7_5, rel-7_4, rel-6_2, rel-6_3, rel-5_9, rel-7_3a, rel-6_0, rel-6_1
Changes since 1.1:	+1 -0 lines
Log Message:	* empty log message *
#	Content
1	NAME
2	rxvtc - control the rxvtd daemon
3
4	SYNOPSIS
5	rxvtc [same options as for rxvt]
6
7	DESCRIPTION
8	This manpage describes the rxvtc client program. It connects to the
9	rxvtd daemon and requests a new terminal window. It takes the same
10	arguments as the rxvt 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 rxvt are valid for rxvtc, too. Please
15	note that all options are currently interpreted in the context of the
16	daemon process, which makes a difference for options that specify a file
17	descriptor (such as -pty-fd).
18
19	ENVIRONMENT
20	All environment variables of the current process will be made available
21	to the new instance, and will be interpreted as if rxvt were started
22	directly.
23
24	RXVT_SOCKET
25	Both rxvtc and rxvtd use the environment variable RXVT_SOCKET to
26	create a listening socket and to contact the rxvtd, respectively. If
27	the variable is missing, $HOME/.rxvt-unicode-<nodename> is used.
28	The variable must specify the absolute path of the socket to create.
29
30	SEE ALSO
31	rxvt(7), rxvtd(1)
32