1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
\r
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
\r
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
\r
5 <link rel="icon" type="image/png" href="/favicon.png">
\r
6 <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
\r
7 <meta name="generator" content="AsciiDoc 8.6.9" />
\r
8 <title>i3: IPC interface (interprocess communication)</title>
\r
9 <link rel="stylesheet" href="/css/style.css" type="text/css" />
\r
10 <link rel="stylesheet" href="/css/xhtml11.css" type="text/css" />
\r
11 <script type="text/javascript">
\r
13 document.addEventListener("DOMContentLoaded", function(){asciidoc.footnotes(); asciidoc.toc(2);}, false);
\r
16 <script type="text/javascript" src="/js/asciidoc-xhtml11.js"></script>
\r
18 <body class="article">
\r
21 <a href="/"><h1 id="title">i3 - improved tiling WM</h1></a>
\r
23 <li><a style="border-bottom: 2px solid #fff" href="/docs">Docs</a></li>
\r
24 <li><a href="/screenshots">Screens</a></li>
\r
25 <li><a href="/contact">Contact</a></li>
\r
26 <li><a href="http://bugs.i3wm.org/">Bugs</a></li>
\r
28 <br style="clear: both">
\r
31 <h1>IPC interface (interprocess communication)</h1>
\r
32 <span id="author">Michael Stapelberg</span><br />
\r
33 <span id="email"><tt><<a href="mailto:michael@i3wm.org">michael@i3wm.org</a>></tt></span><br />
\r
34 <span id="revdate">February 2014</span>
\r
36 <div id="toctitle">Table of Contents</div>
37 <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
41 <div class="sectionbody">
\r
42 <div class="paragraph"><p>This document describes how to interface with i3 from a separate process. This
\r
43 is useful for example to remote-control i3 (to write test cases for example) or
\r
44 to get various information like the current workspaces to implement an external
\r
45 workspace bar.</p></div>
\r
46 <div class="paragraph"><p>The method of choice for IPC in our case is a unix socket because it has very
\r
47 little overhead on both sides and is usually available without headaches in
\r
48 most languages. In the default configuration file, the ipc-socket gets created
\r
49 in <tt>/tmp/i3-%u.XXXXXX/ipc-socket.%p</tt> where <tt>%u</tt> is your UNIX username, <tt>%p</tt> is
\r
50 the PID of i3 and XXXXXX is a string of random characters from the portable
\r
51 filename character set (see mkdtemp(3)). You can get the socketpath from i3 by
\r
52 calling <tt>i3 --get-socketpath</tt>.</p></div>
\r
53 <div class="paragraph"><p>All i3 utilities, like <tt>i3-msg</tt> and <tt>i3-input</tt> will read the <tt>I3_SOCKET_PATH</tt>
\r
54 X11 property, stored on the X11 root window.</p></div>
\r
55 <div class="admonitionblock">
\r
58 <div class="title">Warning</div>
\r
60 <td class="content">
\r
61 <div class="title">Use an existing library!</div>There are existing libraries for many languages. You can have a look at
\r
62 <a href="#libraries">[libraries]</a> or search the web if your language of choice is not mentioned.
\r
63 Usually, it is not necessary to implement low-level communication with i3
\r
70 <h2 id="_establishing_a_connection">1. Establishing a connection</h2>
\r
71 <div class="sectionbody">
\r
72 <div class="paragraph"><p>To establish a connection, simply open the IPC socket. The following code
\r
73 snippet illustrates this in Perl:</p></div>
\r
74 <div class="listingblock">
\r
75 <div class="content">
\r
76 <pre><tt>use IO::Socket::UNIX;
\r
77 chomp(my $path = qx(i3 --get-socketpath));
\r
78 my $sock = IO::Socket::UNIX->new(Peer => $path);</tt></pre>
\r
83 <h2 id="_sending_messages_to_i3">2. Sending messages to i3</h2>
\r
84 <div class="sectionbody">
\r
85 <div class="paragraph"><p>To send a message to i3, you have to format in the binary message format which
\r
86 i3 expects. This format specifies a magic string in the beginning to ensure
\r
87 the integrity of messages (to prevent follow-up errors). Following the magic
\r
88 string comes the length of the payload of the message as 32-bit integer, and
\r
89 the type of the message as 32-bit integer (the integers are not converted, so
\r
90 they are in native byte order).</p></div>
\r
91 <div class="paragraph"><p>The magic string currently is "i3-ipc" and will only be changed when a change
\r
92 in the IPC API is done which breaks compatibility (we hope that we don’t need
\r
93 to do that).</p></div>
\r
94 <div class="paragraph"><p>Currently implemented message types are the following:</p></div>
\r
95 <div class="dlist"><dl>
\r
96 <dt class="hdlist1">
\r
101 The payload of the message is a command for i3 (like the commands you
\r
102 can bind to keys in the configuration file) and will be executed
\r
103 directly after receiving it.
\r
106 <dt class="hdlist1">
\r
111 Gets the current workspaces. The reply will be a JSON-encoded list of
\r
112 workspaces (see the reply section).
\r
115 <dt class="hdlist1">
\r
120 Subscribes your connection to certain events. See <a href="#events">[events]</a> for a
\r
121 description of this message and the concept of events.
\r
124 <dt class="hdlist1">
\r
129 Gets the current outputs. The reply will be a JSON-encoded list of outputs
\r
130 (see the reply section).
\r
133 <dt class="hdlist1">
\r
138 Gets the layout tree. i3 uses a tree as data structure which includes
\r
139 every container. The reply will be the JSON-encoded tree (see the reply
\r
143 <dt class="hdlist1">
\r
148 Gets a list of marks (identifiers for containers to easily jump to them
\r
149 later). The reply will be a JSON-encoded list of window marks (see
\r
153 <dt class="hdlist1">
\r
158 Gets the configuration (as JSON map) of the workspace bar with the
\r
159 given ID. If no ID is provided, an array with all configured bar IDs is
\r
163 <dt class="hdlist1">
\r
168 Gets the version of i3. The reply will be a JSON-encoded dictionary
\r
169 with the major, minor, patch and human-readable version.
\r
173 <div class="paragraph"><p>So, a typical message could look like this:</p></div>
\r
174 <div class="listingblock">
\r
175 <div class="content">
\r
176 <pre><tt>"i3-ipc" <message length> <message type> <payload></tt></pre>
\r
178 <div class="paragraph"><p>Or, as a hexdump:</p></div>
\r
179 <div class="listingblock">
\r
180 <div class="content">
\r
181 <pre><tt>00000000 69 33 2d 69 70 63 04 00 00 00 00 00 00 00 65 78 |i3-ipc........ex|
\r
182 00000010 69 74 |it|</tt></pre>
\r
184 <div class="paragraph"><p>To generate and send such a message, you could use the following code in Perl:</p></div>
\r
185 <div class="listingblock">
\r
186 <div class="content">
\r
187 <pre><tt>sub format_ipc_command {
\r
190 # Get the real byte count (vs. amount of characters)
\r
191 { use bytes; $len = length($msg); }
\r
192 return "i3-ipc" . pack("LL", $len, 0) . $msg;
\r
195 $sock->write(format_ipc_command("exit"));</tt></pre>
\r
199 <div class="sect1">
\r
200 <h2 id="_receiving_replies_from_i3">3. Receiving replies from i3</h2>
\r
201 <div class="sectionbody">
\r
202 <div class="paragraph"><p>Replies from i3 usually consist of a simple string (the length of the string
\r
203 is the message_length, so you can consider them length-prefixed) which in turn
\r
204 contain the JSON serialization of a data structure. For example, the
\r
205 GET_WORKSPACES message returns an array of workspaces (each workspace is a map
\r
206 with certain attributes).</p></div>
\r
207 <div class="sect2">
\r
208 <h3 id="_reply_format">3.1. Reply format</h3>
\r
209 <div class="paragraph"><p>The reply format is identical to the normal message format. There also is
\r
210 the magic string, then the message length, then the message type and the
\r
212 <div class="paragraph"><p>The following reply types are implemented:</p></div>
\r
213 <div class="dlist"><dl>
\r
214 <dt class="hdlist1">
\r
219 Confirmation/Error code for the COMMAND message.
\r
222 <dt class="hdlist1">
\r
227 Reply to the GET_WORKSPACES message.
\r
230 <dt class="hdlist1">
\r
235 Confirmation/Error code for the SUBSCRIBE message.
\r
238 <dt class="hdlist1">
\r
243 Reply to the GET_OUTPUTS message.
\r
246 <dt class="hdlist1">
\r
251 Reply to the GET_TREE message.
\r
254 <dt class="hdlist1">
\r
259 Reply to the GET_MARKS message.
\r
262 <dt class="hdlist1">
\r
267 Reply to the GET_BAR_CONFIG message.
\r
270 <dt class="hdlist1">
\r
275 Reply to the GET_VERSION message.
\r
280 <div class="sect2">
\r
281 <h3 id="_command_reply">3.2. COMMAND reply</h3>
\r
282 <div class="paragraph"><p>The reply consists of a list of serialized maps for each command that was
\r
283 parsed. Each has the property <tt>success (bool)</tt> and may also include a
\r
284 human-readable error message in the property <tt>error (string)</tt>.</p></div>
\r
285 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
286 <div class="listingblock">
\r
287 <div class="content">
\r
288 <pre><tt>[{ "success": true }]</tt></pre>
\r
291 <div class="sect2">
\r
292 <h3 id="_workspaces_reply">3.3. WORKSPACES reply</h3>
\r
293 <div class="paragraph"><p>The reply consists of a serialized list of workspaces. Each workspace has the
\r
294 following properties:</p></div>
\r
295 <div class="dlist"><dl>
\r
296 <dt class="hdlist1">
\r
301 The logical number of the workspace. Corresponds to the command
\r
302 to switch to this workspace.
\r
305 <dt class="hdlist1">
\r
310 The name of this workspace (by default num+1), as changed by the
\r
311 user. Encoded in UTF-8.
\r
314 <dt class="hdlist1">
\r
319 Whether this workspace is currently visible on an output (multiple
\r
320 workspaces can be visible at the same time).
\r
323 <dt class="hdlist1">
\r
328 Whether this workspace currently has the focus (only one workspace
\r
329 can have the focus at the same time).
\r
332 <dt class="hdlist1">
\r
337 Whether a window on this workspace has the "urgent" flag set.
\r
340 <dt class="hdlist1">
\r
345 The rectangle of this workspace (equals the rect of the output it
\r
346 is on), consists of x, y, width, height.
\r
349 <dt class="hdlist1">
\r
354 The video output this workspace is on (LVDS1, VGA1, …).
\r
358 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
359 <div class="listingblock">
\r
360 <div class="content">
\r
393 <div class="sect2">
\r
394 <h3 id="_subscribe_reply">3.4. SUBSCRIBE reply</h3>
\r
395 <div class="paragraph"><p>The reply consists of a single serialized map. The only property is
\r
396 <tt>success (bool)</tt>, indicating whether the subscription was successful (the
\r
397 default) or whether a JSON parse error occurred.</p></div>
\r
398 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
399 <div class="listingblock">
\r
400 <div class="content">
\r
401 <pre><tt>{ "success": true }</tt></pre>
\r
404 <div class="sect2">
\r
405 <h3 id="_outputs_reply">3.5. OUTPUTS reply</h3>
\r
406 <div class="paragraph"><p>The reply consists of a serialized list of outputs. Each output has the
\r
407 following properties:</p></div>
\r
408 <div class="dlist"><dl>
\r
409 <dt class="hdlist1">
\r
414 The name of this output (as seen in <tt>xrandr(1)</tt>). Encoded in UTF-8.
\r
417 <dt class="hdlist1">
\r
422 Whether this output is currently active (has a valid mode).
\r
425 <dt class="hdlist1">
\r
426 current_workspace (string)
\r
430 The name of the current workspace that is visible on this output. <tt>null</tt> if
\r
431 the output is not active.
\r
434 <dt class="hdlist1">
\r
439 The rectangle of this output (equals the rect of the output it
\r
440 is on), consists of x, y, width, height.
\r
444 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
445 <div class="listingblock">
\r
446 <div class="content">
\r
451 "current_workspace": "4",
\r
462 "current_workspace": "1",
\r
473 <div class="sect2">
\r
474 <h3 id="_tree_reply">3.6. TREE reply</h3>
\r
475 <div class="paragraph"><p>The reply consists of a serialized tree. Each node in the tree (representing
\r
476 one container) has at least the properties listed below. While the nodes might
\r
477 have more properties, please do not use any properties which are not documented
\r
478 here. They are not yet finalized and will probably change!</p></div>
\r
479 <div class="dlist"><dl>
\r
480 <dt class="hdlist1">
\r
485 The internal ID (actually a C pointer value) of this container. Do not
\r
486 make any assumptions about it. You can use it to (re-)identify and
\r
487 address containers when talking to i3.
\r
490 <dt class="hdlist1">
\r
495 The internal name of this container. For all containers which are part
\r
496 of the tree structure down to the workspace contents, this is set to a
\r
497 nice human-readable name of the container.
\r
498 For containers that have an X11 window, the content is the title
\r
499 (_NET_WM_NAME property) of that window.
\r
500 For all other containers, the content is not defined (yet).
\r
503 <dt class="hdlist1">
\r
508 Type of this container. Can be one of "root", "output", "con",
\r
509 "floating_con", "workspace" or "dockarea".
\r
512 <dt class="hdlist1">
\r
517 Can be either "normal", "none" or "1pixel", dependending on the
\r
518 container’s border style.
\r
521 <dt class="hdlist1">
\r
522 current_border_width (integer)
\r
526 Number of pixels of the border width.
\r
529 <dt class="hdlist1">
\r
534 Can be either "splith", "splitv", "stacked", "tabbed", "dockarea" or
\r
536 Other values might be possible in the future, should we add new
\r
540 <dt class="hdlist1">
\r
541 orientation (string)
\r
545 Can be either "none" (for non-split containers), "horizontal" or
\r
547 THIS FIELD IS OBSOLETE. It is still present, but your code should not
\r
548 use it. Instead, rely on the layout field.
\r
551 <dt class="hdlist1">
\r
556 The percentage which this container takes in its parent. A value of
\r
557 <tt>null</tt> means that the percent property does not make sense for this
\r
558 container, for example for the root container.
\r
561 <dt class="hdlist1">
\r
566 The absolute display coordinates for this container. Display
\r
567 coordinates means that when you have two 1600x1200 monitors on a single
\r
568 X11 Display (the standard way), the coordinates of the first window on
\r
569 the second monitor are <tt>{ "x": 1600, "y": 0, "width": 1600, "height":
\r
573 <dt class="hdlist1">
\r
578 The coordinates of the <strong>actual client window</strong> inside its container.
\r
579 These coordinates are relative to the container and do not include the
\r
580 window decoration (which is actually rendered on the parent container).
\r
581 So, when using the <tt>default</tt> layout, you will have a 2 pixel border on
\r
582 each side, making the window_rect <tt>{ "x": 2, "y": 0, "width": 632,
\r
583 "height": 366 }</tt> (for example).
\r
586 <dt class="hdlist1">
\r
591 The original geometry the window specified when i3 mapped it. Used when
\r
592 switching a window to floating mode, for example.
\r
595 <dt class="hdlist1">
\r
600 The X11 window ID of the <strong>actual client window</strong> inside this container.
\r
601 This field is set to null for split containers or otherwise empty
\r
602 containers. This ID corresponds to what xwininfo(1) and other
\r
603 X11-related tools display (usually in hex).
\r
606 <dt class="hdlist1">
\r
611 Whether this container (window or workspace) has the urgency hint set.
\r
614 <dt class="hdlist1">
\r
619 Whether this container is currently focused.
\r
623 <div class="paragraph"><p>Please note that in the following example, I have left out some keys/values
\r
624 which are not relevant for the type of the node. Otherwise, the example would
\r
625 be by far too long (it already is quite long, despite showing only 1 window and
\r
626 one dock window).</p></div>
\r
627 <div class="paragraph"><p>It is useful to have an overview of the structure before taking a look at the
\r
628 JSON dump:</p></div>
\r
629 <div class="ulist"><ul>
\r
634 <div class="ulist"><ul>
\r
639 <div class="ulist"><ul>
\r
649 <div class="ulist"><ul>
\r
654 <div class="ulist"><ul>
\r
668 <div class="ulist"><ul>
\r
686 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
687 <div class="listingblock">
\r
688 <div class="content">
\r
703 "layout": "output",
\r
715 "layout": "dockarea",
\r
716 "orientation": "vertical",
\r
739 "orientation": "horizontal",
\r
746 "floating_nodes": [],
\r
752 "border": "normal",
\r
770 "name": "bottomdock",
\r
771 "layout": "dockarea",
\r
772 "orientation": "vertical",
\r
801 <div class="sect2">
\r
802 <h3 id="_marks_reply">3.7. MARKS reply</h3>
\r
803 <div class="paragraph"><p>The reply consists of a single array of strings for each container that has a
\r
804 mark. A mark can only be set on one container, so the array is unique.
\r
805 The order of that array is undefined.</p></div>
\r
806 <div class="paragraph"><p>If no window has a mark the response will be the empty array [].</p></div>
\r
808 <div class="sect2">
\r
809 <h3 id="_bar_config_reply">3.8. BAR_CONFIG reply</h3>
\r
810 <div class="paragraph"><p>This can be used by third-party workspace bars (especially i3bar, but others
\r
811 are free to implement compatible alternatives) to get the <tt>bar</tt> block
\r
812 configuration from i3.</p></div>
\r
813 <div class="paragraph"><p>Depending on the input, the reply is either:</p></div>
\r
814 <div class="dlist"><dl>
\r
815 <dt class="hdlist1">
\r
820 An array of configured bar IDs
\r
823 <dt class="hdlist1">
\r
828 A JSON map containing the configuration for the specified bar.
\r
832 <div class="paragraph"><p>Each bar configuration has the following properties:</p></div>
\r
833 <div class="dlist"><dl>
\r
834 <dt class="hdlist1">
\r
839 The ID for this bar. Included in case you request multiple
\r
840 configurations and want to differentiate the different replies.
\r
843 <dt class="hdlist1">
\r
848 Either <tt>dock</tt> (the bar sets the dock window type) or <tt>hide</tt> (the bar
\r
849 does not show unless a specific key is pressed).
\r
852 <dt class="hdlist1">
\r
857 Either <tt>bottom</tt> or <tt>top</tt> at the moment.
\r
860 <dt class="hdlist1">
\r
861 status_command (string)
\r
865 Command which will be run to generate a statusline. Each line on stdout
\r
866 of this command will be displayed in the bar. At the moment, no
\r
867 formatting is supported.
\r
870 <dt class="hdlist1">
\r
875 The font to use for text on the bar.
\r
878 <dt class="hdlist1">
\r
879 workspace_buttons (boolean)
\r
883 Display workspace buttons or not? Defaults to true.
\r
886 <dt class="hdlist1">
\r
887 binding_mode_indicator (boolean)
\r
891 Display the mode indicator or not? Defaults to true.
\r
894 <dt class="hdlist1">
\r
899 Should the bar enable verbose output for debugging? Defaults to false.
\r
902 <dt class="hdlist1">
\r
907 Contains key/value pairs of colors. Each value is a color code in hex,
\r
908 formatted #rrggbb (like in HTML).
\r
912 <div class="paragraph"><p>The following colors can be configured at the moment:</p></div>
\r
913 <div class="dlist"><dl>
\r
914 <dt class="hdlist1">
\r
919 Background color of the bar.
\r
922 <dt class="hdlist1">
\r
927 Text color to be used for the statusline.
\r
930 <dt class="hdlist1">
\r
935 Text color to be used for the separator.
\r
938 <dt class="hdlist1">
\r
939 focused_workspace_text/focused_workspace_bg
\r
943 Text color/background color for a workspace button when the workspace
\r
947 <dt class="hdlist1">
\r
948 active_workspace_text/active_workspace_bg
\r
952 Text color/background color for a workspace button when the workspace
\r
953 is active (visible) on some output, but the focus is on another one.
\r
954 You can only tell this apart from the focused workspace when you are
\r
955 using multiple monitors.
\r
958 <dt class="hdlist1">
\r
959 inactive_workspace_text/inactive_workspace_bg
\r
963 Text color/background color for a workspace button when the workspace
\r
964 does not have focus and is not active (visible) on any output. This
\r
965 will be the case for most workspaces.
\r
968 <dt class="hdlist1">
\r
969 urgent_workspace_text/urgent_workspace_bar
\r
973 Text color/background color for workspaces which contain at least one
\r
974 window with the urgency hint set.
\r
978 <div class="paragraph"><p><strong>Example of configured bars:</strong></p></div>
\r
979 <div class="listingblock">
\r
980 <div class="content">
\r
981 <pre><tt>["bar-bxuqzf"]</tt></pre>
\r
983 <div class="paragraph"><p><strong>Example of bar configuration:</strong></p></div>
\r
984 <div class="listingblock">
\r
985 <div class="content">
\r
987 "id": "bar-bxuqzf",
\r
989 "position": "bottom",
\r
990 "status_command": "i3status",
\r
991 "font": "-misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1",
\r
992 "workspace_buttons": true,
\r
993 "binding_mode_indicator": true,
\r
996 "background": "#c0c0c0",
\r
997 "statusline": "#00ff00",
\r
998 "focused_workspace_text": "#ffffff",
\r
999 "focused_workspace_bg": "#000000"
\r
1004 <div class="sect2">
\r
1005 <h3 id="_version_reply">3.9. VERSION reply</h3>
\r
1006 <div class="paragraph"><p>The reply consists of a single JSON dictionary with the following keys:</p></div>
\r
1007 <div class="dlist"><dl>
\r
1008 <dt class="hdlist1">
\r
1013 The major version of i3, such as <tt>4</tt>.
\r
1016 <dt class="hdlist1">
\r
1021 The minor version of i3, such as <tt>2</tt>. Changes in the IPC interface (new
\r
1022 features) will only occur with new minor (or major) releases. However,
\r
1023 bugfixes might be introduced in patch releases, too.
\r
1026 <dt class="hdlist1">
\r
1031 The patch version of i3, such as <tt>1</tt> (when the complete version is
\r
1032 <tt>4.2.1</tt>). For versions such as <tt>4.2</tt>, patch will be set to <tt>0</tt>.
\r
1035 <dt class="hdlist1">
\r
1036 human_readable (string)
\r
1040 A human-readable version of i3 containing the precise git version,
\r
1041 build date and branch name. When you need to display the i3 version to
\r
1042 your users, use the human-readable version whenever possible (since
\r
1043 this is what <tt>i3 --version</tt> displays, too).
\r
1047 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
1048 <div class="listingblock">
\r
1049 <div class="content">
\r
1051 "human_readable" : "4.2-169-gf80b877 (2012-08-05, branch \"next\")",
\r
1060 <div class="sect1">
\r
1061 <h2 id="_events">4. Events</h2>
\r
1062 <div class="sectionbody">
\r
1063 <div class="paragraph" id="events"><p>To get informed when certain things happen in i3, clients can subscribe to
\r
1064 events. Events consist of a name (like "workspace") and an event reply type
\r
1065 (like I3_IPC_EVENT_WORKSPACE). The events sent by i3 are in the same format
\r
1066 as replies to specific commands. However, the highest bit of the message type
\r
1067 is set to 1 to indicate that this is an event reply instead of a normal reply.</p></div>
\r
1068 <div class="paragraph"><p>Caveat: As soon as you subscribe to an event, it is not guaranteed any longer
\r
1069 that the requests to i3 are processed in order. This means, the following
\r
1070 situation can happen: You send a GET_WORKSPACES request but you receive a
\r
1071 "workspace" event before receiving the reply to GET_WORKSPACES. If your
\r
1072 program does not want to cope which such kinds of race conditions (an
\r
1073 event based library may not have a problem here), I suggest you create a
\r
1074 separate connection to receive events.</p></div>
\r
1075 <div class="sect2">
\r
1076 <h3 id="_subscribing_to_events">4.1. Subscribing to events</h3>
\r
1077 <div class="paragraph"><p>By sending a message of type SUBSCRIBE with a JSON-encoded array as payload
\r
1078 you can register to an event.</p></div>
\r
1079 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
1080 <div class="listingblock">
\r
1081 <div class="content">
\r
1082 <pre><tt>type: SUBSCRIBE
\r
1083 payload: [ "workspace", "focus" ]</tt></pre>
\r
1086 <div class="sect2">
\r
1087 <h3 id="_available_events">4.2. Available events</h3>
\r
1088 <div class="paragraph"><p>The numbers in parenthesis is the event type (keep in mind that you need to
\r
1089 strip the highest bit first).</p></div>
\r
1090 <div class="dlist"><dl>
\r
1091 <dt class="hdlist1">
\r
1096 Sent when the user switches to a different workspace, when a new
\r
1097 workspace is initialized or when a workspace is removed (because the
\r
1098 last client vanished).
\r
1101 <dt class="hdlist1">
\r
1106 Sent when RandR issues a change notification (of either screens,
\r
1107 outputs, CRTCs or output properties).
\r
1110 <dt class="hdlist1">
\r
1115 Sent whenever i3 changes its binding mode.
\r
1118 <dt class="hdlist1">
\r
1123 Sent when a client’s window is successfully reparented (that is when i3
\r
1124 has finished fitting it into a container), when a window received input
\r
1125 focus or when certain properties of the window have changed.
\r
1128 <dt class="hdlist1">
\r
1129 barconfig_update (4)
\r
1133 Sent when the hidden_state or mode field in the barconfig of any bar
\r
1134 instance was updated and when the config is reloaded.
\r
1138 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
1139 <div class="listingblock">
\r
1140 <div class="content">
\r
1141 <pre><tt># the appropriate 4 bytes read from the socket are stored in $input
\r
1143 # unpack a 32-bit unsigned integer
\r
1144 my $message_type = unpack("L", $input);
\r
1146 # check if the highest bit is 1
\r
1147 my $is_event = (($message_type >> 31) == 1);
\r
1149 # use the other bits
\r
1150 my $event_type = ($message_type & 0x7F);
\r
1153 say "Received event of type $event_type";
\r
1157 <div class="sect2">
\r
1158 <h3 id="_workspace_event">4.3. workspace event</h3>
\r
1159 <div class="paragraph"><p>This event consists of a single serialized map containing a property
\r
1160 <tt>change (string)</tt> which indicates the type of the change ("focus", "init",
\r
1161 "empty", "urgent").</p></div>
\r
1162 <div class="paragraph"><p>Moreover, when the change is "focus", an <tt>old (object)</tt> and a <tt>current
\r
1163 (object)</tt> properties will be present with the previous and current
\r
1164 workspace respectively. When the first switch occurs (when i3 focuses
\r
1165 the workspace visible at the beginning) there is no previous
\r
1166 workspace, and the <tt>old</tt> property will be set to <tt>null</tt>. Also note
\r
1167 that if the previous is empty it will get destroyed when switching,
\r
1168 but will still be present in the "old" property.</p></div>
\r
1169 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
1170 <div class="listingblock">
\r
1171 <div class="content">
\r
1173 "change": "focus",
\r
1176 "type": "workspace",
\r
1181 "type": "workspace",
\r
1187 <div class="sect2">
\r
1188 <h3 id="_output_event">4.4. output event</h3>
\r
1189 <div class="paragraph"><p>This event consists of a single serialized map containing a property
\r
1190 <tt>change (string)</tt> which indicates the type of the change (currently only
\r
1191 "unspecified").</p></div>
\r
1192 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
1193 <div class="listingblock">
\r
1194 <div class="content">
\r
1195 <pre><tt>{ "change": "unspecified" }</tt></pre>
\r
1198 <div class="sect2">
\r
1199 <h3 id="_mode_event">4.5. mode event</h3>
\r
1200 <div class="paragraph"><p>This event consists of a single serialized map containing a property
\r
1201 <tt>change (string)</tt> which holds the name of current mode in use. The name
\r
1202 is the same as specified in config when creating a mode. The default
\r
1203 mode is simply named default.</p></div>
\r
1204 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
1205 <div class="listingblock">
\r
1206 <div class="content">
\r
1207 <pre><tt>{ "change": "default" }</tt></pre>
\r
1210 <div class="sect2">
\r
1211 <h3 id="_window_event">4.6. window event</h3>
\r
1212 <div class="paragraph"><p>This event consists of a single serialized map containing a property
\r
1213 <tt>change (string)</tt> which indicates the type of the change</p></div>
\r
1214 <div class="ulist"><ul>
\r
1217 <tt>new</tt> - the window has become managed by i3
\r
1222 <tt>focus</tt> - the window has received input focus
\r
1227 <tt>title</tt> - the window’s title has changed
\r
1232 <tt>fullscreen_mode</tt> - the window has entered or exited fullscreen mode
\r
1236 <div class="paragraph"><p>Additionally a <tt>container (object)</tt> field will be present, which consists
\r
1237 of the window’s parent container. Be aware that for the "new" event, the
\r
1238 container will hold the initial name of the newly reparented window (e.g.
\r
1239 if you run urxvt with a shell that changes the title, you will still at
\r
1240 this point get the window title as "urxvt").</p></div>
\r
1241 <div class="paragraph"><p><strong>Example:</strong></p></div>
\r
1242 <div class="listingblock">
\r
1243 <div class="content">
\r
1254 <div class="sect2">
\r
1255 <h3 id="_barconfig_update_event">4.7. barconfig_update event</h3>
\r
1256 <div class="paragraph"><p>This event consists of a single serialized map reporting on options from the
\r
1257 barconfig of the specified bar_id that were updated in i3. This event is the
\r
1258 same as a <tt>GET_BAR_CONFIG</tt> reply for the bar with the given id.</p></div>
\r
1262 <div class="sect1">
\r
1263 <h2 id="_see_also_existing_libraries">5. See also (existing libraries)</h2>
\r
1264 <div class="sectionbody">
\r
1265 <div class="paragraph" id="libraries"><p>For some languages, libraries are available (so you don’t have to implement
\r
1266 all this on your own). This list names some (if you wrote one, please let me
\r
1268 <div class="dlist"><dl>
\r
1269 <dt class="hdlist1">
\r
1274 i3 includes a headerfile <tt>i3/ipc.h</tt> which provides you all constants.
\r
1276 <div class="literalblock">
\r
1277 <div class="content">
\r
1278 <pre><tt> https://github.com/acrisci/i3ipc-glib
\r
1280 * https://github.com/proxypoke/i3ipc
\r
1282 * https://github.com/acrisci/i3ipc-gjs
\r
1284 * https:/github.com/acrisci/i3ipc-lua
\r
1286 * https://metacpan.org/module/AnyEvent::I3
\r
1288 * https://github.com/acrisci/i3ipc-python
\r
1289 * https://github.com/whitelynx/i3ipc (not maintained)
\r
1290 * https://github.com/ziberna/i3-py (not maintained)
\r
1292 http://github.com/badboy/i3-ipc</tt></pre>
\r
1299 <div id="footnotes"><hr /></div>
\r
1300 <div id="footer" lang="de">
\r
1301 © 2009-2011 Michael Stapelberg, <a href="/impress.html">Impressum</a>
\r