| Summary: | Line ending not correctly saved after pasting content | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Adam Pigg <adam> |
| Component: | part | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 5.62 | |
| Sentry Crash Report: | |||
| Attachments: | Screenshot of vi showing char | ||
Fixed in KDE Frameworks 5.62. *** This bug has been marked as a duplicate of bug 410951 *** |
Created attachment 123018 [details] Screenshot of vi showing char SUMMARY When working with a file using unix line endings, if I paste in text from a browser, the line ending in the pasted text may be windows. When saving the file the file, this is not corrected, it is also not visible to the user. STEPS TO REPRODUCE 1. Work on a .spec file 2. When building package on OBS, get a failure due to unpackaged files 3. Paste the unpackaged file list in to the .spec and clean up paths 4. Save .spec and trigger a new build 5. Become frustrated when OBS complains about missing file, but when you look for it in the .spec it is there, but with a ^M char after it OBSERVED RESULT File contains rogue ^M chars EXPECTED RESULT File either has no ^M char, or, kate displays the rogue characters to the user to manually remove SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse tumbleweed (available in About System) KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1