Live data from Hacker News

What’s New in Bash/WSL and Windows Console

blogs.msdn.microsoft.com

211–220 of 251 posts

Re: What’s New in Bash/WSL and Windows Console

#211
post #125
post #112

Earlier quoted context omitted.

Edit for folks having trouble understanding: the post you're replying to literally mentions two of the best tabbed terminals for Windows. That's not the problem. A fast, inbuilt, 2017-era terminal is. - ConEmu has a UI that's a shotgun blast of shit. - Hyper still fails at basic shortcuts. - ConEmu plus other software still has a UI that's a shotgun blast of shit. - Some person's half maintained fork of putty is some…

Out of curiosity, what tabbed terminals on other platforms would you consider to be significantly better than ConEmu/Hyper? (I've never actually used any GUI platform other than Windows for any length of time, so I would be interested in seeing what other people do use.)

Apple Terminal, iTerm, gnome-terminal, konsole. I can't really name one worse than ConEmu.

ConEmu likes to do this cute thing where it stops accepting key presses. And with the all the options it has, "starting a new terminal in the directory of the previous" is nowhere to be found.

But still, it's probably the best on Windows if you want tabs.

Re: What’s New in Bash/WSL and Windows Console

#212
Does that mean I can change the font without editing the registry now?

Now that there is 24-bit color, is there actually a reasonable way to change the colorscheme, or are you still stuck with the same UI?

As far as I can tell, this is the first major overhaul of CMD. Full stop. We've been waiting.

Re: What’s New in Bash/WSL and Windows Console

#213

Earlier quoted context omitted.

"I do believe MS has changed. They don't seem to be the conniving organisation they once were" I think this ex-Microsoft employee might disagree with you. https://www.youtube.com/watch?v=wPFbAqICUJo

Could you add a brief summary of the video for those who prefer text for bandwidth (digital or cognitive) reasons?

sure. The guy in the video is a popular youtube personality; his name is Jerry Berg. He is an ex-Microsoft employee who worked on Windows and had access to Microsoft's internal SQL servers used to collect problem reports. He makes a few points in the video.

1. In the Terms & Conditions, Microsoft claims they get your IMEI number from mobile connect devices as part of their telemetry and then go on to say it's not PII (Personally Identifiable). Jerry explains how this is not true and explains how Microsoft through corporate partnerships can eventually link your IMEI data back to logs previously collected.

2. Jerry explains that there are two levels in the new Windows Creator program: A basic level and another, I forget what he called it, more verbose level. Jerry explains that 90% of the telementry data you might think is in the more verbose level is collected at the basic level. Kind of a moot point.

3. If you have turned off telemetry collecting features such as cortana and edge, by upgrading to Windows10 creator, these features are re-enabled and Microsoft says this is a bug but Jerry claims it's intentional.

These were the salient points I recall from the video. If you get a chance to view, I suggest giving it a watch. It's interesting.

Re: What’s New in Bash/WSL and Windows Console

#214

Earlier quoted context omitted.

You need to reread this thread because I am literally the only person who entertained your poorly written arguments and spoke to you like you weren't a troll. Instead of insulting me and demanding compensation you really should be thanking me for being the only person who gave your opinion the time of day. I wasn't the one who downvoted your comments. In fact quite the opposite as I actually upvoted your OP (I felt a…

laumars, 13 hours ago: >So while the trolling remarks of the OP are clearly unconstructive, i can at least emphasise​ with why he feels the need to speak out against MS. He just did so in a pretty lousy way. Just stay on topic and avoid personal attacks. I have been consistently referring to GNU bash, Linux and Linux software interchangeably. Creating confusion around those terms because is not in the best interest o…

typo: I have been consistently against referring to GNU bash, Linux and Linux software interchangeably.

Also against referring to GNU bash and bash.exe interchangeably. Or people trying to redefine what GNU bash is because of how it is distributed under Windows.

Re: What’s New in Bash/WSL and Windows Console

#215
post #36
post #13

Earlier quoted context omitted.

I recently tried starting Windows CLI programs from within bash and it worked just fine, but you have to specify the entire filename, like "./notepad.exe".

This is usually because, by default on many Linux flavours, the current directory is not included in your path environment variable.

Just to note that this (to run scripts/executables you must specify the cwd in the cli invocation)is also the case for PowerShell. So, not unknown in the Windows world.

Re: What’s New in Bash/WSL and Windows Console

#216

Earlier quoted context omitted.

What I do is start sshd in WSL then ssh to @localhost from mobaxterm which is quite a nice (tabbed) terminal app. Works a treat, even with the free edition. http://mobaxterm.mobatek.net/

MobaXterm is awesome. Except the performance is just crap. It's noticeably laggy doing basic things like opening tabs and stuff. Anytime it has to redraw/relayout it's just slow. And if you use RDP, the CPU just burns even when idle. It's so promising though, I paid for it.

I paid for it as well :)

I pretty much use it mostly for ssh and have never noticed any lag. There are one or two oddities, but I can live with them. It's miles better than plain old PuTTY.

If I'm doing RDP I use RoyalTS, another thing I paid for because it does RDP management so well:

https://www.royalapplications.com/ts/win/features

Re: What’s New in Bash/WSL and Windows Console

#217
post #209

Earlier quoted context omitted.

I really support ConsoleZ. The UI is sadly still a little bulky, but you can do a good bit of configuration for hotkeys. The tabbing is nice, and it also to my memory has panes, without ConEmu's weird hidden tab system for them. It has the added benefit of you being able to pick the terminal to spin up, and whether you want Administrator mode or not, on every new tab, so you can be working in a bash tab and pop a new…

Is that?: https://github.com/cbucher/console

It is, yeah. Chocolatey has a package for it, which is how I found it.

Re: What’s New in Bash/WSL and Windows Console

#218
post #208
post #112

Earlier quoted context omitted.

Edit for folks having trouble understanding: the post you're replying to literally mentions two of the best tabbed terminals for Windows. That's not the problem. A fast, inbuilt, 2017-era terminal is. - ConEmu has a UI that's a shotgun blast of shit. - Hyper still fails at basic shortcuts. - ConEmu plus other software still has a UI that's a shotgun blast of shit. - Some person's half maintained fork of putty is some…

> Some person's half maintained fork of putty is some person's half maintained fork of putty and we already have Windows openssh for SSH purposes. I wonder if an MS port/fork/patch-set contribution to putty might not be the best way to a great windows console host. At least until there's a native port of libvt. Putty gets a lot of the console handling right - while win64/32 openssh is pretty outdated and lagging as a…

Windows OpenSSH is excellent - use the one Microsoft maintain.

Re: What’s New in Bash/WSL and Windows Console

#219
post #41

Earlier quoted context omitted.

I also remember the standardization process of OOXML. https://en.wikipedia.org/wiki/Standardization_of_Office_Open... I also think their current strategy could be the one you describe. We're at the Embrace phase. It's not sure that Extend will follow but I wonder what it could look like. Maybe it will be something convenient you can do in Linux only if you're running it inside WSL. Given how Linux is used it should b…

It's named like this because it is a subsytem of the NT kernel (hence the Windows subsystem part) that implements Linux system calls to run Linux applications (hence the for Linux part). Naming it the other way around ie Linux for Windows would imply that the Linux kernel is involved which is actually not the case at all.

Also, they previously had a Subsystem for Unix (SFU/SUA), so they're being consistent with their naming. That was the old POSIX layer that included, IIRC, a shell script to wrap cl.exe to take gcc-like arguments, and you can get third-party compiled binaries of things like bash.

Re: What’s New in Bash/WSL and Windows Console

#220
post #75

Windows Console folk: any chance of tabs in the official terminal? Current Windows terminal options: - ConEmu: mainly excellent but a little dated - eg, the active tab color is hard to distinguish but it can't be changed, apparently due to maintainer's insistence it works on Windows XP. - Hyper: excellent but Ctrl C, Ctrl R etc broken in powershell. Adding tabs to the Windows console makes more sense than have a thir…

What is wrong with ConsoleZ?
Post reply on HN