3 Michael Stapelberg <michael@i3wm.org>
8 i3-msg - send messages to i3 window manager
12 i3-msg [-q] [-v] [-h] [-s socket] [-t type] [message]
17 Only send ipc message and suppress the output of the response.
20 Display version number and exit.
23 Display a short help-message and exit.
25 *-s, --socket* 'sock_path'::
26 i3-msg will use the environment variable I3SOCK or the socket path
27 given here. If both fail, it will try to get the socket information
28 from the root window and then try /tmp/i3-ipc.sock before exiting
32 Send ipc message, see below. This option defaults to "command".
35 Send ipc message, see below.
40 The payload of the message is a command for i3 (like the commands you can bind
41 to keys in the configuration file) and will be executed directly after
45 Gets the current workspaces. The reply will be a JSON-encoded list of
49 Gets the current outputs. The reply will be a JSON-encoded list of outputs (see
50 the reply section of docs/ipc, e.g. at
51 http://i3wm.org/docs/ipc.html#_receiving_replies_from_i3).
54 Gets the layout tree. i3 uses a tree as data structure which includes every
55 container. The reply will be the JSON-encoded tree.
58 Gets a list of marks (identifiers for containers to easily jump to them later).
59 The reply will be a JSON-encoded list of window marks.
62 Gets the configuration (as JSON map) of the workspace bar with the given ID. If
63 no ID is provided, an array with all configured bar IDs is returned instead.
66 Gets a list of configured binding modes.
69 Gets the version of i3. The reply will be a JSON-encoded dictionary with the
70 major, minor, patch and human-readable version.
74 i3-msg is a sample implementation for a client using the unix socket IPC
79 ------------------------------------------------
80 # Use 1-px border for current client
81 i3-msg "border 1pixel"
83 # You can leave out the quotes
86 # Dump the layout tree
88 ------------------------------------------------
94 If no ipc-socket is specified on the commandline, this variable is used
95 to determine the path, at which the unix domain socket is expected, on which
104 Michael Stapelberg and contributors