Earlier quoted context omitted.
My theory is that the next version of Windows is going to use the Linux kernel. They can keep Windows 10 going for a few years yet (maybe up to 5?). That will give them time to work on cross-platform .NET, so new development will be an easy switch, and good quality Win32 emulation, which will be built someway on the work done on Wine.
>My theory is that the next version of Windows is going to use the Linux kernel. Windows 10 is the last version of Windows that Microsoft is making. It will be continuously updated instead of new versions being released.
What’s New in Bash/WSL and Windows Console
121–130 of 251 posts
Re: What’s New in Bash/WSL and Windows Console
#122The 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...
Microsoft: I suspect this blog post is out of date and that, post creators update, this is now safe. If so, maybe you want to edit it?
That was the main tripping point for me last time I tried out the WSL workflow. Mainly just because a bunch of files in our repo were apparently named in an ntfs unfriendly manner, so when I tried to merge etc. the repo would get corrupted.
Re: What’s New in Bash/WSL and Windows Console
#123Windows 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…
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…
Re: What’s New in Bash/WSL and Windows Console
#124Earlier quoted context omitted.
bash.exe on Windows is also GNU Bash: C:\Users\laumars>bash --version GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. The rest of the subsystem isn't called "bash", it's called "Windows System for…
Linux, BSD, Solaris, etc. have significant differences among them, and the source code needs to be aware of them. Same with all crossplatform software. But from the perspective of a Linux binary running on WSL, running on WSL should be the same as running on Linux. If bash is an exception to that, that seems more like a hack on Microsoft's part. If they implemented the execve() syscall and others, starting whatever o…
Re: What’s New in Bash/WSL and Windows Console
#125Windows 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…
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…
Re: What’s New in Bash/WSL and Windows Console
#126Earlier quoted context omitted.
My theory is that the next version of Windows is going to use the Linux kernel. They can keep Windows 10 going for a few years yet (maybe up to 5?). That will give them time to work on cross-platform .NET, so new development will be an easy switch, and good quality Win32 emulation, which will be built someway on the work done on Wine.
>My theory is that the next version of Windows is going to use the Linux kernel. Windows 10 is the last version of Windows that Microsoft is making. It will be continuously updated instead of new versions being released.
Re: What’s New in Bash/WSL and Windows Console
#127Earlier quoted context omitted.
My theory is that the next version of Windows is going to use the Linux kernel. They can keep Windows 10 going for a few years yet (maybe up to 5?). That will give them time to work on cross-platform .NET, so new development will be an easy switch, and good quality Win32 emulation, which will be built someway on the work done on Wine.
>My theory is that the next version of Windows is going to use the Linux kernel. Windows 10 is the last version of Windows that Microsoft is making. It will be continuously updated instead of new versions being released.
Re: What’s New in Bash/WSL and Windows Console
#128Earlier quoted context omitted.
My theory is that the next version of Windows is going to use the Linux kernel. They can keep Windows 10 going for a few years yet (maybe up to 5?). That will give them time to work on cross-platform .NET, so new development will be an easy switch, and good quality Win32 emulation, which will be built someway on the work done on Wine.
>My theory is that the next version of Windows is going to use the Linux kernel. Windows 10 is the last version of Windows that Microsoft is making. It will be continuously updated instead of new versions being released.
Re: What’s New in Bash/WSL and Windows Console
#129Earlier quoted context omitted.
We can argue about whether "nightmare" is overstating the problem but let's be honest that it's easily more than just "a bit annoying". The installer took an hour on one system and the options in those 5-10 pages are far from user friendly. Sure it's stuff I can manage being a seasoned Linux sysadmin but frankly I've found installing ArchLinux (with it's deliberately anti-user approach) easier; never mind your more "…
For problematic processes, I use kill -W -- that uses the TerminateProcess Win32 API, rather than Cygwin's POSIX implementation. I also use it to kill things like the Windows Update full-screen overlay on Windows 10.
Re: What’s New in Bash/WSL and Windows Console
#130Earlier 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…
ConEmu has the best UI I've ever seen in a terminal. Way better than anything I've seen in *nix.
- Minimal contrast in active tabs - can't be fixed due to Windows XP support.
- Flashes it's hidden console proxy on screen continually
- Settings menu with around 5000 options and no sense of heirarchy - something that's rare is just as prominent as something that's common
- Giant colorful icons and wasted space in the title bar. I can't throw my mouse to the top and pick a tab when it's maximised.
- Freaks out when your console is too large
- Does a bunch of things better done elsewhere: my profile bash/powershell profile sets environment variables, I don't need my terminal to do this.