i3 FAQ - Individual question feed

i3 FAQ - Individual question feedhttps://faq.i3wm.org/questions/Frequently asked questions and answers about the i3 window managerenCopyright i3, 2012Wed, 29 Apr 2015 20:03:45 +0000Is it possible to match a window based on the window type? (NORMAL, DIALOG etc.)https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/Shutter is a pretty awesome screenshot tool, but it doesn't have any distinctive instance names or window roles for its various windows. This makes it impossible to write i3 criteria to match the *main* window of the application, since it has the same role, class and instance as all the other windows. The only distinctive feature I can find about the main window is that the window type is set to "normal": _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL While the other windows are "dialogs". **There doesn't seem to be a way to match window types using just the criteria though, so do you guys know of a different way to match the main window?** --- Currently I am doing this: # Shutter set $shutter [class="Shutter" title="^Session"] set $prtscr 107 for_window $shutter move scratchpad bindcode $prtscr $shutter scratchpad show This causes the Shutter main window to get hidden in the scratchpad when launched, and I can summon it using the PrtScr key. The problem is that the Shutter window title only starts with "Session" when there are no screenshots in the Shutter session. As soon as I actually grab a screenshot, the window title changes and this configuration stops working. I am experimenting with using marks to solve this, but I haven't had any luck yet. I have filed a bug report: - https:// bugs.launchpad.net /shutter/+bug/1441942 - https:// bugs.debian.org /cgi-bin/bugreport.cgi?bug=782181Tue, 14 Apr 2015 10:34:59 +0000https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/Comment by Tomas Sandven for Shutter is a pretty awesome screenshot tool, but it doesn't have any distinctive instance names or window roles for its various windows. This makes it impossible to write i3 criteria to match the main window of the application, since it has the same role, class and instance as all the other windows. The only distinctive feature I can find about the main window is that the window type is set to "normal": <pre><code>_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL </code></pre> While the other windows are "dialogs". There doesn't seem to be a way to match window types using just the criteria though, so do you guys know of a different way to match the main window? <hr/> Currently I am doing this: <pre><code># Shutter set $shutter [class="Shutter" title="^Session"] set $prtscr 107 for_window $shutter move scratchpad bindcode $prtscr $shutter scratchpad show </code></pre> This causes the Shutter main window to get hidden in the scratchpad when launched, and I can summon it using the PrtScr key. The problem is that the Shutter window title only starts with "Session" when there are no screenshots in the Shutter session. As soon as I actually grab a screenshot, the window title changes and this configuration stops working. I am experimenting with using marks to solve this, but I haven't had any luck yet. I have filed a bug report: <ul> <li>https:// <a href="http://bugs.launchpad.net">bugs.launchpad.net</a> /shutter/+bug/1441942</li> <li>https:// <a href="http://bugs.debian.org">bugs.debian.org</a> /cgi-bin/bugreport.cgi?bug=782181</li> </ul> https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5790#comment-5790NB: I tried to all lots of useful links to relevant parts of the documentation, but apparently my karma is too lowTue, 14 Apr 2015 10:35:37 +0000https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5790#comment-5790Answer by Airblader for Shutter is a pretty awesome screenshot tool, but it doesn't have any distinctive instance names or window roles for its various windows. This makes it impossible to write i3 criteria to match the main window of the application, since it has the same role, class and instance as all the other windows. The only distinctive feature I can find about the main window is that the window type is set to "normal": <pre><code>_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL </code></pre> While the other windows are "dialogs". There doesn't seem to be a way to match window types using just the criteria though, so do you guys know of a different way to match the main window? <hr/> Currently I am doing this: <pre><code># Shutter set $shutter [class="Shutter" title="^Session"] set $prtscr 107 for_window $shutter move scratchpad bindcode $prtscr $shutter scratchpad show </code></pre> This causes the Shutter main window to get hidden in the scratchpad when launched, and I can summon it using the PrtScr key. The problem is that the Shutter window title only starts with "Session" when there are no screenshots in the Shutter session. As soon as I actually grab a screenshot, the window title changes and this configuration stops working. I am experimenting with using marks to solve this, but I haven't had any luck yet. I have filed a bug report: <ul> <li>https:// <a href="http://bugs.launchpad.net">bugs.launchpad.net</a> /shutter/+bug/1441942</li> <li>https:// <a href="http://bugs.debian.org">bugs.debian.org</a> /cgi-bin/bugreport.cgi?bug=782181</li> </ul> https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?answer=5916#post-id-5916It's worth mentioning that based off of this thread, the feature to use window types as criteria has been added to i3 now. The syntax is for_window [window_type="normal"] … A variety of types are supported: normal, dialog, utility, toolbar, splash, menu, dropdown\_menu, popup\_menu, tooltip. The feature will be available with the first non-bugfix release after 4.10.2 which will either be 4.11 or 5.0, I would expect.Wed, 29 Apr 2015 12:22:43 +0000https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?answer=5916#post-id-5916Comment by Airblader for It's worth mentioning that based off of this thread, the feature to use window types as criteria has been added to i3 now. The syntax is <pre><code>for_window [window_type="normal"] … </code></pre> A variety of types are supported: normal, dialog, utility, toolbar, splash, menu, dropdown_menu, popup_menu, tooltip. The feature will be available with the first non-bugfix release after 4.10.2 which will either be 4.11 or 5.0, I would expect. https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5918#comment-5918I've updated it a little. :)Wed, 29 Apr 2015 20:03:45 +0000https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5918#comment-5918Comment by Adaephon for It's worth mentioning that based off of this thread, the feature to use window types as criteria has been added to i3 now. The syntax is <pre><code>for_window [window_type="normal"] … </code></pre> A variety of types are supported: normal, dialog, utility, toolbar, splash, menu, dropdown_menu, popup_menu, tooltip. The feature will be available with the first non-bugfix release after 4.10.2 which will either be 4.11 or 5.0, I would expect. https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5917#comment-5917Great news and thanks for implementing this feature. Can you please add a bit of information on how to use it? It would make for a much better answer than my ugly workaround.Wed, 29 Apr 2015 19:23:08 +0000https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5917#comment-5917Answer by Adaephon for Shutter is a pretty awesome screenshot tool, but it doesn't have any distinctive instance names or window roles for its various windows. This makes it impossible to write i3 criteria to match the main window of the application, since it has the same role, class and instance as all the other windows. The only distinctive feature I can find about the main window is that the window type is set to "normal": <pre><code>_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL </code></pre> While the other windows are "dialogs". There doesn't seem to be a way to match window types using just the criteria though, so do you guys know of a different way to match the main window? <hr/> Currently I am doing this: <pre><code># Shutter set $shutter [class="Shutter" title="^Session"] set $prtscr 107 for_window $shutter move scratchpad bindcode $prtscr $shutter scratchpad show </code></pre> This causes the Shutter main window to get hidden in the scratchpad when launched, and I can summon it using the PrtScr key. The problem is that the Shutter window title only starts with "Session" when there are no screenshots in the Shutter session. As soon as I actually grab a screenshot, the window title changes and this configuration stops working. I am experimenting with using marks to solve this, but I haven't had any luck yet. I have filed a bug report: <ul> <li>https:// <a href="http://bugs.launchpad.net">bugs.launchpad.net</a> /shutter/+bug/1441942</li> <li>https:// <a href="http://bugs.debian.org">bugs.debian.org</a> /cgi-bin/bugreport.cgi?bug=782181</li> </ul> https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?answer=5791#post-id-5791At the moment it is not possible to have window types as criteria. ---- But in this case it may not be necessary. As you can (reliably?) identify the window in question at least in its initial state, you can use `mark` to give it an unique identifier and then use that instead of `class` and `title`: set $shutter "THIS_IS_SHUTTER" set $prtscr 107 for_window [class="Shutter" title="^Session"] mark $shutter, move scratchpad bindcode $prtscr [con_mark=$shutter] scratchpad show This marks the Shutter window and than moves it to scratchpad in one go. The mark is than used with the `con_mark` criterion. Note that it is important to use `,` to separate the `mark` and `move` commands instead of `;`, else the criterion would only be applied for the first command.Tue, 14 Apr 2015 11:11:00 +0000https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?answer=5791#post-id-5791Comment by Adaephon for At the moment it is not possible to have window types as criteria. <hr/> But in this case it may not be necessary. As you can (reliably?) identify the window in question at least in its initial state, you can use <code>mark</code> to give it an unique identifier and then use that instead of <code>class</code> and <code>title</code>: <pre><code>set $shutter "THIS_IS_SHUTTER" set $prtscr 107 for_window [class="Shutter" title="^Session"] mark $shutter, move scratchpad bindcode $prtscr [con_mark=$shutter] scratchpad show </code></pre> This marks the Shutter window and than moves it to scratchpad in one go. The mark is than used with the <code>con_mark</code> criterion. Note that it is important to use <code>,</code> to separate the <code>mark</code> and <code>move</code> commands instead of <code>;</code>, else the criterion would only be applied for the first command. https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5794#comment-5794Sorry, I do not use Shutter, so I did not actually test it with that. As for plans about this feature: at least in the [i3 bug tracker](https://github.com/i3/i3/issues) I could not find anything about that. If you want you can open an feature request there.Tue, 14 Apr 2015 12:38:27 +0000https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5794#comment-5794Comment by Tomas Sandven for At the moment it is not possible to have window types as criteria. <hr/> But in this case it may not be necessary. As you can (reliably?) identify the window in question at least in its initial state, you can use <code>mark</code> to give it an unique identifier and then use that instead of <code>class</code> and <code>title</code>: <pre><code>set $shutter "THIS_IS_SHUTTER" set $prtscr 107 for_window [class="Shutter" title="^Session"] mark $shutter, move scratchpad bindcode $prtscr [con_mark=$shutter] scratchpad show </code></pre> This marks the Shutter window and than moves it to scratchpad in one go. The mark is than used with the <code>con_mark</code> criterion. Note that it is important to use <code>,</code> to separate the <code>mark</code> and <code>move</code> commands instead of <code>;</code>, else the criterion would only be applied for the first command. https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5792#comment-5792I just tried that, and it doesn't work. Or rather, it works just like the solution I'm currently using. It turns out the main window closes while I take a screenshot, then reopens with a title that doesn't match the criteria.Tue, 14 Apr 2015 11:58:57 +0000https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5792#comment-5792Comment by Tomas Sandven for At the moment it is not possible to have window types as criteria. <hr/> But in this case it may not be necessary. As you can (reliably?) identify the window in question at least in its initial state, you can use <code>mark</code> to give it an unique identifier and then use that instead of <code>class</code> and <code>title</code>: <pre><code>set $shutter "THIS_IS_SHUTTER" set $prtscr 107 for_window [class="Shutter" title="^Session"] mark $shutter, move scratchpad bindcode $prtscr [con_mark=$shutter] scratchpad show </code></pre> This marks the Shutter window and than moves it to scratchpad in one go. The mark is than used with the <code>con_mark</code> criterion. Note that it is important to use <code>,</code> to separate the <code>mark</code> and <code>move</code> commands instead of <code>;</code>, else the criterion would only be applied for the first command. https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5793#comment-5793Also, do you know if window types as a criteria is planned, or has it been rejected for some reason?Tue, 14 Apr 2015 12:07:21 +0000https://faq.i3wm.org/question/5789/is-it-possible-to-match-a-window-based-on-the-window-type-normal-dialog-etc/?comment=5793#comment-5793