2009-08-24 12:22:42 +02:00
|
|
|
i3-msg(1)
|
|
|
|
|
=========
|
2012-08-05 14:29:19 +02:00
|
|
|
Michael Stapelberg <michael@i3wm.org>
|
|
|
|
|
v4.2, August 2012
|
2009-08-24 12:22:42 +02:00
|
|
|
|
|
|
|
|
== NAME
|
|
|
|
|
|
2010-03-21 01:50:10 +01:00
|
|
|
i3-msg - send messages to i3 window manager
|
2009-08-24 12:22:42 +02:00
|
|
|
|
|
|
|
|
== SYNOPSIS
|
|
|
|
|
|
2012-01-27 23:39:51 +01:00
|
|
|
i3-msg [-t type] [message]
|
|
|
|
|
|
|
|
|
|
== IPC MESSAGE TYPES
|
|
|
|
|
|
|
|
|
|
command::
|
|
|
|
|
The payload of the message is a command for i3 (like the commands you can bind
|
|
|
|
|
to keys in the configuration file) and will be executed directly after
|
|
|
|
|
receiving it.
|
|
|
|
|
|
|
|
|
|
get_workspaces::
|
|
|
|
|
Gets the current workspaces. The reply will be a JSON-encoded list of
|
|
|
|
|
workspaces.
|
|
|
|
|
|
|
|
|
|
get_outputs::
|
|
|
|
|
Gets the current outputs. The reply will be a JSON-encoded list of outputs (see
|
2012-10-06 22:27:57 +02:00
|
|
|
the reply section of docs/ipc, e.g. at
|
|
|
|
|
http://i3wm.org/docs/ipc.html#_receiving_replies_from_i3).
|
2012-01-27 23:39:51 +01:00
|
|
|
|
|
|
|
|
get_tree::
|
|
|
|
|
Gets the layout tree. i3 uses a tree as data structure which includes every
|
|
|
|
|
container. The reply will be the JSON-encoded tree.
|
|
|
|
|
|
|
|
|
|
get_marks::
|
|
|
|
|
Gets a list of marks (identifiers for containers to easily jump to them later).
|
|
|
|
|
The reply will be a JSON-encoded list of window marks.
|
|
|
|
|
|
|
|
|
|
get_bar_config::
|
|
|
|
|
Gets the configuration (as JSON map) of the workspace bar with the given ID. If
|
|
|
|
|
no ID is provided, an array with all configured bar IDs is returned instead.
|
|
|
|
|
|
2012-08-05 14:29:19 +02:00
|
|
|
get_version::
|
|
|
|
|
Gets the version of i3. The reply will be a JSON-encoded dictionary with the
|
|
|
|
|
major, minor, patch and human-readable version.
|
2009-08-24 12:22:42 +02:00
|
|
|
|
|
|
|
|
== DESCRIPTION
|
|
|
|
|
|
|
|
|
|
i3-msg is a sample implementation for a client using the unix socket IPC
|
2012-01-27 23:39:51 +01:00
|
|
|
interface to i3.
|
2009-08-24 12:22:42 +02:00
|
|
|
|
2012-01-27 23:39:51 +01:00
|
|
|
== EXAMPLES
|
2009-08-24 12:22:42 +02:00
|
|
|
|
|
|
|
|
------------------------------------------------
|
2012-01-27 23:39:51 +01:00
|
|
|
# Use 1-px border for current client
|
|
|
|
|
i3-msg "border 1pixel"
|
|
|
|
|
|
|
|
|
|
# You can leave out the quotes
|
|
|
|
|
i3-msg border normal
|
|
|
|
|
|
|
|
|
|
# Dump the layout tree
|
|
|
|
|
i3-msg -t get_tree
|
2009-08-24 12:22:42 +02:00
|
|
|
------------------------------------------------
|
|
|
|
|
|
2011-01-11 04:39:48 +01:00
|
|
|
== ENVIRONMENT
|
|
|
|
|
|
|
|
|
|
=== I3SOCK
|
|
|
|
|
|
|
|
|
|
If no ipc-socket is specified on the commandline, this variable is used
|
|
|
|
|
to determine the path, at wich the unix domain socket is expected, on which
|
|
|
|
|
to connect to i3.
|
|
|
|
|
|
2009-08-24 12:22:42 +02:00
|
|
|
== SEE ALSO
|
|
|
|
|
|
|
|
|
|
i3(1)
|
|
|
|
|
|
|
|
|
|
== AUTHOR
|
|
|
|
|
|
|
|
|
|
Michael Stapelberg and contributors
|
