wmii/cmd/wmiir.1

72 lines
1.4 KiB
Groff
Raw Normal View History

2005-11-18 18:54:58 +03:00
.TH WMIR 1 wmii-3
.SH NAME
wmiir \- window manager improved 2 remote
2005-11-18 18:54:58 +03:00
.SH SYNOPSIS
.B wmiir
2005-11-18 18:54:58 +03:00
.RB [ \-s
.IR socketfile ]
.I action
.I action_arg
[...]
.br
.B wmiir
2005-11-18 18:54:58 +03:00
.RB [ \-s
.IR socketfile ]
.B \-f
.br
.B wmiir
2005-11-18 18:54:58 +03:00
.B \-v
.SH DESCRIPTION
.SS Overview
.B wmiir
2005-11-18 18:54:58 +03:00
is a client to access wmi* fileservers for the command line and
scripts. It can be used to configure wmii(1).
.SS Options
.TP
.BI \-s " socketfile"
lets you specify the socketfile to which
.B wmiir
2005-11-18 18:54:58 +03:00
a connection will be established. If the environment variable
.B WMIR_SOCKET
is set and points to a socket file, wmiir will use that file, if this
2005-11-18 18:54:58 +03:00
option is not supplied.
.TP
.B \-f
reads from stdin, useful for interactive wmiir sessions or for
2005-11-18 18:54:58 +03:00
scripts that write/read a bunch of data, because this speeds things up
due to missing process creation/destruction, ie., a hack.
.TP
.B \-v
prints version information to stderr, then exits.
.TP
The syntax of the actions is as follows:
.TP
.B create <path/file> [<value>]
creates file
.TP
.B write <file> <value>
writes value to a file
.TP
.B read <path/file>
reads file or directory contents
.TP
.B remove <path/file>
removes file or directory tree
.SH ENVIRONMENT
.TP
WMIR_SOCKET
See above.
.SH EXAMPLES
.TP
$ wmiir read /
2005-11-18 18:54:58 +03:00
This gives you an idea about what the wmii filesystem currently looks like.
.TP
$ wmiir write /wm/ctl quit
2005-11-18 18:54:58 +03:00
.SH SEE ALSO
.BR wmiibar (1),
.BR wmiifs (1),
2005-11-18 18:54:58 +03:00
.BR wmii (1),
.BR wmiiwm (1),
.BR wmiikeys (1),
.BR wmiimenu (1)