Are you talking about the "Clipboard" plasma applet or really klipper?
This is similar to the plasma-pa/kmix situation, where there is a new plasma applet to do the major functions of the prior systray application.
If it is indeed "Clipboard applet", you could consider disabling it, and using the classic klipper instead, particularly if it works better for your use-cases.
-- Rex
________________________________________ From: Reindl Harald h.reindl@thelounge.net Sent: Tuesday, November 24, 2015 8:20 AM To: Mailing-List fedora-kde Subject: klipper in Fedora 23 *argh*
am i the only only where clipper indepedent of the options you use replaces the clipboard with the current selection which is braindead when you select the text you want to replace with CTRL+V
BTW: currently in konqueror in need to use "copy" for files twice because after the first attempt it asks for a name and tries to paste the clipboard instead the files from the other tab/instance
Am 24.11.2015 um 16:03 schrieb Rex Dieter:
Are you talking about the "Clipboard" plasma applet or really klipper?
This is similar to the plasma-pa/kmix situation, where there is a new plasma applet to do the major functions of the prior systray application.
If it is indeed "Clipboard applet", you could consider disabling it, and using the classic klipper instead, particularly if it works better for your use-cases.
indeed it's a applet and klipper did not run
but how to disable it entirely?
in the systray settings it looks like it can only be hidden, but CTRL+C/CTRL+V act the same way as before even without have klipper started, well, i restarted plasma at a whole and added klipper manually to the autostarts
why can the kde-developers not just stop to ruin working things all the time?
[root@rh:~]$ cat /scripts/restart-plasma.sh #!/usr/bin/dash # killall -s SIGSEGV plasmashell killall plasmashell /usr/bin/plasmashell &
________________________________
From: Reindl Harald h.reindl@thelounge.net Sent: Tuesday, November 24, 2015 8:20 AM To: Mailing-List fedora-kde Subject: klipper in Fedora 23 *argh*
am i the only only where clipper indepedent of the options you use replaces the clipboard with the current selection which is braindead when you select the text you want to replace with CTRL+V
BTW: currently in konqueror in need to use "copy" for files twice because after the first attempt it asks for a name and tries to paste the clipboard instead the files from the other tab/instance _______________________________________________ kde mailing list kde@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org
Il 24/11/2015 16:11, Reindl Harald ha scritto:
why can the kde-developers not just stop to ruin working things all the time?
Because <rant> they fail to grasp that the computer Desktop was originally intended as a metaphor for the top of the desk you're sitting at. That is an empty workspace, which each user populates according its needs and its taste, with the documents he needs at the moment, and the applications he uses more frequently. The best way to implement it is just a folder, as it used to be in the good old times. Anything more elaborated is a source of instability and bugs, without serving any useful purpose for the vast majority of users. For stable, consistent and useful usage, nothing should be "integrated" into the desktop, because each user has different needs and they may change day by day. If you try to integrate everything you build up a monster, if you integrate just something, chances are good that what you deem useful is useless for everyone else. But they conceived that foolish thing that is the Plasma environment, which is nothing but a bloated systray taking all the screen, populated by Plasmoids, which are nothing but bloated (and usually buggy) applets, which take a lot of space, instead of being a few small Icons on the system tray. They try to index your files when you don't need it, and in this way they slow down your workflow, in order to keep track of a few passwords, in place of a simple encrypted list they use a mysql database, which subtracts resources to your useful activities, and gets into the way if you're using mysql for some other useful purpose, etc. etc.
Moreover they failed from the beginning to follow sound design rules. They're rightfully using the Qt widgetset which is good, and provides the pleasant look which is the reason to select KDE, but they failed to take into account that Qt evolves. The only reasonable way to deal with an evolving widgetset is to provide an abstraction layer, isolating the Desktop applications from the WS. The abstraction layer provides a number of API's related to the functions required by the desktop applications, and implements them in the current Qt context. That way changing from let's say Qt4 to Qt5 is just a matter of rewriting the abstraction layer, leaving all the applications unchanged, and keeping all the previous features. Then, with time, new features can be added to take advantage of what the new Qt provides. But they didn't do it that way. It would appear that they always restart from scratch. KDE1 already had all that's required from a desktop. But it took until KDE 2.3 to get the same features. Then it took until KDE 3.5 to get all the features of KDE 1. I'm currently using KDE 4.3.4 (CentOs 6), and I still find it a significant regression with respect to KDE 3.5. The newer versions I've tested seemed to have added new bugs instead of eliminating the old ones.
It would be a pity to leave KDE forever, but if the kde developers continue on their way, I'm afraid that I'll be forced to take a different road. </rant>
Giuliano
Il 24/11/2015 16:11, Reindl Harald ha scritto:
why can the kde-developers not just stop to ruin working things all the time?
Because <rant> they fail to grasp that the computer Desktop was originally intended as a metaphor for the top of the desk you're sitting at. That is an empty workspace, which each user populates according its needs and its taste, with the documents he needs at the moment, and the applications he uses more frequently.
The best way to implement it is just a folder, as it used to be in the good old times. Anything more is a source of instabilities, headaches and crashes.
For stable, consistent and useful usage, nothing should be "integrated" into the desktop, because each user has different needs and they may change day by day. Either you integrate into the Desktop everything conceivable, and build up an unmanageable monster, or you pick up what you deem necessary, and it turns out that it's completely useless for all the rest of the users.
In a physical desk, only a fool would stack only documents with the same look, using the same font style and font size, the same colours, etc. One puts on his desk the documents he needs, and the more they look different, the easier to tell them apart. But desktop designers believe that uniform look should be a value, and they concentrate their efforts to make everything look alike, instead of concentrating on usability, stability, and consistent behaviour between releases.
Then they conceived that foolish thing that is the Plasma environment, which is nothing but a bloated systray taking all the screen, populated by Plasmoids, which are nothing but bloated (and usually buggy, because none is using them) applets, which steal a lot of screen space, instead of being a few small Icons on the system tray. They try to index your files when you don't need it, and in this way they slow down your workflow; in order to keep track of a handful of passwords, in place of a simple encrypted list they use a mysql database, which subtracts resources to your useful activities, and gets into the way if you're using mysql for some other useful purpose, etc. etc.
Moreover they failed from the beginning to follow sound design rules. They're rightfully using the Qt widgetset which is good, and provides the pleasant look which is the reason to select KDE, but they failed to take into account that Qt evolves. The only reasonable way to deal with an evolving widgetset is to provide an abstraction layer, isolating the Desktop applications from the WS. The abstraction layer should provide a number of stable API's related to the functions required by the desktop applications, and implements them in the current Qt context. That way changing from let's say Qt4 to Qt5 is just a matter of rewriting the abstraction layer, leaving all the applications unchanged, and keeping all the previous features. Then, with time, new features can be added to take advantage of what the new Qt provides. But they didn't do it that way. It would appear that they always restart from scratch. KDE1 already had all that's required from a desktop. But it took until KDE 2.3 to get the same features. Then it took until KDE 3.5 to get all the features of KDE 1. I'm currently using KDE 4.3.4 (CentOs 6), and I still find it a significant regression with respect to KDE 3.5. The newer versions I've tested seemed to have added new bugs instead of eliminating the old ones.
The only thing one can say in favour of kde developers is that Gnome developers aren't better in any way, and they manage to provide an uglier, even more confusing and less stable Desktop.
It would be a pity to leave KDE forever, but if the kde developers continue on their way, I'm afraid that I'll be forced to take a different road, to lightweight Desktops, less ambitious but much more usable. </rant>
Giuliano