Bug 174774

Summary:	[konsole] Regression: Different selection behaviour
Product:	[Applications] konsole	Reporter:	Richard Hartmann <richih-kde>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	johnvarouhakis, robertknight
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Unspecified
Latest Commit:		Version Fixed In:

Description Richard Hartmann 2008-11-10 12:51:27 UTC

Version:            (using KDE 4.1.2)
Installed from:    Debian testing/unstable Packages

In Konsole 1.x, I can select text, switch tabs and the selection is gone. Switch back to the tab in question and I see the selection again.

In Konsole 2.x, I select text, switch tabs and the selection is still overlayed over the region that was selected in the other tab. Extremely confusing.



Also, when text is scrolling and you select, Konsole 1.x will move the selection upward with the text you selected originally.

Konsole 2.x will keep the selection over whatever happens to have scrolled into place in the meantime.

Comment 1 Richard Hartmann 2009-01-15 07:03:21 UTC

Confirmed for 4.1.96.

As stupid as this may sound, this change makes the KDE (and all other) channels on freenode unsafer than they were when I was still using 3.5.x as klining bots takes me _considerably_ more time due to mis-selecting and the need to triple-check my selections.

I would be happy with a config option though, obviously, I would prefer to get the old behaviour back.

Comment 2 Robert Knight 2009-01-15 16:04:32 UTC

I can't reproduce the first bug outlined here or the second one.  I couldn't get a friend with KDE 4.1 in Debian to reproduce this either.  Just to check that we're both trying the same thing:

Steps I tried:

1.  Open two tabs
2.  Select a region of text in tab A
3.  Switch to tab B -> observe no selection
4.  Select a region of text in tab B
5.  Switch back and forth between the two tabs -> observe that the selection is preserved in both tabs

I'm a bit mystified as to why it might happen since the selection information is stored entirely within the terminal display widget itself and each tab has its own widget.

Comment 3 Bernd Wurst 2009-05-16 18:08:53 UTC

I can confirm that this bug is not present with the mentioned steps to reproduce.

I cannot reproduce the given errors on KDE 4.2.3.