goglenglish.blogg.se - Colorscheme only working in vimr

COLORSCHEME ONLY WORKING IN VIMR UPDATE
COLORSCHEME ONLY WORKING IN VIMR WINDOWS 10
COLORSCHEME ONLY WORKING IN VIMR PASSWORD
COLORSCHEME ONLY WORKING IN VIMR MAC
COLORSCHEME ONLY WORKING IN VIMR WINDOWS

COLORSCHEME ONLY WORKING IN VIMR WINDOWS

I just wanted to be clear with what I, as a customer and a developer, desperately want to see in Windows and that I frankly thought would be the case already in AU according the information out there. Of course I realize that you have a lot of priorities as all projects do (ours too). I do answer my customers even if they aim high). Update: Thank you very much for a great answer I really appreciate it (I don't understand though why you usually wouldn't reply as a Microsoft representative when a customer gives you feedback.

Great expectations? Yes! Unrealistic? No, IMHO.

I also expect individual Microsoft developers to escalate to decision makers/managers at Microsoft that they need more (or possibly a lot more) resources if they do and make them read this.

I further expect Microsoft managers, with the power to take the decisions to make this Microsoft's top priority, to read this and make it happen.

I expect Microsoft to already have taken the strategic business decisions to make WSL work perfectly on Windows and understand that this is their second chance to make developers go back to Windows.

Please go ahead and tell your rep if you think that will take the project forward faster. No, I tell it to right here and right now even if it is in the middle of a bug ticket since it is, to my experience, impossible to reach out to them in Microsoft forums and I don't have the time or energy to look around. I would love to hear feedback from you why you feel that this isn't an option for you.

Insiders will get it ~3wks after I complete a PR, and everyone else will get it when the next OS version ships.

COLORSCHEME ONLY WORKING IN VIMR UPDATE

When I do get around to investigating this, it's gonna come as an update with the rest of the OS.

COLORSCHEME ONLY WORKING IN VIMR PASSWORD

Breaking remote.exe, echoing your password to the terminal after submitting, segfaulting when running tree - these are all critical bugs, and those would get serviced (had we not caught them)

I would not describe a partial coloring issue to be a "critical bug".

And now the color support is great, with only minor issues, like the bottom of vim not painting. Priority 1 for AU was flushing out the VT engine enough that you could run basically any linux command-line app successfully, which hey, it did quite well.

Yes we knew that 256 color support was lacking in AU, that's why it was priority number 1 for CU.

We have some big long-term goals with the console, but it takes a lot of engineering effort to get there, and to get there without breaking any scenario that anyone has ever had. Most of them are down in the weeds priorities, getting real technical debt cleared up so that we can make more improvements in the future. I usually wouldn't reply to something like this, but hey, We have a lot of priorities at the moment.

We're the only ones who ever really contribute on GH. You really have your second chance here thanks to WSL but you need to put everything else aside and get WSL in top shape well, there's actually a couple more of us.

COLORSCHEME ONLY WORKING IN VIMR MAC

Look what happend with the Mac sales when developers started to use OSX.

COLORSCHEME ONLY WORKING IN VIMR WINDOWS 10

So I wonder When this critical bug, discussed in this thread, is fixed, when and how will we developer get the update? Will we need to wait for the next major Windows 10 release after Creators Update? That is of course not an option so I really really hope that you can release it as an ordinary Windows Update and very soon as a hot Please understand how important it is for your business to get WSL in perfect shape as soon as possible. Unfortunately Microsoft still doesn't seem to be there. I, and many many with me, don't care about anything else in the Creators Update but seeing that WSL is working perfectly for our developing needs. Yes, such a seemingly "small thing" as bad color support, making it not nice to use Vim, is enough for a very large bunch of developers to look elsewhere. As a developer, I had very high expectations on Creators Update in this perspective since the first release with WSL on Anniversary Update was with Ubuntu 14 and with very bad color support and overall didn't work well enough for professionals. Setting up coc nvim.Please understand that getting Windows Subsystem for Linux working perfectly should be absolute top priority from Microsoft if you want developers to use Windows 10 instead of another certain competitor.