Bug 473077 - Kate and kwrite with vi mode enabled incorrectly reports that file saved successfully when clicking cancel in file save dialog
Summary: Kate and kwrite with vi mode enabled incorrectly reports that file saved succ...
Status: CONFIRMED
Alias: None
Product: kate
Classification: Applications
Component: Vi Input Mode (other bugs)
Version First Reported In: 23.04.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-06 17:40 UTC by cdw1978
Modified: 2023-08-09 22:56 UTC (History)
1 user (show)

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

Attachments
Screen capture of incorrect status (26.42 KB, image/png)
2023-08-06 17:40 UTC, cdw1978 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description cdw1978 2023-08-06 17:40:11 UTC 
Created attachment 160779 [details]
Screen capture of incorrect status

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Open Kate/Kwrite and enable vi mode
2.  enter :w and press enter
3.  Cancel the dialog box

OBSERVED RESULT
Status bar reads "Success: Document written to disk"

EXPECTED RESULT
No text in status bar, or a message stating no file was saved

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.27.7
(available in About System)
KDE Plasma Version:  5.27.7
KDE Frameworks Version:  5.108.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
Comment 1 Christoph Cullmann 2023-08-06 18:21:09 UTC 
If you have interest, a patch to fix that is welcome.
Comment 2 cdw1978 2023-08-09 22:56:59 UTC 
(In reply to Christoph Cullmann from comment #1)
> If you have interest, a patch to fix that is welcome.

Hello,

Unfortunately, software development is far from my area of expertise and most likely any attempt I made to fix the issue would either break things more or break something else in the process.  I was simply reporting an observation of a (minor) bug.  One other note: I also confirmed this happens on Windows as well.