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-client, then exec the actual program However, the awesome ruleset would grow a lot with this method, wouldn't cleaning such generated rules be necessary ? I don't think this is so easy, but maybe with a timeout, or auto-cleaning the rule when it has been applied to a window, is possible ? (this exeeds my awesome configuration knowledge) 2013/4/27 Daniel <qu...@hack.org> > On 2013-04-26, Andre Klärner <kan...@ak-online.be> 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 ruleset how to match your starting > > app. > > Ah, that's an nice idea. Though I wonder what the rule should filter on; > class and instance would be identical in different instances of the same > program. WM_NAME is the filename of the document, which could be enough. > But then those rules would be around indefinitely, and might be a > nuisance later on, when programs may be restarted, tag set different, > etc. > > > -- > To unsubscribe, send mail to awesome-unsubscr...@naquadah.org. > -- Vivian Brégier http://www.are-ata.org/Vivian.vcf
