This is why we added support to optionally set Ctrl+Shift+V as the paste keybinding in conhost.
Fortunately, the Windows Terminal doesn't have a lot of the legacy to maintain like conhost does, so it'll support setting paste to whatever keybinging you like :)
No Windows terminal I've ever seen has the ability to do this.
Edit: Note that I haven't used the new terminal yet, so if it supports an actual right-click menu, than bravo!
Fortunately, the Windows Terminal doesn't have any existing back-compat we have to support, so that's definitely a setting we can add to it :)
Pretty sure that this is one of the biggest requests / frustrations you will hear from users. The issue is that MS has normalized the right-click menu as the go-to method of choosing exactly what one wants to do with a selection of text (, or even anywhere, for that matter), and it's useful, and uniformly available in Office and other Windows apps, and missing ONLY in cmd.
For example, when pasting in Excel, Paste vs. Paste Special vs. Keep Formatting vs. Keep Formulas, etc; via the right-click menu is just great. Going from that to a "We insist on a 1982 MS-DOS experience" in the cmd window is just annoying.
The terminal still has the menu commands, by the way. They're tucked away in the window system menu (the one with Minimize, Close etc, that you can open by clicking on the app icon in the title bar - it's all under Edit there).
I do prefer X because of the PRIMARY selection style automatic copy/pasting, but this would go a long way to making my Windows experience more enjoyable. The Windows development experience is hugely improved and my rediscoveries of it in the last few months have been generally very enjoyable.
You have never heard that people might want to use functionality that has worked on all editable text in the entire rest of the operating system since Windows 95?
Feel free to file it over at https://github.com/Microsoft/Terminal, and we'll triage as appropriate
I'm terrified that, when I'm scrolling, I'll accidentally push down just a little bit too hard on the scroll wheel, and it'll do something awful like paste PII into a chat or paste a passage of text into my terminal and one line of it gets parsed as a valid command.
I'd rather just use my middle button for autoscroll. It's safe, and it's my preferred way to scroll in the few applications that supported it.
To me it helps me not have to use the keyboard. Windows is a very hybrid keyboard/mouse driven environment (e.g. Alt-Tab is almost indispensible - but simply not how I think). Using the keyboard for things that are not typing is actually genuinely difficult.
Something like Gnome with the compromises their X-based history forces onto them basically means you can use the system without touching a keyboard except for typing, which is very nice. Alt-Tab and Ctrl-C/X/V are there, I think, but I've never used them.
The existing windows terminal has supported that for ages.
Click the upper left icon of a terminal window
Properties->Options->Quick Edit Mode.
Uncheck.
It isn't 100% the same, after selecting text right clicking will auto copy it, but other than that, mostly the same.
Clipboard UX is a bit of a mess on Linux, but notably on macOS copy is Cmd+C and SIGINT Ctrl+C, so this isn't an issue at all.
Ctrl+C to interrupt was inherited from TOPS (via DOS and CP/M).
Ctrl+C to copy selected text was introduced on Xerox PARC, the granddaddy of all modern UIs. In DOS, some text-mode UI apps were already using it, although IBM CUA was more common.
With the Windows Terminal, we've switched to a DX/DWrite based renderer, which no longer uses the CPU to draw text, and moves it to the GPU. Our preliminary testing has a insane perf improvement for applications writing lots of text, something like 10x faster :)
Presumably, the new terminal will have the same lag now other windows apps have?
I'm asking because 10x sounds great, but in my memories the Windows terminal was so slow to ouput text that this might not be enough, compared to the competition.
(Thank you for responding to so many comments on this thread!)
Also stay tuned for Rajesh Jha's keynote later today, with our official announcement. It'll have some other relevant information I don't think any of the articles have mentioned quite yet :P
It's live now, and I think Windows is up soon, though I don't know where in the keynote we are.
Perhaps it has something to do with Unix tty. Unix systems are mainframes or servers, the tty subsystem only cares about transmitting the text and control sequences, the actual rendering is done by a CRT terminal at a remote location. Meanwhile, the DOS family was designed for microcomputers and PCs, the text output is tightly-coupled with the system and hardware, including how to draw them. The Windows XP console can even switch to the genuine VGA textmode as used by DOS by pressing Control+Enter.
I guess the Unix tty allowed flexibility. It doesn't matter if someone reimplemented it using VGA textmode, or 2D accelerated framebuffer (modern Linux kernel), fancy 3D OpenGL stack (kmscon, but sadly the project is dead), or a cairo-based graphical interface. Meanwhile, Microsoft haven't continue to develop and modernize the console subsystem in a long time (clarify: at least in 8 years of Windows XP era, until recently).
That's just provably false. We've been hard at work on the console for the last 4 years, culminating in today's Terminal announcement.
See https://devblogs.microsoft.com/commandline/ for a few examples of things we've been doing for the last few years.
One in particular: Last year we added support for a pty-like interface in Windows with [ConPty](https://devblogs.microsoft.com/commandline/windows-command-l...)
Midnight Commander, htop, applications that make extensive use of VT command sequences all work fine.
Now that the cloud is the way to go, they're looking at this in a more holistic way, it seems.
We do however have a pretty solid VT100+ implementation nowadays. Case in point, it'd be pretty hard to run anything in the Windows Subsystem for Linux without a complete VT implementation.
EDIT: It is possible you are on an outdated version of Windows, or have upgraded and still retain your old settings.
Be sure QuickEdit Mode is enabled, as well as Ctrl key shortcuts.
One of the things I hate is when the default option is "good enough" so you have the danger of living with mediocrity. Or, worse, the platform doesn't spawn a rich ecosystem of competition.
For example, when I was on OSX I couldn't find a music player I liked. iTunes was bad, but the fact that everyone uses it means there aren't as many alternatives as on Windows.
You can have everything now on all 3, everything important. I almost never use non-cross platform tools.
SMPlayer's homepage says it's only on Windows and Linux. I only ever used VLC for playing one-off files. I never knew about VLC having media collection features, might have to look into that.
Rhythmbox on Ubuntu has been great for me. I just want Rhythmbox on other platforms. I've been using Google Play Music instead. (It lets you upload your music collection into the cloud, which is super useful as I can now use it from devices it's not synced to, though it's not open source or an application I can run offline, and it's pretty limited in how it can sort and display songs. I can't sort songs by date added, etc.)
If you want non-laggy, VLC is the best (both video and audio) but its interface sucks a lot although it is probably tolerable on the long run.
SMplayer could probably be ported in a week or so on OS X given it uses mplayer or mpv which are both available on OSX (its just a fronted to those tools + open sub).
I also used MPD with Cantata in x-platform manner its quite nice and fast.