Comment by MarkusWandel
2 days ago
Unix oldtimer here (first exposure: 1987). A lot of copy/pasting is at the shell prompt. Aside from being super lightweight - just select something in previous output, e.g. a file path, middle click, and done - what about the key bindings? All the world uses ^C for copy, but that already does something conflicting at the Unix shell prompt.
I have to admit that I do feel like an oldtimer though. What I do at the shell prompt, others do in VS Code, and probably 10x faster once they're good at the GUI. So maybe super-lightweight copy/paste at the shell prompt just doesn't matter that much any more.
That is also the one good thing about Window's commandline, you use right click there to copy and paste which is nice. The rest sucks.
I cannot stand the Windows user experience in their command line. The Linux method actually has to software registries that allow for different content to be copied and pasted.
Oh I used CTRL+C to copy something but I need something copied first, highlight paste with middle mouse and paste with CTRL+P.
On Windows you must destroy the content of the CTRL+C and replace it with what the middle mouse can do, go back to the first source to copy and paste again.
You want a clipboard manager/history. You are using middle button paste as a work around for how hard it is to find a good clipboard manager (I'm not sure if one exists...)
1 reply →
Tangential - what do people do faster in vscode than on the terminal ?
The whole "integrated development" experience. Take it or leave it, but old farts like me go all the way back to poring over code on printouts since your only window into it was one file at a time in an 80x25 terminal - not terminal window, actual terminal or, by then, terminal emulator.
That does affect later habits like, for example, hating the information overload from syntax highlighting. And don't even get me started on auto-indent.
Whereas younger colleagues, whose habits were formed in the era of much more sophisticated tools, have dozens of files open in tabs and can follow, say, a "where is this defined" or "where is this driven" (this is RTL code, not normal software) in an instant. Keep in mind some oldtimers had really fancy emacs setups that could do that, and vi users had things like ctags.
They imagine that they're being more efficient.