Bug 378699

Summary:	Should open file dialog with the current file's folder
Product:	[Applications] kate	Reporter:	Victor Porton <porton>
Component:	application	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	alexander, Darren.Lissimore
Priority:	NOR
Version:	17.04.2
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Victor Porton 2017-04-12 14:28:01 UTC

Earlier when I clicked "Open" while editing a file over SSH or FTP, the server folder with that file was automatically opened.

Now (Kate 16.08.3) it opens another folder (probably the current dir at which Kate was started).

Please return back the old behavior.

Comment 1 Victor Porton 2017-04-16 14:46:26 UTC

Note that I start Kate with

XDG_CURRENT_DESKTOP=KDE

and use the KDE Open and Save dialogs.

Comment 2 Victor Porton 2017-04-16 15:28:29 UTC

The bug happens for both Open and Save dialogs.

Comment 3 Alexander Zhigalin 2017-06-10 11:04:29 UTC

I cannot reproduce it on 
Kate 17.04.2
KDE Frameworks 5.35.0,
Qt 5.7.1
Do you still experiencing this issue?
Which versions are you using?

Comment 4 Darren Lissimore 2017-06-12 06:33:23 UTC

Yes - it's occurring for me. 
Kate 17.04.2
KDE Frameworks 5.35.0
Built against Qt 5.7.1 
Using kde-neon developer-stable release - fully updated. 

Symptoms: 
- From a session 2 files - one local - and one via fish. 
- Select the local file - request a file-open (toolbar or menu) you get the file's directory 
- Select the fish'ed file - request a file-open (toolbar or menu) you get the user's home directory.
 
I grabbed the latest kate code from git - and traced the open call to QFileDialog static function getOpenFileUrls() under the KateViewManager::slotDocumentOpen() .  That does get the fish'ed file's url for the dir parameter ... but dialog ends up with users home directory.

Note - this bug and 374296 seem to be the same issue.

Comment 5 Alexander Zhigalin 2017-06-12 06:44:04 UTC


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