Microsoft Unveils a New Terminal for Windows 10 and Windows Subsystem for Linux 2 (techcrunch.com) 198
Windows 10 is getting a new terminal for command-line users, Microsoft announced at its Build developer conference today. The new so-called "Windows Terminal" will launch in mid-June and promises to be a major update of the existing Windows Command Prompt and PowerShell experience. From a report: Indeed, it seems like the Terminal will essentially become the default environment for PowerShell, Command Prompt and Windows Subsystem for Linux users going forward. The new terminal will feature faster GPU-accelerated text rending and "emoji-rich" fonts, because everything these days needs to support emojis, and those will sure help lighten up the command-line user experience. More importantly, though, the Windows Terminal will also support shortcuts, tabs, tear-away windows and theming, as well as extensions. It also will natively support Unicode and East Asian fonts. Microsoft also unveiled a new update to WSL, a compatibility layer for running Linux binary executables natively on Windows. From a report: WSL 2 is based on a Linux 4.19 kernel coming soon to Windows. This kernel uses technology built for Azure. In both cases, it helps to reduce Linux boot time and streamline memory use. In fact, Microsoft is promising developers "twice as much speed for file-system heavy operations, such as Node Package Manager install." WSL 2 will also support running Linux Docker containers natively, so that VMs are no longer required. WSL 2, like Windows Terminal, is coming in mid-June.
maybe I missed an episode but... (Score:5, Insightful)
Re: (Score:2)
If your job involves processing through and filtering and human-written logs written without (usual) managerial oversight (such as chat logs or internal changelogs), a disturbing amount of your day is spent trying to determine whether a particular byte sequence is "poop", "happy", or "explosion".
Re:maybe I missed an episode but... (Score:5, Funny)
a particular byte sequence is "poop", "happy", or "explosion".
Easy for me, mine are all three.
Re: (Score:2)
TMI! :(
Re: (Score:3)
Hmm, is that the new ctrl-alt-del sequence?
Re: (Score:2)
People do still use terminals for chat, and I'm sure it's there for more wysiwyg purposes when embedding them in code.
But they're wasting their time with powershell. Improved terminal support for graphics is a good first step. But they need to do away with the last vestiges of DOS and just embrace bash/tcsh/unix. It flat out works better.
If they want to add proprietary windows commands on top, go nuts, I will never learn them or use them or waste even a second worrying about them. I might be compelled to us
Re: (Score:2)
They do offer bash, at least on WSL. But they also have a version of PowerShell for Linux, and it actually has more users than the Windows version!
The Linux version is open source, unlike the Windows version. But Microsoft is working on a future version for Windows that will use the same code base as the Linux version and that one will be open source. (The open PowerShell is not 100% bug for bug compatible with the classic PowerShell so both will be available on Windows.) A big part of that is that Windows
Re: (Score:2)
Any terminal with unicode support can already display emoji's. For example, if I do Ctrl+LeftShift+u then type in 1f4a9, I get the "Poo" emoji in my xfce-terminal.
Re: (Score:3)
You may not want to, I also don't use Unicode. That doesn't mean I like seeing Slashdot display gibberish just because someone else didn't account for the lowest common denominator.
Re: (Score:2)
Slashdot is English-language.
Re: (Score:2)
Indeed. The "lowest" common denominator. :-P
Re: (Score:2)
Re: (Score:2)
Can I quote you on that?
Re: (Score:2)
I never used emoji in CLI...WHY THE HELL WOULD I ANYWAYS ? I always used CLI for tech stuff let say. I don't even know where to start as to why would I use emoji's in CLI anyways
How else can you get a millennial to learn how to use the black box thing with writing in it?
Re: (Score:3)
I am not saying these are good ideas...
1. More complexity to your passwords.
2. Enhanced Character Set for your applications (and text based games can have some graphics)
3. Text based versions of your chatting software.
4. Some Emoji's can be a little more functional. Such as picking the Flag for your international settings.
5. Enhanced comments in code.
6. Parsing data from other applications that use Emojis. Grep for the eggplant emoji to weed out troubling users.
7. In general just keeping the import functio
Re: (Score:2)
I never used colors in CLI...WHY THE HELL WOULD I ANYWAYS ? I always used CLI for tech stuff let say. I don't even know where to start as to why would I use color in CLI anyways
Re: (Score:2)
I don't even know where to start as to why would I use color in CLI anyways
I often have multiple terminal windows open, with different settings (credentials, environment settings, etc). I use different font and background colors, which lets me quickly and easily switch to the appropriate one when multitasking.
Of course, the default is VT220 P3 phosphor amber on black, as God intended it
Re: (Score:2)
I have to say I have been doing something similar for decades as well (I use the same font, and just change the colours). It makes it easy to determine what the terminal window is logged into and reduces the chances of any wrong window action.
Re: (Score:2)
*whooosh*
Re: (Score:2)
Re: (Score:2)
*whoosh*
Re: (Score:2)
I think they were being snarky. But I may be wrong, too many things these days that I assume are spoofs turn out to be serious.
Re: (Score:2)
Irc has emoji support now.
Re: (Score:2)
Re: (Score:2)
Emoji by itself doesn't really matter. However it is part of Unicode, and I expect a modern terminal to have complete Unicode support.
If there is an emoji in a log file, file name, etc... it should show as an emoji on the terminal, just as Japanese text should look like Japanese text and diacritics should be at their proper place. It is just about supporting a standard.
It anything, Arabic may be a more touchy subject, with all that right-to-left business and control characters that can really mess things up
Re: (Score:2)
Re: (Score:2)
I have not ever typed an emojis on the command line, and do no expect to type one, ever.
But I have also never typed a 'fancy' Unicode character on the command line... while I have been tearing my hair out multiple times because PowerShell could not display things properly. There is number of very useful command line utilities that benefit from special characters used to convey information concisely, and I've had to run other terminals to get them to work properly. I have also had to alter utilities of my
Re: (Score:3)
I don't know why they gave special mention to Emoji's, if the terminal supports unicode, emoji's come with it.
Re: (Score:2)
I use Unicode (not just the ASCII sub-part of UTF-8) every day (I work in computational linguistics), and I have to say that its support in command line programs is dreadful. (This is Linux programs, including the Windows Linux subsystem; can't speak for Windows PowerShell etc.) I don't expect it to display right-to-left scripts correctly, or join Arabic characters, or make Devanagari vowel signs show up in the proper place. But it would be nice if I could paste in a non-ASCII character in UTF-8 and not
Re: (Score:2)
https://docs.microsoft.com/en-... [microsoft.com]
I use the command line... (Score:3)
Re: (Score:2, Funny)
It's called Unicode, dad.
Re: (Score:3)
If you write code that renders Unicode, this can be helpful.
A more likely case is that you end up grepping through logs that contain Unicode from human-generated text. You never know what you'll run into... or need to compare.
Re: (Score:2)
For the past 30+ years. Most computers supported an adjustable True Type font which is rendered on the fly. Unless you are in a non-gui screen. your text is being rendered.
Re: (Score:2)
How is this new command line with rendered fonts and emojis a good thing?
"Rendering" in this case means that the Windows Terminal will be able to use outline fonts instead of raster fonts. This will allow for much better font scaling, and a wider variety of font size choices.
Emojis are just a byproduct of Windows Terminal finally supporting Unicode properly, as Emojis are part of the Unicode spec. It probably sounds more interesting to the MS marketing droids to put in a press release than to state that the Windows Terminal now correctly supports Anatolian Hieroglyphs [unicode.org].
It's abo
Re: (Score:2)
You already need to go there to do support of typefaces with more than 256 characters. A modern full Unicode typeface has tens of thousands of characters to enable multi-language support, a necessity in the modern world of computing. Emojis just come along for the ride.
With even the lowest end integrated graphics in modern computers, the burden of rendering those characters is minimal. You might feel the burden on a microcontroller but not on anything you would use for desktop computing.
Re: (Score:2)
Afaik, very few fonts render "tens of thousands of characters"; Microsoft's Arial Unicode (which came on the scene decades ago) is one of the few. Generally, one needs fall-back fonts for different scripts.
But there's a lot more to rendering some languages' scripts than having the right Unicode code points or even glyphs. Like right-to-left support; joining characters (as in Arabic script); character X that needs to appear before character Y on the screen, even though X follows Y in the string (certain De
Re: (Score:2)
Depends on locale and terminal used. But you would not know that...
Re: (Score:2)
You're assuming he doesn't know something just because he didn't mention it. Just because someone doesn't mention some irrelevant information, doesn't mean they don't know it.
Besides, unicode has been the default for years now.
Unicode on Windows Command Line?! (Score:5, Interesting)
I've run into Unicode on the Windows command line before.
It's not proper UTF-8 encoded Unicode like God and Dennis Ritchie intended. It's forced 16 bits per character unicode. So when you recompile your C linux command line tool, after fixing the lack of getopt support in Windows, you find all the character I/O has been completely screwed up. Try comparing a signature on a text file when the characters have all been changed out with 16 bit encodings.
I was starting to make peace with Windows - I could almost get by with a bash shell and MinGW. But the way Windows does Unicode messed it all up again.
Re:Unicode on Windows Command Line?! (Score:5, Funny)
If you're looking for an emotional support network because something doesn't support unicode, you've come to the wrong place.
Re: (Score:2)
I'm giving people fair warning.
Re: (Score:2)
I disagree. You couldn't find more emotional support in a M*A*S*H outpatient ward, unless you're unfortunately mired in the mindset "what do cripples know about anything?"
Re: (Score:2)
Most text editors and terminal settings, can be forced to UTF-8 if it really creates a problem. But we shouldn't feel constrained on an 8 bit character set .
Re: (Score:2)
Most text editors and terminal settings, can be forced to UTF-8 if it really creates a problem. But we shouldn't feel constrained on an 8 bit character set .
We should be confident that when outputting a byte from C, we get one byte, not two.
Now it's become a chore, to accommodate the backwards unicode encoding on ANSI C programs compiled into Windows land.
Re: (Score:2)
Re: (Score:2)
Yes. But it's at work, I'm not and I don't have a machine at home exhibiting the same behaviour to test the example tonight.
Re: (Score:2)
Microsoft has a history of embracing some standards before theyr'e fully standardized or thought out. The 16-bit characters was one of these as at the time I think they honestly assume that this was the proper way to do things; never mind that it's not a big enough space and that even at the time multi-byte character sets were standard in Chinese, Japanese, and Korean. Sometimes Microsoft embraces standards just as they're about to die as well, witness code pages. I think it's the NIH attitude that drive
Re: (Score:3)
The 16 bit characters were adequate at the time they adopted them. Unicode did not yet have more than 64K glyphs. But it was rapidly growing and Microsoft should have seen the problem approaching. 32 bit characters would have been a better solution, but they were reluctant to go to that because computers of the day still had very small amounts of RAM and storage by modern standards.
The first hard drive I personally owned stored 20MB and I used even smaller ones. I remember being thrilled when 1GB drives fir
Re: (Score:2)
32-bit characters are dumb though. A massive waste of space and multi-byte characters are very simple to use (simpler than wide characters in many cases). The vast majority of the time you do not need to know all bytes of a character until the moment when you're ready to display it. For a file name specifially, there's never a need to interpret the full character when doing file operations, just treat the string as an opaque key.
(with UTF-8 and other well formed multi-byte character sets there are never a
Re: (Score:2)
That should be fixed in 1903. And since WSL 2 is an actual Linux kernel, things will be getting more Linuxy.
Re: (Score:2)
You mean just after the Wright brothers flew their plane?
(Sorry, I couldn't resist. I know what you're saying...but my first reading, well...)
Re: (Score:3)
If you're willing to pay the size overhead, the fastest way to handle Unicode is with 32 bit characters. No fussing around with characters of different sizes. 16 bit characters were a solution for a while but Unicode now includes more than 64K glyphs, but I don't think we'll reach 4G glyphs for a while so 32 bit character sets will be adequate.
Handling UTF-8 gets you into messy problems like dealing with the possibility that you're jumping into the middle of a multi-byte character. The code for any sort of
Insert jump-the-shark emoji (Score:4, Insightful)
Who the hell needs emojis in a shell? Da fuq, Microsoft?!
When my Zune crashes (Score:2)
I agree! The command line is for software engineers, to script actions that need repeat-ability or scheduled execution. An eff'ing emoji? Who would I send one to - Microsoft support, when my Zune crashes?
Re: (Score:3)
I've seen many projects that use emoji in git commits for various things. I would assume being able to see these Unicode characters would be a big help to some people.
Re: (Score:2)
That's worse than no comment at all because it's subject to interpretation.
Re: (Score:2)
Thanks, I now have added another entry in my team guidelines about what to not put into commits.
Re:Insert jump-the-shark emoji (Score:4, Funny)
Who the hell needs emojis in a shell? Da fuq, Microsoft?!
To be fair, I just tried pasting a chunk of text from the Wikipedia "emoji" article into my XFCE terminal in Linux, and all the emojis rendered correctly (although in monochrome) in the terminal. It's a feature that I never knew I had.
Maybe I should use this capability to have the prompt string display a pile of poop whenever the previous command failed.
Re: (Score:2)
I just tried pasting a chunk of text from the Wikipedia "emoji" article into my XFCE terminal in Linux, and all the emojis rendered correctly (although in monochrome) in the terminal.
They should have rendered in color, they do in my xfce-terminal. What happens if you enter a unicode sequence by hand? Ctrl+LeftShift+u and then the sequence, try 1f6a6 That should get you a vertical traffic light with red, yellow and green lights.
Maybe I should use this capability to have the prompt string display a pile of poop whenever the previous command failed.
This will work:
command && echo ðY(TM) || echo ðY'©
Re: (Score:2)
damnit, mean to preview. That will be:
command && echo u1f642 || echo u1f4a9
Re: (Score:3)
I prefer Unicode to ASCII in a shell because then I can process my native language. One man's heavy metal emoji is another man's regular letter.
Now, having Unicode contain emojis is another problem. Back in the day, we had things like :-j and d^_^b and we liked it! It's basically forming words out of letters, instead of using a separate "letter" for each meaning. Kids today will have trouble expressing themselves in written language if all they learn is to use ready-made emojis. Probably affects their cr
Re: (Score:2)
No one. That doesn't mean it is better if the shell prints gibberish just because someone put an emoticon in something else and you happened to use the shell to display the text in question.
How about the basics? (Score:2)
Like support for copy and paste via standard shortcuts, and mouse support so we can select text by dragging.
Re: (Score:2)
Like support for copy and paste via standard shortcuts, and mouse support so we can select text by dragging.
You're in luck! Those are both available already in the Windows 10 console. Right-click on the title select properties. Then under the "options" tab you will find the following:
Enable Ctrl key shortcuts
Enable line wrapping selection
Re: (Score:2)
That does work in cmd.exe, but I can't make it work in the Linux subsystem bash shell; I get nothing the first time I hit ^V, and I get a literal ^V (the control character) if I hit ^V again. Have you been able to make it work in the Linux subsystem shell?
Re: (Score:2)
That's just crazy talk! Who would want basic functionality we've had in linux for 20+ years?
Re: (Score:2)
That's just crazy talk! Who would want basic functionality we've had in linux for 20+ years?
Microsoft, which is why the Windows 10 console has supported this basic functionality out of the gate.
WSL is mostly a toy (Score:5, Informative)
I have used Cygwin heavily for years and not long ago evaluated WSL and found it mostly worthless for anything serious. The inability to run daemons at startup severely limits its usefulness. It cannot replace Cygwin which is still much more mature and valuable.
That emoji support is being touted kind of confirms the toy-ness of it.
ConEmu is the best (Score:2)
By the way, as far as terminals go, ConEmu [github.io] is the best.
Re: (Score:2)
And it's telling, that this is the best alternative.
I read an article awhile back (which I can't find now) that talked about the deep and extensive work it's taking to allow us to finally (finally!) have a real terminal on Windows. It's not surprising that they've taken this long to do so, and tied it in with a new WSL. It's a LOT of work, which will impact a LOT of existing code.
Re: (Score:2)
You can run wsl with conemu. And yes, works great.
Re: (Score:2)
pffff. cygwin is the toy. you can easily run wsl at startup.
Re: (Score:2)
WSL also has threading issues and os issues. This will be fixed in later versions. I went back to cygwin because its faster. Cygwin is great, WSL might over take it someday, you can also follow the WSL github to see whats going on. But for now, Cygwin is much faster.
Re: (Score:2)
JEsus, that's saying something if the monumental kludge that is Cygwin is faster than WSL. Using Cygwin was like extracting toenails with a prybar.
Re: (Score:2)
Using Cygwin was like extracting toenails with a prybar.
What part of it did you find to be especially painful, besides all the stuff that won't compile cleanly under it?
Re: (Score:2)
That it wasn't that fast. It was really quite agonizingly slow. But it has been about ten years since I last used it, so perhaps it's come a long way.
I did manage to get a Radius server to compile in Cygwin, so while it was painful, it actually saved my skin back in the day.
Re: (Score:3)
I've noticed that the time to acquire an I/O handle under Windows is exceedingly slow all which affects all manner of Un*x operations (you can write a toy program in C which simply opens a file, writes a single character and then exits). Since everything from 'git status' to 'grep myString * -R' requires using file handles, Unix-y command line stuff is several orders of magnitude slower on a Windows system. It's not the file system either -- you can mount a drive FAT32 in Linux and still notice that Windows
Re: (Score:2)
It cannot replace Cygwin which is still much more mature and valuable.
It can replace cygwin just fine. Your little edge case just affects you.
That emoji support is being touted kind of confirms the toy-ness of it.
So you understand such little about what you're talking about that you combined news of emojis and WSL even though the former is being talked about in relation to a completely different project than WSL?
To clarify the stupidity, no WSL is not getting "emoji support". The two aren't even in the same paragraph in the summary.
Now please, less frothing at the mouth and more using that squishy thing between your ears.
In related news ... (Score:5, Funny)
The new Terminal isn't just about local use (Score:3)
Re: (Score:2)
Well 20 years ago, To even think that Microsoft would include a Linux compatibility layer, or them putting any focus on a command line interface, would had been considered unthinkable.
The use of the PC has changed from the Personal Computer that people use for fun, to a Personal Workstation that people will use for work. Microsoft knows, this so they have moved away from trying to be the User Friendly OS that grandma can use, to a more serious professional OS.
We have seen this from XP moving to the NT kern
Re:A suggestion (Score:4, Insightful)
Microsoft knows, this so they have moved away from trying to be the User Friendly OS that grandma can use, to a more serious professional OS.
Is that why you get Candy Crush (and a bunch of other bullshit games/time-wasters) that are damn hard to remove (and KEEP removed) on a "serious professional OS"????
I spent a 20 year career supporting Windows (and towards the end of the career, Linux) and I am damn glad I made the decision to dump Windows on my personal/home systems back when I retired in 2010. If I hadn't made the switch then, with dualbooting Linux and Win7, I DAMN sure would after seeing what people who continue to use Windows have to put up with...
Re: (Score:2)
Oddly enough, you posted immediately below an AC mouthpiece posting GNU/Linux propaganda.
Re: (Score:3)
With 4k displays the memory mapped characters is becoming too cumbersome. The 8x8 characters for the CGA display will now need to be 80x80 to make characters at the same viewable size. Rendering the characters with such a high display is a much more efficient method. Being that screen resolutions are now so dynamic. GPU rendering is a much better option.
Re: (Score:2)
Re: (Score:2)
it can tear ascender from serif _really_ quickly.
Re: (Score:2)
The new terminal will feature faster GPU-accelerated text rending...
Why do I feel like this was a deleted scene from Hellraiser?
"Oh the fonts you'll see!"
Re: (Score:3)
if it's faster to render (not 'rend' like GP was pointing out...) a page full of sub-pixel-aligned, anti-aliased, resolution-independent, quadratic/cubic-bezier outlined, hinted, composited glyphs with a GPU, why _wouldn't_ you use it?
i mean, we _could_ go back to blitting 6x8 bitmaps all over the place...
Re: (Score:3)
well, if the unicode textfile you're piping through less has non-ascii characters in it, how would you like those to be displayed? a bunch of control characters? or the actual glyph? don't like emojii in your console? how about Kanji, Chinese or Hebrew glyphs? or is 'text' just ASCII, for you?
Re: (Score:2)
It's not a big deal, many Unix terminals have been doing this for over a decade. I didn't have to bring up special GUI tools to figure out if the text file had the foreign characters formatted correctly, I just used "less".
Re: (Score:2)
The next Microsoft Keyboard better have the poop key or it's all for naught.
Re: (Score:2)
But now we can finally use a smiley face as a function declaration in C#! Just think of the possibilities. Finally, error catching routines can poopy-faces in function calls.
Can't wait until the next Brainfuck compiler is developed. It will now use emojis solely!
Re: (Score:2)
>> Yes! Now I can run SystemD on Windows!
You can install SystemD on windows.
But it will probably not run.
I suggest you run away from it before it triggers aliens.
Re: (Score:2)
Strange, maybe I live in an alternate universe. I've used all of those, except Win8 (which I agree was a monstrosity). Including my Windows phone, which I use to this day; and I'm typing this on Win10 on my PC. It seems to be quite alive.
I used to have an Android, and I find my Win phone much easier. (My wife has a Pixel, and I find it quite frustrating. I've never used an iPhone--nothing against them but the price. Ok, and the fanboys.)
Re: (Score:2)
Now that MS will ship a friggin Linux kernel integrated into Windows, yes, it will be the YOLD !
Re: (Score:2)
An octal calculator.
That's cute
Is there an hexadecimal version ?
Re: (Score:2)
Will wine emulate support for WSL1 or WSL2 ?
Re: (Score:2)
Re: (Score:2)
That's the work of msmash. It seems to be a crapflooding botposter.