Thanks Uli,
>
> Am 20.09.2015 um 13:25 schrieb Fran:
> > 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.
> [...]
>
> Ok, another quick idea: Move it to screen 2 first.
>
> callback = function(c)
> c.screen = 2
> c:tags({tags[2][2]})
> end
>
No luck I'm afraid, it still just appears on the first tag on screen 2.
My rules definitely seem to be obeying the screen bit. When I restart
awesome to test, clients that I'd moved move back to the first tag on
the screen they should be on (so for example my URxvt running mutt,
which should be on tag 2 of screen 1, moves back to tag 1 of screen 1
whenever I restart awesome).
Could the fact that I'm running nvidia proprietary drivers make any
difference to awesome tags? (Although I guess if they were going to
affect anything they'd affect the screen as well?)
Fran
--
To unsubscribe, send mail to [email protected].
