Version: 1.2.1 (using KDE 3.1.1) Installed from: SuSE Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB It is impossible to copy filenames from the konsole window by selection with the mouse when they continue onto the next line. The clipboard then contains a newline, which when pasting causes nothing but trouble. Obviously there are cases where the newlines are needed (selecting a list of whole lines), some intelligence in handling this is needed. xterm gets this right. Dunno what xterm algorithm is, but when I select by character or by word, I hardly ever want the newlines. Especially not mid-word, like in filenames.
Bug seems to be a duplicate of Bug 69403or vice versa.
Duplicate #69403 has more votes. *** This bug has been marked as a duplicate of 69403 ***
duplicate of bug 69403? Um... how? :-)
See discussion on bug 89299 (a related but different issue); we need a way to make it easier to not select the trailing newline, otherwise someone will always be unhappy. Probably there should be a way to suppress it outright (e.g. modifier key). But we should keep Old Farts like me happy by making it easy to still get the final newline. Personally, I like adding a threshold so one must be more purposeful about getting the final newline rather than getting it if hovering just a hair past the last character.
@ Matthew: This bug is actually about a different issue than the one we're discussing. It is indeed a duplicate of Bug 69403 if you read closely. This bug appears to be about selecting wrapped output and having it copied as multi-line, and it appears to be resolved. (Wrapped output from ls and ls | less seems to be selected fine, vim text has trouble but holding Ctrl while selecting resolves it. See Bug 69403) We are discussing the way Konsole 1.6.6 selects the newline if you extend the cursor past the last character on a line (which frustrates me and Sebastian but makes life easier for you apparently) but Konsole 2 doesn't do this. This is Bug 152774. Lets continue discussing there.
Hmm... ok, guess I did read wrong. However bug 152774 didn't start out as dealing with selecting the newline in the first place (though I see you're trying to transmute it to that effect). Personally, I'd open a new bug, but I'm willing to see what others think about repurposing bug 152774. *** This bug has been marked as a duplicate of 69403 ***