Invoke Win32 applications with Bash on Windows(msdn.microsoft.com) |
Invoke Win32 applications with Bash on Windows(msdn.microsoft.com) |
I typically install it along with git and Git Extensions. It's great when you already know the bash way of doing something, hashing files for example.
Plus Bash on Windows isn't a new thing: we already have Cygwin, MinGW and I believe there was also some native Windows PE ports too. This is just a better implementation than the aforementioned three.
Like nearly everything, it's a context-dependent cost-benefit consideration.
This is amazing, now I can have emacs server in Linux running through bash with windows service manager.
This is fucking awesome. I hope they improve thing further and further.
The only and biggest problem : Windows ridiculous conemu. I am not going use a console which I can't resize without any problem. For the sake of God they don't have unlimited buffer option and hide scrollbar (permanently) or resize window without messing up text.
Sorry I don't follow. What resizing problems are you having with ConEmu? Works fine when I've tried it. We are talking about the same ConEmu, right?
This might rain on your parade a bit. Each island still has to know about the file sytem of the other island.
As we all know Microsoft messed up with mobile and web, but when it comes to software development they are ruler without even competition. Windows kernel is wonderful peace of software, and with this wsl they are literally showing industry how is software developed.
> 1 Use the same working directory as the CMD or PowerShell prompt > 2 Are run under as the WSL default user > 3 Have the same Windows administrative rights as the calling process and terminal
1 and 3 are not surprising. But 2? There's a WSL default user? Windows users aren't automatically mapped to unique Linux users? That seems problematic in theory. How does it work out in practice?
When they run bash for the first time, system asks them to create a default linux user. Typically, this is also the only user.
Mapping Linux users to Windows users would be quite problematic, e. g. with user such as nobody or apache that are typical to Linux.
As I'm reading the comments I keep seeing things that other people want to do that I never thought of...that's awesome.
As for the parent poster, they must be abusing the term `ConEmu`, a completely separate console program that can run win32 programs (including `cmd.exe`).
There are a lot of other people saying how amazing it is though, when functionality wise it's only just coming up to par with cygwin.
Edit - functionality wise as a usable bash shell, it's an acceptable linux virtual machine already.
Also, not being able to edit the WSL filesystem from inside a windows editor is a huge loss in terms of usage. It's worse than using Samba/CIFS to share a directory and edit across to a full VM. I happen to like my gui editor, but prefer to run in Linux.
At a guess one of them might be that apparently the Unix things like permissions and Unix-style metadata are stored in NTFS alternate streams (~"resource forks") that they may be worried some Windows programs might not handle quite right (ie, accidentally mangle/remove/destroy).
I'm using Bash on Ubuntu on Windows for Jekyll (because installing and keeping up to date Ruby on Windows is a terrible experience and this is a much nicer alternative). My files are in D:\Repos\..., I'll have VSCode open and Jekyll running in Bash in the equivalent /mnt/d/Repos/...
The word has uses outside of the PTSD context though, like gun or database triggers.
Why would them being self-diagnosed matter? Why would you react to it having been “made a mockery of” by reinforcing this supposed mockery? It only makes it worse for people who have to deal with it.
Because the self diagnosis is largely made up by people who don't understand what PTSD even is. It's like someone declaring they have cancer without going to a doctor.
> Why would you react to it having been “made a mockery of” by reinforcing this supposed mockery?
Because it's become part of the lexicon now. I don't think there's any going back. My usage was the "new" usage, no relation to PTSD was intended.