On 27.04.2013 16:50, Daniel wrote:
> On 2013-04-25, Uli Schlachter wrote:
>> P.S.: You don't need wmctrl to find a window by pid:
>>
>> function find_by_pid(pid)
>>for _, c in pairs(client.get()) do
>> if c.pid == pid then return c end
>>end
>> end
>
> Here I attempt to first spawn a
On 2013-04-25, Uli Schlachter wrote:
> P.S.: You don't need wmctrl to find a window by pid:
>
> function find_by_pid(pid)
>for _, c in pairs(client.get()) do
> if c.pid == pid then return c end
>end
> end
Here I attempt to first spawn and then catch the window by pid, but I
seem to l
The idea was to restart some programs after power cycling, not only
restart of awesome. So pid is out of the question.
Yes, I really would like to make a program open its window on the
desktop of my choice. But it seems impossible.
--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.or
I think you can match with the pid. (
http://awesome.naquadah.org/doc/api/modules/client.html#client has a field
called pid)
The pid will remain the same if you run your program via a script with exec
So you can make a wrapper script that generates the rules using its pid,
feeds them to awesome-cl
On 2013-04-26, Andre Klärner wrote:
> just a small question: if you don't want to use static rules, why don't you
> "compile" the just before launching and feed them to awesome via
> awesome-client? That way they don't exist in the config and you have only
> to maintain within your launcher the ru
