Gräßlin: Next Generation Klipper

Posted Jul 5, 2014 4:08 UTC (Sat) by roskegg (subscriber, #105)
In reply to: Gräßlin: Next Generation Klipper by bokr
Parent article: Gräßlin: Next Generation Klipper

Good suggestions. That sounds closer to the proper Unix way to do things. Maybe even THE proper Unix Way. I hope KDE gives your plan serious thought. What is up with all these young coders pissing on "The Unix Philosophy" by Mike Goncarz, as if it went out of date?

Gräßlin: Next Generation Klipper

Posted Jul 5, 2014 9:13 UTC (Sat) by roblucid (guest, #48964) [Link] (1 responses)

Klipper's worked really well since KDE1 days, it needs to operate invisibly for a smooth UI experience and NOT add any latency or delays, to copy/paste operations. Being memory based, with load/store across login's meets the requirement.

I actually used ed(1), at times when booting off tape and adjusting BSD kernel config during the install process.

ed(1) DID not split your text file up line by line, into seperate files but used a data structure in memory, and klipper which makes persistent what is already highlighted and stored, ought to take the same approach, as that IS the true UNIX way, doing 1 simple job and doing it well, getting out of the user's way, rather than generating a whole load of crappy temporary files. This is why McIlroy's idea of pipes is so superior to FS based alternatives.

Gräßlin: Next Generation Klipper

Posted Jul 6, 2014 4:32 UTC (Sun) by roskegg (subscriber, #105) [Link]

That sounds interesting. Can you explain in more detail?