Closed GoogleCodeExporter closed 9 years ago
As I remember, this has been reported several times as a bug, but is intended
behavior.
You are wrong that this happens with new instances of programs. It happens with
new
windows of already running applications. If you call "firefox" when a firefox is
already running, a new window of that instance is invoked. You may verify this
by
calling "firefox -no-remote", which should open a new instance, but then this
does
not work since Firefox allows only one instance (what a weird option then...).
I was annoyed by the same thing happening with acroread. If you happen to have
acroread installed, you can verify this. acroread by default also opens new
windows
of an already running instance (which are then collected on the view/tag where
the
first acroread got launched), but calling "acroread -openInNewInstance" lets
you open
new instances.
Original comment by skwi...@googlemail.com
on 21 Jan 2010 at 1:56
It sounds like my verbiage was wrong. Especially considering what you described
matched closer to what I was trying to say!
I am thinking about branching as the behavior makes wmii nearly unusable for me. I'm
always bringing up terminals to do various impromptu operations that require a
terminal. I can think of a few nifty ways around the new short comings, but I
think
they are just that; short comings.
If so many people have reported it as a bug, perhaps it should be looked at
that way.
Sometimes a new feature just doesn't work out for the user.
It drove me absolutely crazy. I eventually rolled back to 3.6 after it started
hitting my productivity at work. I gave it a fair chance and I've concluded I
just
can't live with the change.
Original comment by October...@gmail.com
on 21 Jan 2010 at 2:59
Kris was not around for a long time, he will be able to explain why it works
this way.
If you have good reasons to use gnome-terminal over urxvt or xterm, try
"gnome-terminal --disable-factory" which starts new instances instead of new
windows.
xfce4-terminal will probably have a similar option.
Original comment by skwi...@googlemail.com
on 22 Jan 2010 at 1:15
Ah, I misunderstood before. We weren't saying the same thing. It just so
happens that
the applications I use just open new windows when you execute their command,
instead
of a new instance? hmm... If I am ever compelled to upgrade again, I will at
least
give what you described a shot before jumping ship. Thank you for the help.
Original comment by October...@gmail.com
on 22 Jan 2010 at 1:42
New windows open with the same tags as their window group. This is the standard
behavior of most window managers, and is the expected behavior >90% of the
time. I
don't know of any terminals which set a window group, which seems an entirely
untoward behavior. The only reasonable workaround I can see is to use either
wihack
(included with wmii) or Freedesktop's launch notification, which is fairly
perverse
in that it requires dot-desktop files.
At any rate, Suraj's ruby wmiirc (included with wmii) overrides the stock
behavior.
Original comment by maglion...@gmail.com
on 23 Jan 2010 at 1:11
This issue was updated by revision 54c9b922e2.
You can work around this by adding something like the following to
your /tagrules:
/terminal/ -> sel # Ignore terminal window groups.
Original comment by maglion...@gmail.com
on 23 Jan 2010 at 1:56
This issue was closed by revision 54c9b922e2.
Original comment by maglion...@gmail.com
on 23 Jan 2010 at 1:56
I would like just to thank you for fixing this issue and confirm that is
working with
revision 5973799cd90a. Now pcmanfm and evince work as expected! No more
"infinite"
waiting for program to open (while it was already opened in another view).
Original comment by marco.rucci
on 13 Feb 2010 at 2:43
Original issue reported on code.google.com by
October...@gmail.com
on 15 Jan 2010 at 3:34Attachments: