Bug 246172

Summary:	kate session launch replaces existing kate session
Product:	[Plasma] krunner	Reporter:	Diggory Hardy <kde2>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	minor	CC:	justin.zobel
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Diggory Hardy 2010-07-29 17:21:07 UTC

Version:           unspecified (using KDE 4.4.4) 
OS:                Linux

When I launch a kate session via krunner by typing in the session name, it will:
1. if this session is already open in kate, switch to it
2. if another kate session is open, replace this session (use existing kate instance)
3. start kate with the session

I would prefer it if case 2. had the same behaviour as case 3. (i.e. create a new kate window, leaving other open sessions alone), since:
* if I have a temporary session open in kate which gets replaced, this session is lost (all documents must be reopened again)
* it's often useful having multiple sessions open, and closing unwanted ones is easier than explicitly opening a new window then opening the session (besides, RAM limits aren't usually a problem with kate anymore)

Reproducible: Always

Comment 1 Andrew Crouthamel 2018-11-05 03:09:25 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 2 Andrew Crouthamel 2018-11-16 05:37:39 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!

Comment 3 Justin Zobel 2020-12-02 04:03:00 UTC

Thank you for the report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thank you.

Comment 4 Bug Janitor Service 2020-12-17 04:33:54 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2021-01-01 04:39:16 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!