Bug 318450 - Selecting by double click at end of line should stop at the last character of the line instead of the last printable character
Summary: Selecting by double click at end of line should stop at the last character of...
Status: CONFIRMED
Alias: None
Product: konsole
Classification: Applications
Component: copy-paste (show other bugs)
Version: 2.10.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-16 14:30 UTC by Yichao Yu
Modified: 2021-03-11 03:17 UTC (History)
0 users

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 Yichao Yu 2013-04-16 14:30:00 UTC
See detail below.
The problem is on double click selecting, the end of line instead of the end of visible line should be treated as a break. Some what related to bug #318449. (I report them separately since they are not exactly the same....)

An option for triple click for whether selection the newline should also be added once this bug is fixed.


Reproducible: Always

Steps to Reproduce:
1. echo 'a'
2. echo 'b          '
3. double click the "a" printed
4. double click the space after the "b" printed
5. double click the end of the printed "a" line
6. double click the end of the printed "b" line

Actual Results:  
3: "a" selected (as expected)
4: all spaces after "b" as well as the newline are selected
5: the newline after "a" is selected (as expected)
6: all spaces after "b" as well as the newline are selected


Expected Results:  
4: all spaces after "b" are selected (but not the newline)
6: the newline at the end of the "b" printed line is selected
Comment 1 Kurt Hindenburg 2014-02-15 23:56:33 UTC
Yes, the spaces after the b are 'ignored'
Comment 2 Justin Zobel 2021-03-11 01:23:52 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 3 Yichao Yu 2021-03-11 03:17:19 UTC
Yes, this is still an issue.