Bug 404212 - Most recent document not remembered in quick document selector
Summary: Most recent document not remembered in quick document selector
Status: RESOLVED DUPLICATE of bug 407103
Alias: None
Product: kate
Classification: Applications
Component: application (show other bugs)
Version: 18.12.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-11 20:26 UTC by Gregor Petrin
Modified: 2019-07-13 19:16 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Petrin 2019-02-11 20:26:45 UTC
SUMMARY

The quick document selector no longer selects documents in the least-recently-used order. If I switch to another document, then activate quick selector and press enter, I get a blank document. I should get the previous document, as per documentation at https://docs.kde.org/trunk5/en/applications/kate/kate-application-plugin-projects.html : "Further, the quick open remembers the previous file. So when you change to the quick open view the previously activated file is automatically selected and you just need to hit Enter, which comes very handy at times."


STEPS TO REPRODUCE
1. Open document A
2. Open document B
3. Activate quick document selector
4. Choose first option by pressing "Enter"

OBSERVED RESULT

A blank document is displayed


EXPECTED RESULT

Document A should be displayed.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.14
KDE Frameworks Version: 5.54.0
Qt Version: 5.12.0
Comment 1 Patrick Silva 2019-03-26 19:07:47 UTC
I can confirm with kate 18.12.3. No document is selected when quick document selector is activated (ctrl+alt+o), so an empty document is created when we press enter.

Operating System: Arch Linux 
KDE Plasma Version: 5.15.3
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2
Comment 2 Christoph Cullmann 2019-07-13 19:16:54 UTC
This got fixed thanks to a patch!

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