Bug 202210

Summary: kate --use --start SESSION doesn't work well
Product: [Applications] kate Reporter: Mildred <silkensedai>
Component: generalAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Mildred 2009-08-01 15:43:46 UTC 
Version:           3.2.4 (using KDE 4.2.4)
OS:                Linux
Installed from:    Fedora RPMs

When I use --use and --start option to start kate, and if the session specified using --start is the same as the current session, all current files are closed and the files specified on the command line are opened.

Since the current session is the same as the session specified on the command line, I would except that the files opened in that session would stay open instead of disappearing. In few words, I except the following command line to append files in the session instead of replacing them:

kate --use --start SESSION FILE

If you want to test, just run the following commands:

touch a
touch b
touch c
kate --use --start test a &
kate --use --start test b &

First, the a file is opened, that's expected.
Then, when kate open b, a is closed.



------



Now, if we have two kate instances, --use always use the first instance. It should instead use the instance that has the session specified by --start opened if there is any.

Now, do the following test:

kate --start test1 &
kate --start test2 &

You have two instances

kate --use --start test1 a &

the file 'a' is opened in the first instance that has the session test1 running

kate --use --start test2 b &

Instead of opening the 'b' file in the second instance that has the session test2 running, the first instance closes the session test1, open the session test2 and open the file 'b'.

kate --use --start test3 c &

Now, I suppose the best behaviour would be to open a new instance of kate and create the session test3 instead of replacing the session in the first instance. I think that was the behaviour a while ago (when Kate still used DCOP, KDE3 I think)
Comment 1 Joseph Wenninger 2009-09-19 18:24:28 UTC 
SVN commit 1025768 by jowenn:

Do not reload the session if it is already opened, just raise the window.

kate --start session1	         (same as --use)
kate --start session1            just raise the opened session (same as --use)
kate --start session2            raise instance and open new sessoin (same as --use)
kate -n --start session3         start a new instance and open tne new session
kate -n --start session4         start a new instance and open tne new session
kate -n --start session3         raise instance of session3.

kate -n --start session3  somefile
kate  --start session3  somefile2        (same as --use)
behave the same if an instance of session3 is already opened and open the two files in that instance
if before -n only another instance, eg session2 is opened than a new instance is opened with session3

--> only one instance of one specific session possible
--> there can be more instances running, each having an own session (-n)

I think that's the most sane behaviour

BUG:202210

 M  +3 -1      katemain.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1025768