Wasn't mouse support in the console for decades as well? At least it has worked in Far for ages. Or is just the integration with Linux console applications new?
What’s New in Bash/WSL and Windows Console
31–40 of 251 posts
Re: What’s New in Bash/WSL and Windows Console
#32The inotify implementation looks very promising! Editing source files in a Windows-native IDE and having changes picked up by, say, node.js is a great workflow. I'm yet to try it out, but I wonder if the problems with editing files in the linux filesystem[0] is going to be an issue with this? [0]: https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-n...
I tried it and it works just fine. Changes from WSL(vim) and windows IDE were picked up correctly by nodemon.
Re: What’s New in Bash/WSL and Windows Console
#33Earlier quoted context omitted.
Your entry point to WSL is bash and while you may be able to compile and install other shells, calling it "bash" isn't too far from the truth. Really the awkwardness of the naming is more of a testament to the power of scripting on Unix-like OSs (eg how scripting is a first class citizen and how most of the ecosystem is modelled around CLI, and thus scripting, support) more than it is an insult. As for cygwin, that w…
EDIT: Your choice of shell can be something different than bash... you opt to use zsh or fish or another shell. Therefore saying "Bash for Windows" can be objectively said to be unnecessarily confusing/inaccurate. I think Cygwin was less convenient than an ABI such as WSL, but by no means "terrible". Cygwin was initially released around 1995, it served a valuable purpose before the first VM products came along.
>EDIT: Your choice of shell can be something different than >bash...
Bash is the default shell. It's also the generic command you run to launch the WSL environment.
While the multiple names for the same subsystem are a little nebulous, Bash is far from being as confusing or misleading as you're attempting to portray.
Also, editing your original snide grammar dismissal due to the downvotes it received isn't appreciated. That's deceptive at best. Either own your bad behavior or apologize for it, but don't edit it and pretend like you were being rational.
Re: What’s New in Bash/WSL and Windows Console
#34Earlier quoted context omitted.
A lot of resistance some will have to WSL will be old battle scars from Microsofts past behaviour. Microsoft have done a lot over the years to troll the Linux community. While many of the younger HN members will be familiar with the "new open source Microsoft" some of us oldies have had to endure IE breaking the web plus ActiveX / Silverlight and other MS web lockins. Comments like "open source is communism" from top…
> A lot of resistance some will have to WSL will be old battle scars from Microsofts past behaviour. I'm also not convinced they've changed at all when I see what they've done to things like skype, where they have somewhat of a monopoly (thanks to office).
Or more recently, Microsoft's refusal to remove "curl" from Powershell, where "curl" was an alias to a totally different Windows function that barely resembled curl.
Re: What’s New in Bash/WSL and Windows Console
#35Anyone tried deploying a linux program on windows via WSL?
Re: What’s New in Bash/WSL and Windows Console
#36Ok, this is awesome, if everything works as advertised. I have been mostly a Linux user for quite some time - at least on my own computer, clients always have Windows. But this year I bought a Surface Pro as a secondary device. I first evaluated WSL and really liked it, but I switched to Hyper+Git Bash because networking in node.js was not working properly, and because I could not start Windows programs from the comm…
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.
Re: What’s New in Bash/WSL and Windows Console
#37Symlinks!
Windows has always been such a pain in the ass with regard to symlinks (my revision control workflow for big projects spread across multiple repos always includes symlinks). So, this is cool.
Re: What’s New in Bash/WSL and Windows Console
#38Earlier quoted context omitted.
I've definitely had issues doing an upgrade on a real Ubuntu installation. Years ago I needed to update a more or less clean install of Ubuntu Desktop. It managed to completely break Gnome somehow (This was before Unity). I'm guessing things are better now and that the server distribution is better for this but I could see complications happening.
I used Ubuntu Server LTS a couple of times. The 14.04 version which is supported until 2019 still has the bug that it won't clear out old kernels after upgrading them. So if you don't look into your /boot partition now and then it fills up and breaks your installation.
Can you link to a bug report? dist-upgrade (as opposed to upgrade) should remove the old packages;that's its whole point...
Re: What’s New in Bash/WSL and Windows Console
#39>Upgrade In-Place ...though this may not result in an optimal instance. Wondering why such a disclaimer? Ubuntu apt upgrades are reliable. Or is it related to WSL? Anyway good job WSL team.
If you're asking why Microsoft's advice is to format and reinstall, well, consider who it's coming from.
Because you can upgrade from windows 3.11 all the way to 10, good luck with ubuntu.
Yeah, I see your point.
Re: What’s New in Bash/WSL and Windows Console
#40Earlier quoted context omitted.
Microsoft adds this amazing set of features and the only response you have is "your name is insulting the people you're trying to appeal to"? "Trying"? As if they're failing? Do you know how much people love this project?
A lot of resistance some will have to WSL will be old battle scars from Microsofts past behaviour. Microsoft have done a lot over the years to troll the Linux community. While many of the younger HN members will be familiar with the "new open source Microsoft" some of us oldies have had to endure IE breaking the web plus ActiveX / Silverlight and other MS web lockins. Comments like "open source is communism" from top…
> at least with WSL, if they do decide to cripple it once they have the customer base then it's pretty trivial for users to switch away again
Now that they're embracing the typical Linux userland, I can't help but ponder if they'll try shifting to the extend+extinguish part later on. I guess old habits die hard, especially when you got burnt multiple times already, although I'm not cynical enough to think this would be all planned beforehand but more like at some point some exec would notice this as a strategic opportunity to seize.
That said they're certainly winning some Linux users back, and if anything, this may even help in getting some Windows people used to Unix and Bash, reducing the gap for them to try their hand at some Linux distro. All in all, cross-pollination is good both ways.