<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>i3 FAQ - Individual question feed</title><link>https://faq.i3wm.org/questions/</link><description>Frequently asked questions and answers about the i3 window manager</description><atom:link href="http://faq.i3wm.org/feeds/question/6330/" rel="self"></atom:link><language>en</language><copyright>Copyright i3, 2012</copyright><lastBuildDate>Wed, 22 Jul 2015 04:05:24 +0000</lastBuildDate><item><title>i3 3 commands after another</title><link>https://faq.i3wm.org/question/6330/i3-3-commands-after-another/</link><description> I want to enable the keyboard, log the screen, and  disable the keyboard again
like:
xinput enable 10 &amp;&amp; sudo pm-suspend | i3lock ; **xinput disable 10**
this is where the error happens</description><pubDate>Tue, 21 Jul 2015 20:15:22 +0000</pubDate><guid>https://faq.i3wm.org/question/6330/i3-3-commands-after-another/</guid></item><item><title>Answer by i3convert for &lt;p&gt;I want to enable the keyboard, log the screen, and  disable the keyboard again
like:
xinput enable 10 &amp;amp;&amp;amp; sudo pm-suspend | i3lock ; &lt;strong&gt;xinput disable 10&lt;/strong&gt;
this is where the error happens&lt;/p&gt;
 </title><link>https://faq.i3wm.org/question/6330/i3-3-commands-after-another/?answer=6331#post-id-6331</link><description> The best solution is usually to create a separate script file and just call it.</description><pubDate>Tue, 21 Jul 2015 20:21:51 +0000</pubDate><guid>https://faq.i3wm.org/question/6330/i3-3-commands-after-another/?answer=6331#post-id-6331</guid></item><item><title>Comment by i3convert for &lt;p&gt;The best solution is usually to create a separate script file and just call it.&lt;/p&gt;
</title><link>https://faq.i3wm.org/question/6330/i3-3-commands-after-another/?comment=6335#comment-6335</link><description>@Sol64: Run commands in order in which you want them to be executed, but run i3lock with the -n switch. The i3lock command won't finish (more precisely, it won't fork) until the screen is unlocked. Is this what you want?</description><pubDate>Wed, 22 Jul 2015 04:05:24 +0000</pubDate><guid>https://faq.i3wm.org/question/6330/i3-3-commands-after-another/?comment=6335#comment-6335</guid></item><item><title>Comment by Sol64 for &lt;p&gt;The best solution is usually to create a separate script file and just call it.&lt;/p&gt;
</title><link>https://faq.i3wm.org/question/6330/i3-3-commands-after-another/?comment=6333#comment-6333</link><description>I tried but than i3lock and xinput disable 10 are executed at the same time</description><pubDate>Tue, 21 Jul 2015 20:24:30 +0000</pubDate><guid>https://faq.i3wm.org/question/6330/i3-3-commands-after-another/?comment=6333#comment-6333</guid></item><item><title>Answer by Sol64 for &lt;p&gt;I want to enable the keyboard, log the screen, and  disable the keyboard again
like:
xinput enable 10 &amp;amp;&amp;amp; sudo pm-suspend | i3lock ; &lt;strong&gt;xinput disable 10&lt;/strong&gt;
this is where the error happens&lt;/p&gt;
 </title><link>https://faq.i3wm.org/question/6330/i3-3-commands-after-another/?answer=6332#post-id-6332</link><description>i tried but then i3lock and xinput disable 10 are executed at the same time ...</description><pubDate>Tue, 21 Jul 2015 20:23:46 +0000</pubDate><guid>https://faq.i3wm.org/question/6330/i3-3-commands-after-another/?answer=6332#post-id-6332</guid></item></channel></rss>