mortdeus / wmii

Automatically exported from code.google.com/p/wmii
MIT License
0 stars 0 forks source link

Some clients cannot be launched in new tags #242

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Open some clients in a tag (e.g. tag 1). Then open a new tag (e.g. 3).
2. Launch a client in tag 3, e.g. Chromium, Firefox or GQview.

What is the expected result? What do you see instead?

The client is opened in the last populated tag. So it's opened in tag 1, not in 
tag 3.

What version of the product are you using (wmii -v)? On what operating
system (uname -a)?

$ wmii -v
wmii-hg2793, ©2010 Kris Maglione

$ uname -a
Linux Adamantium 3.0-ARCH #1 SMP PREEMPT Tue Aug 30 08:53:25 CEST 2011 x86_64 
Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz GenuineIntel GNU/Linux

Please provide any additional information below.

This behavior was introduced by changeset 7921fa9d5f7c. I cannot reproduce this 
with some clients like urxvt.

Original issue reported on code.google.com by jpabl...@gmail.com on 17 Sep 2011 at 8:28

GoogleCodeExporter commented 9 years ago
Clients open in the same tag as the other clients in their group 
by default. If you want to override it for some windows, use 
/rules:

  /^Chromium:/ force-tags=sel

Original comment by maglion...@gmail.com on 17 Sep 2011 at 8:32

GoogleCodeExporter commented 9 years ago
OK. However note that this is also reproduced as follows:

1) Open 2 urxvt clients in tag 1.
2) Try to open Chromium in tag 3 for the first time.

Is Chromium considered as in the same group as urxvt in this case?

Original comment by jpabl...@gmail.com on 17 Sep 2011 at 8:37

GoogleCodeExporter commented 9 years ago
Comment #2 on issue 242 by jpabl...@gmail.com
> OK. However note that this is also reproduced as follows:
> 
> 1) Open 2 urxvt clients in tag 1.
> 2) Try to open Chromium in tag 3 for the first time.
> 
> Is Chromium considered as in the same group as urxvt in this case?

No, not unless there's another open Chromium window you don't 
know about. You probably have an issue with your /rules.

Original comment by maglion...@gmail.com on 17 Sep 2011 at 8:43

GoogleCodeExporter commented 9 years ago
I can confirm there are no other open Chromium or GQview clients. As for the 
/rules, I've retested this with the default ones:

$ wmiir read /rules
/^Pidgin:/ allow=+activate
/MPlayer|VLC/ floating=on
/^ROX-Filer:/ group=0

I can reproduce this in 2791:7921fa9d5f7c but not in 2790:95951abe29c5 (I'm 
using the p9p wmiirc). I've also verified it using a default wmiirc with no 
local customizations.

Original comment by jpabl...@gmail.com on 17 Sep 2011 at 8:55

GoogleCodeExporter commented 9 years ago
Well it works for me, so unless you can find some reliable way 
of reproducing this, it stays Invalid.

Original comment by maglion...@gmail.com on 17 Sep 2011 at 9:03

GoogleCodeExporter commented 9 years ago
Fair enough. This changeset fixes the issue for me: http://dpaste.org/6iENp/raw/

Original comment by jpabl...@gmail.com on 17 Sep 2011 at 9:42

GoogleCodeExporter commented 9 years ago
This issue was closed by revision e4739e15343d.

Original comment by maglion...@gmail.com on 19 Sep 2011 at 7:49