Command c command v works fine for me because I don’t “optimise” my experience.

It’s a fun game to do I guess but if you become “more productive” by having a slightly quicker mechanism to find a file through 9 different chords on your terminal only interface - you likely aren’t solving problems that are worthwhile.

▲

doix 6 days ago | parent [-]

I've heard this opinion worded slightly different many, many times over the years. I just can't agree with it. You're going to spend thousands of hours infront of a computer, it makes sense to invest time in being "efficient".

You reach a point of diminishing returns with everything. You can only gain so much knowledge/intelligence/experience before every increase in that becomes extremely difficult. Trying to become "smarter" when you are already "smart" is much harder than getting easy efficiency wins.

There are people that take it to the extreme of course, where they spend all their time on extremely tiny efficiency wins instead of learning how to program, but that's the same problem in reverse.

It's a pretty old concept, the first time I've seen it given a proper name was "aggregation of marginal gains" [0].

[0] https://jamesclear.com/marginal-gains

▲

troupo 6 days ago | parent [-]

> it makes sense to invest time in being "efficient".

It does. However, spending time remembering which of the different weird buffers something is pasted into is not being efficient.

▲

0points 5 days ago | parent [-]

It's not "weird buffers".

It's a feature you're not accustomed to.

▲

troupo 5 days ago | parent [-]

Yes. Yes they are weird buffers in that you have to spend some (minor) effort remembering what exactly is in the "clipboard", "selection", and the difference of invoking them between apps (e.g. having to Ctrl+Shift+V in the terminal).

Oh, and the fact that selection buffer gets overwritten if you switch between apps with active selections.

Oh, usually there's also a cherry on top in that everyone's darling, vim, doesn't even interact with any of those and has its own buffers aka registers.

I'm sure if there was a way to track how many time you make and undo mistakes in copy-pasting the wrong thing from the wrong buffer, your assumptions would be seriously challenged.

▲

0points 4 days ago | parent [-]

> I'm sure if there was a way to track how many time you make and undo mistakes in copy-pasting the wrong thing from the wrong buffer, your assumptions would be seriously challenged.

> Oh, and the fact that selection buffer gets overwritten if you switch between apps with active selections.

What can I tell you...

Use a clipboard manager.

The end.

▲

troupo 4 days ago | parent [-]

> Use a clipboard manager.

> The end.

Does it fix the issue with the multiple buffers and minor annoyances?

No. It just adds a different friction point.

The end.

	▲	0points 4 days ago \| parent [-]
		> Does it fix the issue with the multiple buffers and minor annoyances? The stuff you mentioned so far is all about you not configuring your setup: - buffers: You configure your clipboard manager to use a single buffer. - vim: configure to use global clipboard if that's your preference - X11: dont use legacy software > No. It just adds a different friction point. You think using software that implements functionality you deem missing "adds friction", and yet you still want said missing functionality and complain about it is missing. That's wild.