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/x-icon" href="/favicon.ico">
\r
6 <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
\r
7 <meta name="generator" content="AsciiDoc 8.6.10" />
\r
8 <title>i3: i3bar input protocol</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();}, 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="https://www.reddit.com/r/i3wm/">FAQ</a></li>
\r
26 <li><a href="/contact">Contact</a></li>
\r
27 <li><a href="https://github.com/i3/i3/issues">Bugs</a></li>
\r
29 <br style="clear: both">
\r
32 <h1>i3bar input protocol</h1>
\r
33 <span id="author">Michael Stapelberg</span><br />
\r
34 <span id="email"><tt><<a href="mailto:michael@i3wm.org">michael@i3wm.org</a>></tt></span><br />
\r
35 <span id="revdate">August 2012</span>
\r
38 <div class="sectionbody">
\r
39 <div class="paragraph"><p>This document explains the protocol in which i3bar expects its input. It
\r
40 provides support for colors, urgency, shortening and easy manipulation.</p></div>
\r
44 <h2 id="_rationale_for_choosing_json">1. Rationale for choosing JSON</h2>
\r
45 <div class="sectionbody">
\r
46 <div class="paragraph"><p>Before describing the protocol, let’s cover why JSON is a building block of
\r
47 this protocol.</p></div>
\r
48 <div class="olist arabic"><ol class="arabic">
\r
51 Other bar display programs such as dzen2 or xmobar are using in-band
\r
52 signaling: they recognize certain sequences (like ^fg(#330000) in your input
\r
53 text). We would like to avoid that and separate information from
\r
54 meta-information. By information, we mean the actual output, like the IP
\r
55 address of your ethernet adapter and by meta-information, we mean in which
\r
56 color it should be displayed right now.
\r
61 It is easy to write a simple script which manipulates part(s) of the input.
\r
62 Each block of information (like a block for the disk space indicator, a block
\r
63 for the current IP address, etc.) can be identified specifically and modified
\r
64 in whichever way you like.
\r
69 It remains easy to write a simple script which just suffixes (or prefixes) a
\r
70 status line input, because tools like i3status will output their JSON in
\r
71 such a way that each line array will be terminated by a newline. Therefore,
\r
72 you are not required to use a streaming JSON parser, but you can use any
\r
73 JSON parser and write your script in any programming language. In fact, you
\r
74 can decide to not bother with the JSON parsing at all and just inject your
\r
75 output at a specific position (beginning or end).
\r
80 Relying on JSON does not introduce any new dependencies. In fact, the IPC
\r
81 interface of i3 also uses JSON, therefore i3bar already depends on JSON.
\r
85 <div class="paragraph"><p>The only point against using JSON is computational complexity. If that really
\r
86 bothers you, just use the plain text input format (which i3bar will continue to
\r
91 <h2 id="_the_protocol">2. The protocol</h2>
\r
92 <div class="sectionbody">
\r
93 <div class="paragraph"><p>The first message of the protocol is a header block, which contains (at least)
\r
94 the version of the protocol to be used. In case there are significant changes
\r
95 (not only additions), the version will be incremented. i3bar will still
\r
96 understand the old protocol version, but in order to use the new one, you need
\r
97 to provide the correct version. The header block is terminated by a newline and
\r
98 consists of a single JSON hash:</p></div>
\r
99 <div class="paragraph"><p><strong>Minimal example</strong>:</p></div>
\r
100 <div class="listingblock">
\r
101 <div class="content">
\r
102 <pre><tt>{ "version": 1 }</tt></pre>
\r
104 <div class="paragraph"><p><strong>All features example</strong>:</p></div>
\r
105 <div class="listingblock">
\r
106 <div class="content">
\r
107 <pre><tt>{ "version": 1, "stop_signal": 10, "cont_signal": 12, "click_events": true }</tt></pre>
\r
109 <div class="paragraph"><p>(Note that before i3 v4.3 the precise format had to be <tt>{"version":1}</tt>,
\r
110 byte-for-byte.)</p></div>
\r
111 <div class="paragraph"><p>What follows is an infinite array (so it should be parsed by a streaming JSON
\r
112 parser, but as described above you can go for a simpler solution), whose
\r
113 elements are one array per status line. A status line is one unit of
\r
114 information which should be displayed at a time. i3bar will not display any
\r
115 input until the status line is complete. In each status line, every block will
\r
116 be represented by a JSON hash:</p></div>
\r
117 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
118 <div class="listingblock">
\r
119 <div class="content">
\r
124 "full_text": "E: 10.0.0.1 (1000 Mbit/s)",
\r
128 "full_text": "2012-01-05 20:00:01"
\r
134 "full_text": "E: 10.0.0.1 (1000 Mbit/s)",
\r
138 "full_text": "2012-01-05 20:00:02"
\r
143 <div class="paragraph"><p>Please note that this example was pretty printed for human consumption.
\r
144 i3status and others will output single statuslines in one line, separated by
\r
146 <div class="paragraph"><p>You can find an example of a shell script which can be used as your
\r
147 <tt>status_command</tt> in the bar configuration at
\r
148 <a href="https://github.com/i3/i3/blob/next/contrib/trivial-bar-script.sh">https://github.com/i3/i3/blob/next/contrib/trivial-bar-script.sh</a></p></div>
\r
149 <div class="sect2">
\r
150 <h3 id="_header_in_detail">2.1. Header in detail</h3>
\r
151 <div class="dlist"><dl>
\r
152 <dt class="hdlist1">
\r
157 The version number (as an integer) of the i3bar protocol you will use.
\r
160 <dt class="hdlist1">
\r
165 Specify to i3bar the signal (as an integer) to send to stop your
\r
167 The default value (if none is specified) is SIGSTOP.
\r
170 <dt class="hdlist1">
\r
175 Specify to i3bar the signal (as an integer) to send to continue your
\r
177 The default value (if none is specified) is SIGCONT.
\r
180 <dt class="hdlist1">
\r
185 If specified and true i3bar will write an infinite array (same as above)
\r
191 <div class="sect2">
\r
192 <h3 id="_blocks_in_detail">2.2. Blocks in detail</h3>
\r
193 <div class="dlist"><dl>
\r
194 <dt class="hdlist1">
\r
199 The <tt>full_text</tt> will be displayed by i3bar on the status line. This is the
\r
200 only required key. If <tt>full_text</tt> is an empty string, the block will be
\r
204 <dt class="hdlist1">
\r
209 Where appropriate, the <tt>short_text</tt> (string) entry should also be
\r
210 provided. It will be used in case the status line needs to be shortened
\r
211 because it uses more space than your screen provides. For example, when
\r
212 displaying an IPv6 address, the prefix is usually (!) more relevant
\r
213 than the suffix, because the latter stays constant when using autoconf,
\r
214 while the prefix changes. When displaying the date, the time is more
\r
215 important than the date (it is more likely that you know which day it
\r
216 is than what time it is).
\r
219 <dt class="hdlist1">
\r
224 To make the current state of the information easy to spot, colors can
\r
225 be used. For example, the wireless block could be displayed in red
\r
226 (using the <tt>color</tt> (string) entry) if the card is not associated with
\r
227 any network and in green or yellow (depending on the signal strength)
\r
228 when it is associated.
\r
229 Colors are specified in hex (like in HTML), starting with a leading
\r
230 hash sign. For example, <tt>#ff0000</tt> means red.
\r
233 <dt class="hdlist1">
\r
238 Overrides the background color for this particular block.
\r
241 <dt class="hdlist1">
\r
246 Overrides the border color for this particular block.
\r
249 <dt class="hdlist1">
\r
254 The minimum width (in pixels) of the block. If the content of the
\r
255 <tt>full_text</tt> key take less space than the specified min_width, the block
\r
256 will be padded to the left and/or the right side, according to the <tt>align</tt>
\r
257 key. This is useful when you want to prevent the whole status line to shift
\r
258 when value take more or less space between each iteration.
\r
259 The value can also be a string. In this case, the width of the text given
\r
260 by <tt>min_width</tt> determines the minimum width of the block. This is useful
\r
261 when you want to set a sensible minimum width regardless of which font you
\r
262 are using, and at what particular size.
\r
265 <dt class="hdlist1">
\r
270 Align text on the <tt>center</tt>, <tt>right</tt> or <tt>left</tt> (default) of the block, when
\r
271 the minimum width of the latter, specified by the <tt>min_width</tt> key, is not
\r
275 <dt class="hdlist1">
\r
280 Every block should have a unique <tt>name</tt> (string) entry so that it can
\r
281 be easily identified in scripts which process the output. i3bar
\r
282 completely ignores the name and instance fields. Make sure to also
\r
283 specify an <tt>instance</tt> (string) entry where appropriate. For example,
\r
284 the user can have multiple disk space blocks for multiple mount points.
\r
287 <dt class="hdlist1">
\r
292 A boolean which specifies whether the current value is urgent. Examples
\r
293 are battery charge values below 1 percent or no more available disk
\r
294 space (for non-root users). The presentation of urgency is up to i3bar.
\r
297 <dt class="hdlist1">
\r
302 A boolean which specifies whether a separator line should be drawn
\r
303 after this block. The default is true, meaning the separator line will
\r
304 be drawn. Note that if you disable the separator line, there will still
\r
305 be a gap after the block, unless you also use <tt>separator_block_width</tt>.
\r
308 <dt class="hdlist1">
\r
309 separator_block_width
\r
313 The amount of pixels to leave blank after the block. In the middle of
\r
314 this gap, a separator line will be drawn unless <tt>separator</tt> is
\r
315 disabled. Normally, you want to set this to an odd value (the default
\r
316 is 9 pixels), since the separator line is drawn in the middle.
\r
319 <dt class="hdlist1">
\r
324 A string that indicates how the text of the block should be parsed. Set to
\r
325 <tt>"pango"</tt> to use <a href="https://developer.gnome.org/pango/stable/PangoMarkupFormat.html">Pango markup</a>.
\r
326 Set to <tt>"none"</tt> to not use any markup (default). Pango markup only works
\r
327 if you use a pango font.
\r
331 <div class="paragraph"><p>If you want to put in your own entries into a block, prefix the key with an
\r
332 underscore (_). i3bar will ignore all keys it doesn’t understand, and prefixing
\r
333 them with an underscore makes it clear in every script that they are not part
\r
334 of the i3bar protocol.</p></div>
\r
335 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
336 <div class="listingblock">
\r
337 <div class="content">
\r
339 "full_text": "E: 10.0.0.1 (1000 Mbit/s)",
\r
340 "_ethernet_vendor": "Intel"
\r
343 <div class="paragraph"><p>In the following example, the longest (widest) possible value of the block is
\r
344 used to set the minimum width:</p></div>
\r
345 <div class="listingblock">
\r
346 <div class="content">
\r
348 "full_text": "CPU 4%",
\r
349 "min_width": "CPU 100%",
\r
353 <div class="paragraph"><p>An example of a block which uses all possible entries follows:</p></div>
\r
354 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
355 <div class="listingblock">
\r
356 <div class="content">
\r
358 "full_text": "E: 10.0.0.1 (1000 Mbit/s)",
\r
359 "short_text": "10.0.0.1",
\r
360 "color": "#00ff00",
\r
361 "background": "#1c1c1c",
\r
362 "border": "#ee0000",
\r
366 "name": "ethernet",
\r
367 "instance": "eth0",
\r
369 "separator_block_width": 9
\r
373 <div class="sect2">
\r
374 <h3 id="_click_events">2.3. Click events</h3>
\r
375 <div class="paragraph"><p>If enabled i3bar will send you notifications if the user clicks on a block and
\r
376 looks like this:</p></div>
\r
377 <div class="dlist"><dl>
\r
378 <dt class="hdlist1">
\r
383 Name of the block, if set
\r
386 <dt class="hdlist1">
\r
391 Instance of the block, if set
\r
394 <dt class="hdlist1">
\r
399 X11 root window coordinates where the click occurred
\r
402 <dt class="hdlist1">
\r
407 X11 button ID (for example 1 to 3 for left/middle/right mouse button)
\r
410 <dt class="hdlist1">
\r
411 relative_x, relative_y
\r
415 Coordinates where the click occurred, with respect to the top left corner
\r
419 <dt class="hdlist1">
\r
424 Width and height (in px) of the block
\r
427 <dt class="hdlist1">
\r
432 An array of the modifiers active when the click occurred. The order in which
\r
433 modifiers are listed is not guaranteed.
\r
437 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
438 <div class="listingblock">
\r
439 <div class="content">
\r
441 "name": "ethernet",
\r
442 "instance": "eth0",
\r
444 "modifiers": ["Shift", "Mod1"],
\r
457 <div id="footnotes"><hr /></div>
\r
458 <div id="footer" lang="de">
\r
459 © 2009-2011 Michael Stapelberg, <a href="/impress.html">Impressum</a>
\r
projects / i3 / i3.github.io / blob