sup /g/ods
Ok Fellers - heres an Idea:
Ctrl-C and Ctrl-V should "stack" like a CPU.
Each time I type Ctrl-V it should cycle back to the previous thing that I copied. Most recent copied gets pasted first of course, but the memory should cycle back through.
Huge security risk, perhaps a ram hog, but what a fucking time saver.
What does /g/ think? or am I re-inventing a wheel here?
>>55259907
go for it bro I'd buy that for a dollar
>>55259907
>What does /g/ think?
I got the habit of pressing ctrl-c multiple times years ago and this would seriously disrupt me.
>>55260077
But you have to flip back to the source so many times.
Also how would this interrupt your normal C and V?
why not just use one of those clipboard history programs?
>>55260197
OP here
>or am I re-inventing a wheel here?
>clipboard history programs?
didn't know those were a thing - thank you
>>55260107
I suppose if repeatedly pressing Ctrl+C DIDN'T stack multiple copies it would be alright.
But then you need application support anyway, for anything that isn't plain text.
Most (useful) editors do that, like Emacs with its kill ring : you kill(cut) a region A, then a region B, and when you yank(paste) B appears, you yank again B disappears and A appears, etc.
>>55259907
>What does /g/ think? or am I re-inventing a wheel here?
Alt-Y in emacs. It's called a kill ring.
