Bug 358415 - Caret return character screws up text on the same line
Summary: Caret return character screws up text on the same line
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: outputview (show other bugs)
Version: 4.90.90
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords: triaged
: 358417 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-01-23 11:21 UTC by Alexander Potashev
Modified: 2019-01-07 23:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot (72.34 KB, image/png)
2016-01-24 09:28 UTC, Alexander Potashev
Details
screenshot (18.62 KB, image/png)
2018-11-03 19:34 UTC, Alexander Potashev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Potashev 2016-01-23 11:21:43 UTC
'\r' character is not supported in the outputview in KDevelop. It does not work as "caret return", and also it shifts the baseline of the other text up by ~80% of the line height making it unreadable.

Reproducible: Always
Comment 1 Milian Wolff 2016-01-23 17:44:32 UTC
*** Bug 358417 has been marked as a duplicate of this bug. ***
Comment 2 Milian Wolff 2016-01-23 17:50:17 UTC
I can't reproduce this, can you attach a file to reproduce this? Also please show a screenshot.

I used this file for testing:

echo -e "just n:\nr and n:\r\njust r:\rlast line" > /tmp/testBug358415

and then added an "external script" into KDevelop which just executes "cat /tmp/testBug358415". The output view shows the expected lines just fine for me.
Comment 3 Alexander Potashev 2016-01-24 09:28:31 UTC
Created attachment 96808 [details]
screenshot

The above "echo ..." command has the same effect like I had with a C++ program, see the screenshot.
Comment 4 Milian Wolff 2016-01-24 12:21:21 UTC
Are you running the latest kdevelop git (i.e. 5.0 or master) code? Or is this the 5.0 beta 1 release? There were some changes in that area to make it behave better under windows, so I think/hope it got fixed then. If you are running 5.0 from git, then we'll need to figure out why this breaks for you but works fine for me...
Comment 5 Milian Wolff 2016-01-24 12:21:39 UTC
also: what Qt version do you have?
Comment 6 Andrew Crouthamel 2018-09-25 21:40:00 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-10-27 02:25:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 8 Alexander Potashev 2018-11-03 19:33:26 UTC
Now the "\r" is ignored, see new screenshot. IMO it should act as a line break, exactly like "\n", etc.
Comment 9 Alexander Potashev 2018-11-03 19:34:25 UTC
Created attachment 116069 [details]
screenshot

OS: Fedora 28
kdevelop 5.2.3
kdevplatform 5.2.3
KDE Frameworks 5.48.0,
Qt 5.11.1 (собрана с версией 5.11.1),
Оконная система xcb.
Comment 10 Alexander Potashev 2018-11-16 11:50:23 UTC
(In reply to Andrew Crouthamel from comment #7)
> Dear Bug Submitter,
> 
> This bug has been in NEEDSINFO status with no change for at least 30 days.
> The bug is now closed as RESOLVED > WORKSFORME due to lack of needed
> information.
> 
> For more information about our bug triaging procedures please read the wiki
> located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
> 
> Thank you for helping us make KDE software even better for everyone!

Hi Andrew,

I think this report should be reopened according to my comments #8, #9. Could you please automate reopening of bugs for this case that were closed on the 30-day timeout? I'm afraid many bug report may be lost due to such random closures.
Comment 11 Alexander Potashev 2019-01-07 23:00:02 UTC
ping?