Hidden Windows Terminal goodies to check out: Retro mode that emulates blurry CRT display – and more Microsoft has bequeathed new capabilities to both the released and the preview versions of Windows Terminal, a feature-laden alternative to the command prompt. It's the features that now appear in the released version that are most interesting. Windows Terminal – as found in the Microsoft Store – has reached version 1.2, with …
Better late than never I suppose. By late I'm measuring in decades.
The windows command prompt has always sucked and the powershell terminal really isn't much better except for more easily allowing a terminal wider than 80 columns.
I've tried a few 3rd party terminal emulators and I'm yet to find one that I'm happy with. PuTTY is the smoothest for SSH but the lack of tabs means it's too cumbersome for me when working with multiple sessions.
I just don't get why terminals in Windows have to be so damn bad - from hideous, chunky fonts to awkward and cumbersome copy+paste functionality.
I'm stuck with server 2012r2 for the foreseeable future so given this terminal apparently requires Windows 10 I doubt it'll help me much. But if it gets backported I'll give it a whirl.
My rant is a little further down below ;)
I made this tmux clone. https://github.com/osen/vimux
It isn't perfect but does just about allow us to avoid making multiple SSH sessions. You might find it useful too?
(Edit: I tested it on Win7+ but it should also run on older, such as Windows XP)
The standard console in Windows 10 has supported Ctrl+C/Ctrl+V for copy and paste for quite a while now. It's even smart enough for Ctrl+C to copy (if there's a text selection) or kill the current process as you would expect. Suffice to say I miss it when I have to use bash for something (talk about awkward copy+paste functionality - enter to copy, right click to paste... uh-huh, that makes sense).
And you've always been able to change the font - at least as long as I can remember.
>> Suffice to say I miss it when I have to use bash for something (talk about awkward
That probably means you are running bash in the standard (pre-10) Windows console. Agreed, the copy and paste in the Windows console is bizarre.
Normally bash is distributed by Cygwin and with it, the mintty terminal. In that case you just select the text with your mouse (no copy needed) and then middle click to paste. Copying off the traditional X11 approach. Works very nicely and no risk of sending a ctrl-c signal to the running program (haha!) (actually I guess that *was* the reason behind the decision for Microsofts weird "enter" to copy system of old)
You are aware that bash (at least on Linux) is a shell not a terminal emulator.
The difference is that shells process commands, and the terminal emulation handles the presentation. This allows you to keep the same terminal emulation while changing the shell you want to use.
I know I'm an old foagy, but this type of confusion between components on systems is part of the root of many of the problems with modern CLIs.
You use something like Putty or an xterm to get access to the system, and you then run a shell such as bash or ksh through that access to run commands. This allows you to separate the terminal emulation from the command processor. So the terminal emulator handles driving the screen, handling keys and doing the copy/paste, and the shell runs commands.
It fits in with the Unix ethos, do one thing, and do it well.
I know this is conflated by the monolithic commands that developers appear to like developing now, where the a single tool does everything, and that has it's place for some types of applications, but basic OS commands should IMHO be independent of the terminal access.
This is something that I don't believe Windows has ever done properly. The command.com window was seen as just for legacy DOS type programs. Maybe this is a move in the right direction.
I've changed the fonts many times but all the windows fonts look horrible to me. There is just no decent option available.
Enter to copy sounds much more like my experience of copying in Windows. And ctrl+c is for cancelling the current operation so it had better not be bound to copy in my terminal.
What you're describing with bash is definitely down to the terminal emulator and not bash itself. PuTTY comes with really odd defaults for copy pasting in my opinion.
On a native Linux system there are typically two separate copy buffers - one is your classic ctrl+c (typically ctrl+shift+c in a terminal) whilst the other is really smart and I miss it like crazy on other systems: Whenever you highlight some text it is automatically copied to a buffer so your copy paste is as simple as highlighting what you want and then middle-click where you want it pasted (or various other options for pasting - the simplest being both mouse buttons together if you don't have a middle one).
I am forever forgetting to press ctrl+c in Windows because I'm so used to the copy being automatic.
But in Linux the two clipboards come in handy if there's both a username and a password for example - select the username from your secure password manager of choice and hit ctrl+c and then just highlight the password....
Back where it's needed, paste the username with ctrl+v and middle click in the password box - job done! No need to go back to the password manager a second time.
Highlighting is especially weird in Windows terminals as it selects a block area as opposed to whole lines. If I'm trying to select some text which starts halfway along a line and wraps to the next line, I can't do it in Windows.
Don't even get me started on the supposed 'intelligent' select that expands the area I've highlighted because Windows thinks I wouldn't actually want to highlight a word starting from the 2nd letter.
I think that anyone who finds the windows console Windows to be acceptable, probably never used DOS and hasn't experienced Linux or Mac terminals.
Let's just hope this new one is a nicer experience
Give superputty a try, its a tab and session manager for putty, fixed all of my putty woes, to the point that win term is nothing more than a curiosity, integrates with winscp (or scp client of choice) tabbed sessions, layout history so if you always have 3 sessions open you can just have them open when you launch superputty, and it it runs on xp upwards so should be fine with 2012r2, and its free :)
https://github.com/jimradford/superputty
I'm stuck with server 2012r2 for the foreseeable future
I have come to loathe 2012r2. Last year I had a problem where ssl connections would sometimes break.
Turns out that 2012's cipher suite configuration is a little bit obsolete. Just enough to cause random issues.
We upgraded to 2016 and our "mysterious" problem vanished.
Windows comes with its own ssh client these days. I have Terminal configured to open a ssh connection to a handful of different servers -- all with a nice little graphic in the corner so I can easily tell 'em apart. Works a treat.
Hmm, tabs... how quaint. Do people not use SSH or (even less likely) Remote Powershell? How about some sort of sodding console multiplexer on the hosts end so I don't need to make about 5 separate ssh connections just to develop/debug software remotely on this annoying platform?
tmux, screen.... (even DESQview from the 90s!). All very popular for a reason.
I even had to hack up a "poor man's tmux" (https://github.com/osen/vimux) for whenever I have to babysit a "special" Windows machine.
The main issue with local tabs is you need to keep relogging into the SSH server every time you create a new one. It is much more effective to "open up a tab" on the server session instead.
Sure, if you only edit the occasional config file, who cares but if you have many tabs, i.e text editor (nvi), compiler (clang), debugger (lldb) and manpages all up at once on the remote machine, it soon becomes inefficient to log in and change directory for each one.
In the past we happily solved this with job control (ctrl-z, bg, fg) and it worked great but... of course flipping Windows is lacking that fundamental thing too! XD
Most people install a POSIX layer like Cygwin and get on with their lives but unfortunately Cygwin minces up the environment just enough that it can make testing and debugging native win32 software unreliable (for example it changes a lot of environmental variables).
Or you know, you use tabs to connect to different remote machines, and then run screen in all of them ...
Then again, what do I know ... I installed cygwin/X and use different Xterms (each with a slightly different colored font) to connect to different remote linux boxes ..
and run screen in all of them ... ever since I discovered screen in 1992 (or so, give or take a year) it has been my multiplexer of choice ... plus the fact that your session stays alive if your connection drops ..
back in the day when you would loose the connection if your wife would pick up the phone while you were using the same phone line to connect your VT100 to the office machine ....
Glad those days are over :)
You create tabs by selecting profiles. Each profile is highly configurable. Ie, if you use your brain you can make a profile that uses your favorite Linux flavor in WSL to run "SSH" just the way you want. Or maybe through Powershell. Who cares, it's just a command. I don't know why you're bitching. Seems like you don't know how to use the thing. It takes less effort to edit a json profile in Windows Terminal than it does to set up all the crap you are talking about.
IBM 2741s and 3270s, KSR33, VT52, VT1xx, VT2xx... and then we had the merciful release of the GUI. No-one at that point would have imagined that programmers in 30 years time would be spending their time more perfectly reproducing the experience of the 1980s.
Or, indeed, that vinyl records would be on the shelves of cloth-eared and cognitively dissonant youngsters supposedly concerned about plastic pollution.
What happened to progress?
We tried it, and most of it turned out to be rubbish.
In all seriousness tho, a huge amount of effort was put into making the good old "shell" an effective way of interacting with the machine. Since the arrival of the gui there has been huge amounts of effort poured into making the gui look cool, because that's way more attention grabbing than making it work better. With a text shell, you don't really have that option.
I fervently believe that gui development has been horrifically backsliding over the last few decades, with developers apparently more obsessed with what they can take out to make the thing look nicer, than what they should put in to make it work better.
a huge amount of effort was put into making the good old "shell" an effective way of interacting with the machine
Then it was hopelessly misspent. Using bunch of randomly-named commands with poorly-documented and often misspelled options is not an effective way of interacting with anything. It's also actively hostile if your first language isn't an approximation to English or, worse, doesn't use the latin alphabet. It also promotes an exclusive culture that demands you are initiated into the arcana before you can practice your craft (and I say that as someone who used to write JCL...).
Although I agree that usability has largely been forgotten in a lot of UI design, it's never going to be fixed if we continue to make a fetish out of yesterday's technology.
I firmly believe that there is nothing wrong with interacting with a computer in whatever way works for you - gooey for when you like that, and an emulation of an insanely noisy printing terminal from the 1950s when you're so inclined. Or speaking (which when you think about it, is very much like a command-line).
It's unfortunate that the cli is tied to English, but that's a solvable problem. As is the insanely huge collection of commands (some of which are poorly documented). For a tiny example, I have a bletcherous shell function called "show" (which could also be called "sioe") which looks at the file extension before deciding how to display it (by preference) in the terminal.
"initiated into the arcana before you can practice your craft"
Do you really think there is a single profession out there that doesn't have to initiate people into the secrets of the trade before they can practice? A somewhat outdated saying: "Windows allows any idiot to run a computer. Do you really want any idiot running your servers?" (and this is really a knock to the assumption that running a fleet of servers is something anybody can do; not to Windows itself)
For sure there's some fetishization... I'm sure that's not a word, but I'm gonna roll with it... going on here. The whole "Look, it's a green and black CRT!" option is clearly some kind of fan service - although I'm not sure what kind.
But you know what, there's nothing really wrong with a bit of nostalgia, but that's not really the point I was trying to make. How, with a gui, do you loop over every member of group a, check if they're in some other group b, if they are add them also to group c as well as drop a few files in their home directory and send them an email telling them that it's happened?
There really isn't a better way to do random arbitrary tasks like that than an old fashioned text shell, and odd corner case shit happens all the time in the devops world where basically everything is made out of the digital equivalent of string and duct tape.
Another one - rename every file in this directory to an MD5 hash of it's content if and only if the MD5 matches the hash of another file in another directory on a remote server. I actually had to do that last week. It took about 5 lines of bash. No one in their right mind would ever write a GUI tool to do something like that it's just too niche.
You're not wrong about things often being arbitrary - but then trying to find things in the Windows control panel isn't exactly an object lesson in logical structure these days - and yes, there's very much an anglocentric nature to 99% of text shells - but then since they were pretty much all invented in the US, that's probably to be expected, and to be honest if English isn't your first language there's a better than even chance it's your second language and so there really isn't a better option - unless you're expecting a sudden resurgence in Esperanto?
Text shells fill a really important role, and I don't see any way for that role to be filled better.
I fervently believe that gui development has been horrifically backsliding over the last few decades, with developers apparently more obsessed with what they can take out to make the thing look nicer, than what they should put in to make it work better.
Couldn't agree more - I see a lot of forum threads all over descend into arguments over the minutiae of proposed spacing regimes - and this on modern ui layouts which appear more blank space than content.
What happened to progress?
An entire sub-industry grew where it promoted form over function, user interfaces become less useful and omit many of the key and most important factors in good user interfaces. Not that there were that many good user interface designers in the first place, but with the vast growth in developers (of very varying competences) there has not been a similar growth in user interface designers. Nor database designers/developers either. This largely explains much of the mess the software industry is in.
As for vinyl over digital - the perceived snobbery of this is where it comes from. That and mainstream digital services which genuinely output worse quality products for technical reasons. For example, digital TV picture quality often being usually somewhat worse than analogue equivalent broadcasts due to bandwidth restrictions and the commercial need to cram more channels into the same limited bandwidth, thus reducing the quality of most of them.
@Nick
"An entire sub-industry"
And what they build can only be changed in timescales measured in eons. So much for a new option to do something different hacked up in a day, now it is weeks of lead time and a release cycle away.
Or do we have to live with that worst of both worlds "enter additional parameters in this box" and then the GUI does a flipping CLI command under the hood :|
Yep, far too much "modern" software is cobbled together in a manner too well reflected in this onligatory XKCD: https://xkcd.com/2054/ (Data Pipelines)
Personally the TTY ruled them all.
Typing stuff, seeing it printed on the sheet of dot matrix compatible paper ( with the typing errors that can't be corrected ) and then seeing the system answer being printed on the same paper after you hit return is unforgettable.
I think every developer should try it at least one. It was woefully wasteful of paper but honestly I would much rather use it even today than one of the typical web browser IDEs that the cool (albeit misguided) kids are using.
For example the ex command:
:%s/^M//g
Would still work. Cloud IDE's just assume your line endings are whatever "they" use. I am also fairly sure that the typical Cloud IDE developer doesn't quite know that different line endings exist...
Again, if it didn't kill so many damn trees, the paper is really nice on your eyes too XD
Just hook up your VT100s and Teletypes and have at it. :-D
Powershell also supported.
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/bootcfg-ems
https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/boot-parameters-to-enable-ems-redirection
VMs also
https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/serial-console-windows
(For the TTYs you may have to use a baud rate converter. Although I haven't tried, I suspect that neither the line driver nor the hardware will go low enough for a TTY.)
Many modern hypervisors use serial to manage VMs. For example OpenBSD's vmm and for a while Byhve too.
A server operating system would be an absolute joke if it didn't provide serial access. The Windows SAC is there... but like most other Microsoft solutions is pretty weak.
Debugging kernel panics is also fairly reliant on serial connection. Not everyone wants to just stare at a BSOD all day and do nothing about it.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
