What is Reddit's opinion of
Windows Terminal?
From 3.5 billion Reddit comments
100 reviews of this app found across Reddit:
Actual packaged release previews will come by summer. We plan to distribute via the Windows Store. Maybe also packages on our GitHub as well for those who have set Developer Mode on their Windows machine to sideload apps.
We're still working on this part. There were a lot of moving pieces to get this far by TODAY and this is one of those that we're going to get back to tackling starting after the Build conference ends later this week!
Right now, you can get it by building it yourself from our GitHub at https://github.com/microsoft/terminal.
Just to whet your appetite - the full write up is here 😊
​
In short:
- Multiple tabs
- New text rendering engine
- Control over the Terminal’s appearance and each of the shells/profiles that you can open as new tabs
​
As of today, the Windows Terminal and Windows Console have been made open source and you can clone, build, run, and test the code from the repository on GitHub: https://github.com/Microsoft/Terminal
When can I get my hands on it?
As of today, the Windows Terminal and Windows Console have been made open source and you can clone, build, run, and test the code from the repository on GitHub: https://github.com/Microsoft/Terminal
This summer in 2019, Windows Terminal previews will be released to the Microsoft Store for early adopters to use and provide feedback.
This winter in 2019, our goal is to launch Windows Terminal 1.0 and we’ll work with the community to ensure it’s ready before we release!
> Right now, you can get it by building it yourself from our GitHub at https://github.com/microsoft/terminal
Waouh, I was not expecting that, and this is great!
(and WIL seems cool too!)
Thanks!
> 🍿🍿🍿 - https://github.com/microsoft/terminal/issues/10623
I understand Muratori's point with the whole refterm saga, and I think it was handled very badly by the windows terminal team inside github issues.
But this dude is just straight up riding on the wave against the windows terminal without providing anything relevant beside parroting what was said by Muratori in his videos, which at this point I assume the windows terminal team has already seen.
Source is here: https://github.com/Microsoft/Terminal
​
I'm confused why many devs don't add a screenshot of their application to their README. Thanks /u/jenmsft for adding a screenshot to your writeup.
Dude's unbearably insufferable, and frankly just wrong. E.g., from comment
> Windows Terminal, Conhost, ConPTY, etc. > > * Increased OOP, Increased C# and .NET, Increased layers > * Increased Memory, Increased CPU > * Decreased Performance
- OOP is not necessarily bad
- The Terminal actually doesn't use .NET or C#, so that's just wrong.
- No duh it has more layers? The Terminal is doing more things than the console, so obviously there will be more layers.
- The memory footprint of the console has been going down over the years, and the performance has been steadily improving.
But this dude isn't there to have a good faith discussion.
We're working as hard as we can! We've got a spec open, we're prototyping, working with the Settings App folks to get the UI in the Settings app, it's all coming together - it's just one of the trickier pieces of architecture. Mainly because we don't just want to make the Windows Terminal the default terminal - what we'd really like is to allow users the ability to pick any terminal application as the default on Windows (and have them still choose the Windows Terminal as their default 😄)
/uj
https://github.com/microsoft/terminal/issues/10362
MS devs adamantly claim they have reached the fundamental rendering limits of modern hardware; turns out they just don’t know how DirectWrite calls work.
Mouse should already work for apps that use VT-style (or *nix-style) mouse input. For apps using Win32 mouse mode, that support was actually just added in this release! (dunno how that was missed in the release notes 😨)
Note that you'll have to have your app disable <code>ENABLE_QUICK_EDIT_MODE</code>, there are more details in #9970
I definitely think the console/terminal performance in Windows needs significant improvement. God knows how many times I've suppressed the output of commands because of the significant performance cost. And I will happily admit that I am not anything close to an expert on any of the topics this video/issue covers.
However, I don't find the video entirely persuasive. He spends so much time ranting about "excuses" the developers have made, and repeatedly exclaims that this is a simple fix that could be done over a weekend or whatever.
Here's the issue in question where the debate takes place. Again, I'm not an expert, but the discussion here seems fairly reasonable and honest to me, and not peppered with excuse-making as this guy claims.
In fact, DHowett says they'll use the issue for for tracking related performance improvements and thanks him for providing the termbench program. That doesn't seem dismissive at all to me.
It's the OP himself who closes the issue after being gently called out for his tone, which I think was fair. His assertions of how simple and easy it is to do X (which he also constantly repeats in the video) come across as a little condescending to me.
But my question is, if it really is so stupidly dead simple, why create a separate fake terminal? If drastically improving the performance of the Windows Terminal was as simple as he claims, why not just do it yourself? I would find that more persuasive. I can only assume it's because he thinks that would take a lot more work than the weekend he spent building this demo. How much more work, and why? Is it because it's perhaps not so simple a problem to solve?
Creating a separate demo terminal just raises questions for me as to whether he's really understood and met all the requirements/constraints that the Terminal is built under. Maybe he has (he certainly claims to), but it's impossible for me to know as an outside observer.
> this was his coup de grâce in some lengthy argument about terminal optimization that none of us were present for
https://github.com/microsoft/terminal/issues/10362 and I think the specific comment that tipped him over the edge was this one
It's not just about watching text fly by… there are real usability issues in Windows Terminal such as not being able to CTRL-C when there is a large amount of text being output. It's especially bad over SSH, so if you accidentally run something that outputs a ton of stuff, you're pretty much hosed for like 30+ seconds.
One of the things pointed out was a lot of strings were created. See here. This was also part of the issue with long GTA load times a few months ago. This is actually a very common problem.
Now, if you use less CPU, all else being equal, you burn less energy, because they underclock. I'm not 100% sure, but I think the same happens with GPUs.
If I read it correctly, the offload to the GPU is already there, so we are already burning energy for that.
I can't extrapolate my experience, but I use a Mac for work. There's a bug in my workflow that I didn't bothered fixing that causes some Docker containers to live more than they should. They burn CPU. I often run out of battery in a matter of about 1 hour when they run. It lasts about 6-8 hours when they don't. CPU usage does affect battery life. That's a fact. That's also why every consumer architecture is moving to LITTLE.big and the like: having less power hungry cores for the regular loads and more powerful ones when needed optimizes battery life.
And again, if your problem comes before printing to the screen, then piping will still use those resources.
EDIT: the mention to using a Mac comes from Docker running in a virtual machine for Mac; in Linux it's just namespacing and stuff like that, under the same kernel, which makes for better resource distribution.
- It's not cmd that's getting a new version, it's conhost. The Windows Command Prompt has nothing to do with this. Certainly not the lexical analyzer of the cmd parser (why would it?).
- You should read a (now 19 year old) document about giving more indifferent options to users.
- You are of course welcome to find the proper place in the code yourself; the new Windows Terminal is open source.
> Recent apps like Windows Terminal aren’t .NET, which can be justified from a performance point of view but is also a slap in the face.
Wrong example. At this stage, the fact that most of the project is C++ has more to do with legacy.
On one hand, Windows terminal is based on the original conhost which of course was made in C++ (since C# didn't exist at the time). On the other hand, all samples (but one) are written in C#: https://github.com/Microsoft/Terminal/tree/master/samples
This is a matter of context: text rendering is factually hard, but when you aren't actually working on the hard part (e.g. https://github.com/microsoft/terminal/issues/538), it makes "text rendering is hard" a pure excuse, no matter how nice you appear.
It actually is from Microsoft, here's an article about it. It's also open source, so you're right it can be found on Github.
We've seen employees post issues on Microsoft's GitHub projects with higher build numbers before. In fact, we've even seen a screenshot that shows an updated context menu selection color.
This does not necessarily mean that the public Dev branch is changing now.
If I had to place my bets, I think we're getting 22000.71 next. Perhaps the branch will change soon, but employees keep posting from newer builds here and there. :D
> That's not quite what it says, though. It's also unclear what that mean. Does UWP "make sense" for Terminal and Calculator?
Calculator and Terminal are pure UWP applications. Terminal uses runFullTrust capability which allows it to run non-UWP applications.
It makes perfect sense to make utility applications as UWP.
I already replied to your other comment but seeing as you asked the direct question I will reiterate:
Windows terminal, due to it's low/fluctuating FPS, causes issues with VRR monitors because the monitor refresh rate syncs to the FPS. Everything on the screen (inlcuding other apps) becomes very choppy as a result.
I personally do not use WT for this reason. Here is a GH issue of other's reporting the same issue:
https://github.com/microsoft/terminal/issues/649
(Yes I am aware there are suggested solutions, they don't work and have problems I can't be bothered explaining).
Windows Terminal seems to have all of those, except the privileged/administrator one (which requires running a separate window). But it has some known performance issues that make it not as responsive as other terminals in certain scenarios, which makes it not as pleasant to use (cannot CTRL-C or switch tmux windows during large text output).
For now, most of the settings are only accessible in a json file - here's the md about them:
https://github.com/microsoft/terminal/blob/master/doc/cascadia/SettingsSchema.md
>As of today, the Windows Terminal and Windows Console have been made open source and you can clone, build, run, and test the code from the repository on GitHub: https://github.com/Microsoft/Terminal
>
>This summer in 2019, Windows Terminal previews will be released to the Microsoft Store for early adopters to use and provide feedback.
>
>This winter in 2019, our goal is to launch Windows Terminal 1.0 and we’ll work with the community to ensure it’s ready before we release!
Why assume that? refterm clearly demonstrates that the problem is easily solvable.
Did you know: refterm has features that the windows terminal does not have, like arabic shaping
https://github.com/microsoft/terminal/issues/4122
https://github.com/microsoft/terminal/issues/538
Did you also know that supporting arabic shaping and other unicode features is provided by "uniscribe", the official system library for doing that stuff in windows?
Yea, see, it's not that "windows terminal has a lot of features".
No.
It's just poorly implemented.
Refterm outsources the "complex" text problems to the operating system (windows).
If you're interested in this then you should at least be aware of where the info is that will tell you how to build it....
If you cant get that far a beta build isn't for you.
https://github.com/Microsoft/Terminal
Check the readme
No. They've stated their working on a scheme that could possibly support this but right now it can't because it is considered insecure.
https://github.com/microsoft/terminal/issues/632#issuecomment-491033558
Windows 10 already has that. There's a setting called "Acrylic" that, when enabled, adds blurred transparency to the profile you enable it in. I'd never consider it my favourite terminal, but from what I've seen it's still way better than what's usually available in windows.
As with most of Windows' shortcomings, I thought it was simply unwilling — until this past June. Microsoft is putting resources into building better, and failing badly at it. Is that "unable" as in they lack sufficient expertise within the organization? Or maybe they're just "unwilling" to put the appropriate expertise towards the problem since it's more needed elsewhere (i.e. kernel work), leaving the console update in incapable hands.
I sure think so, but I'm obviously biased 😜 It really depends on how many PuTTY features you're really using. If you just want to be able to easily connect to a couple simple ssh endpoints, then yea, absolutely. But if you're a heavy user of things like auto logging(terminal#642), or changing the sequences sent by certain keys, or more elaborate connection settings, then you might want to stick with putty.
Have you ever looked at the github for Windows Terminal? There was recently a big drama discussion about its performance in rendering text vs Linux's terminal. One of the MSFT developers suggested the fix was equivalent to a PhD research project after the issue creator said he'd be able to fix it over a weekend. That's how bad things are at MSFT and they really don't like looking incompetent compared to external developers.
https://github.com/microsoft/terminal/issues/10362
First, it was clearly not said as a joke in context. Second, the reason it has riled people up so much is that the guy making the complaint proved them wrong in a weekend. No matter how skilled he may be (he is), Microsoft of all companies should have the resources to figure this kind of thing out.
> if I can do this part better, why can't you do this part better?
This is a completely valid question to ask in this instance. It's rendering, which is an isolated system. You tell it what glyphs to render and where. The fact that Windows, as a whole, is large and complicated is irrelevant.
> Casey even admitted as much when he said he wasn't even sure his Arabic rendering was correct for all cases.
Windows terminal doesn't display Arabic properly at all so I don't understand why you've even brought this up. According to MS, rendering Arabic right to left is also apparently really hard and a lot of work despite Casey having implemented it here in two days.
All this shit you've written about Unicode being hard is also irrelevant. DirectWrite deals with all of that, which Casey was using and his renderer was still faster. Most of the things that make text rendering hard in the general case don't apply to mono-spaced font rendering, which is what terminals do.
>Pretending it isn't because you can build a subset of the features required to render modern unicode is, as I've stated, a bad faith argument.
What does windows terminal do in terms of text rendering that Casey didn't implement????? Seriously are you even reading what I'm writing? What is this mythical superset that Windows terminal handles, of which Casey only implemented a subset?
Fuck me, Windows terminal doesn't even do right to left rendering of Arabic and in many cases doesn't display Arabic characters correctly at all. Seems to me that Casey's renderer is more fully featured than the Windows terminal in terms of unicode support.
It is not. In fact, the new windows terminal is using UWP through XAML islands.
If I remember correctly, It is also the only way to make applications on the Xbox platform.
The 3.0 update to Windows UI Library (WinUI) will decouple UWP from the operating system.
WinUI is actively being worked on, so it's definitely not discontinued.
You can download the new Windows Terminal icon from the official GitHub page, should you just want to use it as a replacement for the standard Command Prompt: https://github.com/microsoft/terminal/blob/master/res/terminal.ico
You can build it yourself from cloning and building the repo: https://github.com/Microsoft/Terminal
​
its very alpha though its not going to be released GA until later this year if I remember right.
For large amounts of text, /u/mrcaptncrunch 's option to create a new file is the most efficient. If you only have a page or two of data, another thing you can try is to use a different terminal program, like Windows Terminal:
- Download and install: (https://github.com/microsoft/terminal/releases/tag/v1.11.2921.0 download at the bottom).
- Configure it to ssh to your host: https://docs.microsoft.com/en-us/windows/terminal/tutorials/ssh
- Once you are connected to the host, generate the data you want to copy.
- Then, maximize the window and use ctrl+mouse wheel to quickly change the font size down to something tiny.
- When all the data you want to copy is on the screen, you can select it with mouse and then right click and it will be in your Windows buffer.
- Once you have copied the data, you can zoom the text back to normal.
Unfortunately, the team that would be best suited to make this kind of change has already confirmed that it is unlikely to ever happen, because in their estimation there is too much risk in changing this, or even anything in cmd.exe:
https://github.com/microsoft/terminal/issues/217
Which is too bad, because the Terminate batch job prompt is really annoying and PowerShell sucks.
As others have mentioned get WSL. But I'd also recommend getting the new Windows Terminal (it's a beta version), you can find it on https://github.com/microsoft/terminal or in the Microsoft store.
The problem with WSL mostly is that it's annoying to switch and transfer files between the subsystem and windows. So I'd suggest using an FTP or SFTP drive for remote transfers, my personal setup is using SyncThing. Otherwise write your software in the windows :C drive folders and run the bash commands there.
Basically no.
cmd.exeis never getting updated. Period. Literally every time we've tried, it's come back to bite us, so it's in maintenance-only mode.powershell.exethat ships with Windows is powershell 5, which is quite a bit out of date these days. It's also probably not getting updated any time soon.pwsh.exe, or "PowerShell Core" though, is receiving updates. You might be able to ask on their repo, https://github.com/powershell/powershell.
Interesting that you want new tabs, with the same path, with different shells. That's a specific request I don't think we've heard before - mind filing it over at https://github.com/microsoft/terminal?
Windows Terminal just released in the store as a preview like a week or so ago. There's lots of work left to do. Check out the GitHub! There's also a pretty good video talking about some of the features that someone put together up on YouTube.
It looks like the available settings are documented here.
If anyone is Running Windows 10, They are now slowly but surely integrating Linux features and this includes the Bash Terminal and Ubuntu 16.04. Something is also in the works called a Windows Terminal
So for now, OP if you are running windows 10, download
This is all you really should give a shit about if you care about software freedoms.
https://github.com/microsoft/Terminal/blob/master/LICENSE
I couldn't give 2 shits about any company, but if they are releasing software under open source licensing(like that there MIT license that I just linked), then that is objectively a good thing. It's all 'bout that license.
> Is there a good terminal out there written in Rust?
Personally I've never understood this desire. Sure, I like Rust a lot, but when I'm using an application I don't really care what language(s) it is written in, so long as it does its job well and efficiently. I usually use the new Windows Terminal which is actually not half-bad, though I often use the integrated terminal inside VS Code as well.
As far as terminals written in Rust, I used to use Alacritty which is decent, but I don't use it any more.
This is also an issue for the Terminal: it's not possible to run it in full screen on a default Windows 11 installation without a white line at the bottom: https://github.com/microsoft/terminal/issues/11474
(I thought it was sometimes a thin blue line, but it may just be the accent color effects)
While that one is left open and somewhat regularly updated, you may want to track this one: https://github.com/microsoft/terminal/issues/5000
This is where they're trying to rebuild the process model so they can support elevation.
From the FAQ
> Windows Terminal requires a good number of Windows-specific technologies. We unfortunately won't be supporting it on Mac or anywhere else any time soon. There are some really good terminals on OS X, including iTerm and Hyper, and an uncountable number of good terminals on Linux.
This was tracked by microsoft/terminal#9320 and the upstream microsoft/microsoft-ui-xaml#4554, and was fixed for the Terminal in microsoft/terminal#10922, which should be shipping in 1.11 preview later this week ☺️
I think it may be related to these issues:
...but I have no idea about the technical details, just that the behaviour differs. Let me know if you still think I should file an issue.
The console features (like VT sequences) are not tied to the PowerShell version but rather conhost itself. While not official and in no way supported by Microsoft you can actually replace C:\Windows\System32\conhost.exe with OpenConsole.exe from the Microsoft Terminal app. OpenConsole is essentially conhost but with some of the newer features and bufixes that were never backported. You don't even technically have to replace conhost.exe, you can open PowerShell with OpenConsole by running OpenConsole.exe powershell.exe (OpenConsole.exe needs to be in the PATH here).
This is in no way supported by Microsoft so proceed with caution. You can learn more about here https://github.com/microsoft/terminal/issues/8101.
There’s a roadmap item to look into making it the default console for applications https://github.com/microsoft/terminal/blob/main/doc/terminal-v2-roadmap.md#20-scenarios. Last time I checked there was a pretty in depth draft doc on how they are planning on implementing it.
From your reaponses here it seems you are using the default terminal, which is called conhost and not like someone else said "cmd.exe".
Theme information for conhost is stored in the registry and you can edit it yourself or import other peoples themes as a .reg file.
Another option is to use ColorTool which allows you to import iTerm2 themes which you can find many of because iTerm2 is a very popular Mac terminal.
Then use ColorTool to import this: https://github.com/mbadolato/iTerm2-Color-Schemes/blob/master/schemes/Gruvbox%20Dark.itermcolors
Do yourself a favor and install the new Windows Terminal. It's fantastic and will make your command-line experience, whether running Linux command in WSL or using something like PowerShell, much nicer.
microsoft/terminal: The new Windows Terminal and the original Windows console host, all in the same place! (github.com)
>Why aren't more Windows servers headless, as is the standard for Linux?
Shitty legacy 3rd party products that where never designed to be run headless.
>How can I remote directly into a Windows server's CLI without dealing with the crappy stuttering GIF-GUI?
Remote power shell commands.
>Why do Windows admins still use PuTTY? Surely there is a more comfortable terminal available, right? Also why is Powershell so ugly and hard to read by default? Does Windows come with a nicer monospace font?
There are other 3rd party options that have existed, howeve you probably want to checkout the new Micrsoft Terminal.
That file is JSONC.
You get those errors because, instead of treating it as such, you treat it as JSON.
Again, either you treat it as the JSONC it is (tooling compatible with JSONC), or you tweak your JSON tooling to accept comments, or you insist on treating it as the JSON it is not and you live with those errors.
Either way, the brain dead dummies at MS are at fault, here, by exporting a JSONC file with a JSON extension: https://github.com/microsoft/terminal/issues/2292. Instead of complaining about how you are treated here by unpaid volunteers I'd suggest voicing your frustration on that issue and let those overpaid idiots fix their own mess.
The default profile settings include a rather large border of 8px on all four sides. It looks like this is what you are seeing here. If that's the case, you can adjust it with the "padding" per-profile setting.
This right here is the right answer. Use the installer from the Releases page. Since 0.11, we fixed some issues with our dependencies too, so the .msix from this page should work better in even more scenarios.
I've tried installing the app on my domain admin logged on locally, made sure it ran, then swapped back over to my standard user and tried running WindowsTerminal.exe as my admin account only to be met with a permissions error- the same one I had when it wasn't installed on that user.
There's actually a thread tangentially about this already on github (it's really more for getting an offline installer for servers, but should solve this as well), the long and short of it basically comes down to "we're working on it."
It appears that it comes down to limitations of UWP for now.
Looks like this issue: https://github.com/microsoft/terminal/issues/832. I think Conemu might be using conhost for rendering.
Try and see if it happens with a different terminal, I use wsltty and it should also be fixed in the new Windows terminal.
This issue is kind of a deal-breaker for me, and it doesn't look they're ever going to fix it. I guess I'll keep looking.
The issue is that cls or Clear don't clear the history, as they do in the old fashioned cmd or powershell consoles. For instance, this sequence still leaves you with a big scrolling history. The primary reason I ever clear is so that I can find the beginning of the next command by scrolling to the top.
cd \ ; dir -Recurse clear
You may be interested to look into the New Windows Terminal, intended to replace CMD/PS windows (don't worry the old ones won't go away).
You can take a look through the source code to see how they did it and see if you can adapt it to your purpose or at least get some ideas.
The backslash could be related to AltGr issues? Looks like it could be resolved soon.
Also there is multipane support in the works, but I haven't tried it and it may not have a default keybinding.
D'oh! Yeah, pretty obvious what you meant... once you point it out.
You can still compile the terminal yourself from the github repo. They've simplified the process considerably from the original commits. All you need is Visual Studio Express or Community... whatever the free version is called at the moment.
I have it running, but it's very alpha. The Terminal part works fine but a lot of the UI niceties are still coming/in-development.
Everything is on GitHub. You can follow a good build guide here: https://github.com/microsoft/terminal/issues/489
Here in the README.md of GitHub repo: Azure DevOps
Select a build of the master branch and download the artifact. Use whatever tool to decompress CascadiaPackage_0.0.1.0_x64.msix. Execute Add-AppxPackage -Register AppxManifest.xml inside the decompressed directory, and it should work.
While it is fixable by setting BCE as described, it is probably a bug related to the Windows terminal (conhost in your case): https://github.com/microsoft/terminal/issues/832. For instance wsltty does not exhibit this behavior.
Here's the source code for Terminal. Was anyone able to successfully build and install it locally? I am getting too many random errors.
Your classes may be done by the time WSL2 is released, but you should also check out the new Windows Terminal. It will have a drop-down list to open a new terminal running CMD, PowerShell, or any of the WSL distros that you have installed. I actually just put in a PR to auto-populate the WSL part of the list :) https://github.com/microsoft/Terminal/pull/695
I serve at the pleasure of the community. Most of the most highly requested features are all GUI based. If that's what the community want's, that's what the community gets 😄
Cascadia Code, it's a relatively new font created by Microsoft, developed alongside Windows Terminal. It is also the default font in Visual Studio 2022.
I don’t know about humor, but the smug sanctimoniousness and borderline hostility your colleague originally exhibited in this GitHub issue really left a sour taste in my mouth, enough that I didn’t contribute much further after my initial dive into Terminal: https://github.com/microsoft/terminal/issues/610
#10362 is the one I remember, and I suspect it's the one Microsoft are talking about when they say "a kerfuffle we caused in the summer of 2021". This GitHub thread got a little heated.
The Windows Terminal is the definitive terminal on Windows, and we're not about to ship another. Command Prompt and PowerShell are shells, like bash, fish, zsh, etc. More reading: What's the difference between a shell and a terminal?
This also exists on that page, apparently.
> The hinting on the brace ligatures was incorrect in the Italic style, which looked downright hilarious.
>Technically, what happens when the OS determines that you're launching a console application that doesn't currently have a console server, it creates a new conhost for that process, and aclls some private APIs to re-parent the commandline application as a child of conhost.exe. In order to connect the client to the conhost.exe it's about to spawn, it creates a bunch of console handles in ConDrv, and passes the server handle to conhost on the commandline. That's why you'll see the commandline for conhost typically be conhost.exe 0x4 - 0x4 is the value of the console server handle that the OS has created for this console instance.
source: https://github.com/microsoft/terminal/issues/8101
cheers!
I don't know the answer to that question but depending on how much Windows support you need you can use the Windows Terminal which has this virtual setting enabled by default (assuming a Windows version > 1903) so pure ANSI escape codes will work out of the box.
Not supported in windows 10 and never will be, most likely. You'll have to upgrade to 11 since that's the only version of the OS that supports changing the console host.
https://github.com/microsoft/terminal/issues/10869#issuecomment-963058614
If you can get a consistent repro outside of neovim, could you file this over at https://github.com/Microsoft/terminal ? I don't think I've seen this variant specifically. Removing neovim from the equation might help identify the root cause here.
There are (as far as I know) only two official ways to get it. You can either get it from the Microsoft Store. Don't worry, it's still free.
Or from GitHub, which happens to be the official home of the project.
Try the new Windows Terminal. It has all those features (resizing, escape sequences).
Note that a terminal (emulator) and a shell are not the same. A shell is a command interpreter. It understands commands and sends back responses to that command. PowerShell is a shell. A terminal (emulator) is, where you type in the commands. It sends the commands to a shell and prints back the response.
It means, that you can use a terminal with any shell underneath. So, Windows Terminal can be used with PowerShell, Bash, CMD, ... whatever you fancy. Colorful prompts and outputs are entirely possible with PowerShell, if you use a decent terminal emulator. Or you use a decent terminal emulator with any other shell.
OP asked about terminal and you are talking about shell and kernel...
Windows Terminal is an open source program, which allows you to interact with any shell. It is the same as terminal emulators we use on Linux.
Oh, there is one thing I did that I forgot about: added Windows Terminal from github. I used the "Via Github" method here:
https://github.com/Microsoft/Terminal
... which is basically downloading the msixbundle from there, and using a Powershell command to install it.
I have no idea if it will help, but it's minimal impact and it's easy to uninstall again if you don't want it.
May I ask if your problem is still present only when using editors such as neovim? If so, make sure you are using the stable or nightly release. Additionally, I installed Windows Terminal from the Github repository. Please let me know if that helps! I know how annoying this bug is.
I've never had this but it says you need "Microsoft.VCLibs.140.00.UWPDesktop" maybe start there? I started Googling and found some possible fixes? Which eventually lead be to here. If this doesn't work, then sorry idk?
GitHub shows that they just pushed out an update to stable that includes the default terminal feature
https://github.com/microsoft/terminal/releases/tag/v1.11.2921.0
Yeah pretty much. .bashrc is not an important file really, just a file that is run when the shell starts up.
That export command just sets the default browser of your Linux distro to your windows Firefox install.
I’d grab this program. It’s the new terminal from Microsoft.
When it’s open you’ll see an arrow by the tab screen. Click that and select your WSL distro you want to work on.
Run ‘nano ~/.bashrc’ and it will open a text editor. You can move with the arrow keys here. Just go to the bottom and paste that in there.
“Ctrl X” is to quit. It will ask you if you want to save. Press “y” for yes then enter. It will ask for a name for the file and just press enter again without typing to keep the same name.
You’ll then need to run ‘source ~/.bashrc’ to reload the changes or just close the terminal and open a new one
See https://github.com/microsoft/terminal/issues/11415
Tl;dr: default terminal feature not ready for stable release yet...hopefully by the 1.12 Terminal release
set shell=C:Users\myuser\AppData\Local\Microsoft\WindowsApps\Microsoft.Powershell_XXX\pwsh.exe " :shell and :terminal use powershell 7 instead of default
" And for the visuals If has("termguicolors") set termguicolors set t_ut="" " https://github.com/microsoft/terminal/issues/832#issuecomment-493747616 colorscheme peachpuff endif
" I also have set shellcmdflag=-command Not sure what it does
Last comment on the github issue muratori made explains pretty well that he, actually, does not know completely what he's talking about.
So no, the issue really is more complicated than it looks. And it's kinda disturbing how many people here are so arrogant to even think that they alone are so much smarter than dozens of experienced developers working on the Windows Terminal or the Open Source community that has access to the same codebase.
Shame you're not on Mac, because iTerm2 has exactly the functionality you are looking for.
That said, I found this page where people seemed to have some ideas on how to accomplish part of what you want.
Sorry that I can't reproduce your question, but the question won't prevent your code execution. At least you can get right result, you may ask in microsoft/terminal for more help.
If you like terminal and have difficulty binding shortcuts have a look at the following functions: event-apply-{control}-modifier
They are magics!
Got mentioned here: https://github.com/microsoft/terminal/issues/3483#issuecomment-835816593
Also reminds me of this comment from the Windows Terminal repo. It seems passing a std::string_view to a function is much more complicated than just passing a const char* and size_t thanks to the Windows x64 ABI.
Microsoft be like: "I believe what you’re doing is describing something that might be considered an entire doctoral research project in performant ..."
https://github.com/microsoft/terminal/issues/10362#issuecomment-862844333
From what I have tried, it's impossible. Yes, you can run WSL or Cygwin, but when you are using virtual machines, it's easier to sping a small Linux VM and use the Microsofts terminal to connect to it. https://github.com/microsoft/terminal. This is the way I do it when I need Bash shell, however, this way I have no option to manage host OS.
Windows Terminal is developed separately from the core Windows OS as an open source project. Issues with Terminal or (in many but not all cases) Console Host can be discussed at https://github.com/microsoft/terminal/issues
Are you talking about in the terminal? I suggest you give WindowsTerminal a try. You can set settings like font size in the profiles.
Easiest way to install is via the Windows store.