Bug 417201 - When double-clicking on an associated file, a new instance of Kate is started rather than a new tab within an already-running instance. Furthermore, when the new instance is closed, a kate.exe process is left behind.
Summary: When double-clicking on an associated file, a new instance of Kate is started...
Status: RESOLVED MOVED
Alias: None
Product: kate
Classification: Applications
Component: application (show other bugs)
Version: 19.12.1
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-05 17:41 UTC by Mark Gibb
Modified: 2020-02-10 08:24 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Gibb 2020-02-05 17:41:50 UTC 
SUMMARY
When double-clicking on an associated file, a new instance of Kate is started rather than a new tab within an already-running instance.  Furthermore, when the new instance is closed, a kate.exe process is left behind.

STEPS TO REPRODUCE
1. Open a document in Kate
2. In File Explorer, double-click on a file associated with Kate
3. 

OBSERVED RESULT
New Kate window and instance is started to display the second file.

EXPECTED RESULT
I would prefer the second document to open as a second tab within the current instance.  That is how Kate works when I am on Linux.

SOFTWARE/OS VERSIONS
Windows: Windows 10 Enterprise, version 1809, build 17763.973

ADDITIONAL INFORMATION
The version that works for me on Linux is very old, 3.14.8
Comment 1 Dominik Haumann 2020-02-06 23:05:46 UTC 
I believe this was fixed 4 days ago:
https://invent.kde.org/kde/kate/merge_requests/61
Comment 2 Mark Gibb 2020-02-08 22:47:03 UTC 
Thank you Dominik.  It says it was merged into Master.  Does that mean it has been put into a release?  On Friday, I downloaded the most recent release build and the problem still occurred.
Comment 3 Christoph Cullmann 2020-02-09 15:00:36 UTC 
Which build did you try?
Today e.g. the one on https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/ should contain the fix.
Comment 4 Mark Gibb 2020-02-10 01:13:01 UTC 
Hi Christoph.  I don't remember the exact build for the case where I thought the bug was still there (not at that computer at the moment).  However, I downloaded 19.12.2-769 and the problem is fixed in that build.  So all good.

Thank you!
Comment 5 Christoph Feck 2020-02-10 08:24:44 UTC 
Issue was reported and fixed, see https://invent.kde.org/kde/kate/issues/6