Bug 99084 - kfmclient newTab option not obeyed when Konqueror instance is not on the current desktop
Summary: kfmclient newTab option not obeyed when Konqueror instance is not on the curr...
Status: RESOLVED DUPLICATE of bug 66575
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.3.2
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-11 01:42 UTC by Frisb Com
Modified: 2005-02-11 11:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frisb Com 2005-02-11 01:42:42 UTC
Version:           3.3.2 (using KDE KDE 3.3.2)
Installed from:    Compiled From Sources
Compiler:          gcc 3.3.5 -O2
OS:                Linux

Open konqueror on virtual desktop 4.  On desktop 1, type kfmclient newTab http://www.slashdot.org.  Instead of a new tab on the konq. in desktop 4, a new konqueror is opened on desktop 1. (the same is true for minimized konquerors as well)

This is discussed briefly in 66575 as an aside. The developer mentions that s/he meant for the newTab function to behave in this manner. While this may be what some people want, I for one have gotten accustomed to having this ability with firefox and would greatly appreciate its addition to konqueror.  Perhaps --forceNewTab would be appropriate, but I think the behavior I desire is better described with the --newTab option, while the current behavior would be better suited with an --smartNewTab option. ;)

(I'm just switching from firefox, and this is the last of the abilities that I haven't found a replacement/match for in konqueror.  Keep up the good work!)
Comment 1 Stephan Binner 2005-02-11 11:13:16 UTC

*** This bug has been marked as a duplicate of 66575 ***