It happens with everything. I just used Inkscape for testing purposes as I was trying a more complicated rule matching instance and class which is where I noticed the problem.
Sent from TypeMail On 20 Sep 2015 12:21, at 12:21, Uli Schlachter <psyc...@znc.in> wrote: >Hi, > >Am 18.09.2015 um 10:18 schrieb Fran Thomson: >[...] >> { rule = { class = "Inkscape" }, >> properties = { tag = tags[2][2], }, >> } >> >> and >> >> { rule = { class = "Inkscape" }, >> callback = function (c) c:tags({tags[2][2]}) end >> } >> >> If I change the first index of tags[2][2] to tags[1][2] it'll show on >screen 1, >> and vice versa. But it's ignoring the second index - it always shows >on the tag >> that's displaying at the time. >[...] > >does this only happen with Inkscape? I would test with something like >xterm or >urxvt and if these work, then either your rule doesn't match inkscape >(you can >test with callback = function(c) naughty.notify{ text = c.name } end) >or >inkscape is interfering (you could try looking through its options and >check if >it has something like "Remember window position" that you can turn >off). > >Cheers, >Uli >-- >A normal person is just someone you don't know well enough yet. > - Nettie Wiebe > >-- >To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.