0

Sometimes you want to paste some text on the console or a chat window but you didn't know that it has an enter \n inside on it and it caused alot of trouble because you wanted to edit first.

Solutions:
- Popup a notification about \n inside the clipboard when you want to paste
- Let user to choose to filter \n or not and paste
- Let user to edit the clipboard (I think Klipper actually lets you do this)

Even better if the user have the chance to modify and add its own blacklist of text, words, characters, etc

can you not do this yourself with the "add actions" option

if I understand this right, I can add an acction to trigger whan clipboard has an \n and execute an app that can popup the notification and do the replacement of the clipboard content or not.

Well, I was thinking in an improvement in the UX, so this mean having this functionality out of the box with KDE

@Bill
He wants to fixup

Code: Select all

#rm -rf ~/*\n~

which he probably copied from some webpage which "accidentally" injected a linebreak (for rendering)
to

Code: Select all

#rm -rf ~/*~

if I understand this right, I can add an action to trigger when clipboard has an \n and execute an app that can popup the notification and do the replacement of the clipboard content or not.

Semi (you don't have to execute some app for the popup, that's built in) - however this behavior was seriously no UX improvement at all. On the contrary.
Do you really always want a popup everytime when you select some text that contains a newline?

Regardless of whether what you want to do is reasonable - how you want to do it is wrong (and unlikely what you originally wanted)

Background:
-----------------
a) klipper "only" manages the primary and secondary selection buffer ("the mouse and keyboard clipboards")
b) when something enters the buffer, the actions allow you to automatically perform some action on it - this would allow to eg. strip all selections from \n by eg. piping it through sed, but the intention is to prevent accidental command entering, ie. stripping only when pasting to a shell.
c) klipper has no control on what happens w/ the buffer when it's read by the client (konsole)
d) klipper is not mandatory - it's nice to have, but you can kill/suspend/block it for konsole and paste your newline entering clipboard into konsole

=> iff this was to be done at all, it would have to be done by the client.
The konsole part needed to detect the newline and offer to strip it or transfer it into a "dead" CRLF (as if you had entered Alt+Enter)
It must be offered, as konsole may run sth. entirely else, like eg. vim, and one would be very annoyed if all stuff was suddenly pasted in a single line.


Semi OT, my 2¢:
Do not copy random stuff into an interactive shell. NEVER.
That's just dangerous.
Eg. the selection could contain a shellbomb out of non-printable characters, build an rm command and whatnot.
If you're not absolutely sure what you copied: don't paste it into an interactive shell. Period.

luebking wrote:@Bill
=> iff this was to be done at all, it would have to be done by the client.
The konsole part needed to detect the newline and offer to strip it or transfer it into a "dead" CRLF (as if you had entered Alt+Enter)
It must be offered, as konsole may run sth. entirely else, like eg. vim, and one would be very annoyed if all stuff was suddenly pasted in a single line.

Semi OT, my 2¢:
Do not copy random stuff into an interactive shell. NEVER.
That's just dangerous.
Eg. the selection could contain a shellbomb out of non-printable characters, build an rm command and whatnot.
If you're not absolutely sure what you copied: don't paste it into an interactive shell. Period.

I like this feature to be included inside konsole. Obviously this has to be offered and also with a checkbox to not notify it again and a checkbox in the configuration to enable/disable.

I know we all have to behave with care.. but well.. we are humans, so I think it's nice to have a smart environment.