But why do I need to copy a line before being enable to copy it to the clipboard?
Why didn't you just make every line (every single clip) clickable?-robbero
Long-winded explanation coming up...
This goes way back to why I wrote ClipTrap in the first place. During that time, my job entailed working on the CLI of many different networking devices (routers, switches, BRAS, DSLAMS, etc.) and it was very common to have to run several commands on various devices and then get all that content into, say, a trouble ticket. As you might imagine, this involved very long outputs (1000s of lines) of text. ClipTrap was designed to make this sort of
temporary aggregation of data very easy.
For instance, let's assume you have six different SSH sessions open to various devices. You clear ClipTrap's current state, run your commands on those devices, and then do a copy command on each window. You then switch over to ClipTrap, which now has all the outputs from the six SSH windows. You do a copy there in ClipTrap and, bam, you're ready to paste all that output into a trouble ticket, email, etc. Does that make sense?
ClipTrap was never designed as a
long-term permanent database type of clipboard caching tool as there are plenty of those already available. As it states on
ClipTrap's webpage, you can think of ClipTrap as something in between using a full-fledged clipboard manager and using nothing. I use this in conjunction with
ArsClip, a fantastic clipboard caching tool.
ps: I confirm that it is wind10 compatible.-robbero
Great to hear. Thank you for the report.
