> Microsoft only does what suits Microsoft's interests

As does any other company that wants to survive. I doubt Google will do anything against its own interests.

Anyone have any idea what theme they use in the gif that demonstrates the ruby auto-indent feature?

I believe it's One Dark Pro: https://marketplace.visualstudio.com/items?itemName=zhuangto...

I've been using "Atom One Dark" which is also pretty similar

https://marketplace.visualstudio.com/items?itemName=akamud.v...

I'd also like to know the name of the theme in the "Manage your .gitignore file" section.

https://code.visualstudio.com/images/1_14_gitignore.gif

The standout feature for me is the added support for SCM providers other than git. I also like the theming upgrades

Yeah, work is still ongoing with it: https://github.com/dotnet/corert

No, that is for standard .NET, I was referring to llilum for the .NET Micro Framework, the only one that has always been fully interpreted, which hasn't seen any updates in a while.

https://github.com/NETMF/llilum

So PSReadline looks really good and it seems popular too. I haven't used it yet but I would imagine that because it's a Powershell module it can't be easily used in other .NET languages like C#, F# or even VB

Lol, yes you can maxaf. Part of the reason I built this library in the first place

Library author here. I would love if people took it for a spin and gave me feedback. Also contributions are welcome, I'm currently trying to figure out ways of testing deeper into the library.

Do you plan to support the equivalent of ~/.inputrc to configure editing options (specifically vi editing mode)?

https://www.gnu.org/software/bash/manual/html_node/Readline-...

That's a good one. Although, considering I built the library to allow developers build their own bash like experiences I think it might be better to leave it up to them to define their own editing config files

Hi, I'm the author of prompt_toolkit. A library that does something similar for Python. Don't hesitate to copy anything you need. It took me a few iterations to get the API as I wanted.

One thing I underestimated was the importance of having all readline key bindings available. People are really sensitive when certain functionality that they are used to is missing. (And you've no idea how much functionality there is in readline until you have to implement it.)

Thanks jonathan, I'll be sure to take a look. Having feature parity with GNU Readline is something I'm hoping to have in the future, it's a lot of work but it's open source so Im sure I'm not alone :)

This might be the PS library he's talking about: https://github.com/lzybkr/PSReadLine

I found it terribly useful