Will do.
On Friday, October 28, 2016 at 5:17:38 PM UTC, David Anthoff wrote:
>
> Yes, PRs to the main repo are welcome. It would be great if you could
> write up a short issue describing how this code goes about things. There
> are quite a number of strategies on how to achieve things in VS
Yes, PRs to the main repo are welcome. It would be great if you could write up
a short issue describing how this code goes about things. There are quite a
number of strategies on how to achieve things in VS code (language server
protocol vs everything in typescript vs mixed language solutions)
-users@googlegroups.com] On
Behalf Of David Anthoff
Sent: Thursday, June 23, 2016 12:07 PM
To: julia-users@googlegroups.com
Subject: RE: [julia-users] Re: VS code extension
Yes, VS Code does feel a lot snappier than Atom. I never had problem with
installation or updating with Atom, though
Yes, VS Code does feel a lot snappier than Atom. I never had problem with
installation or updating with Atom, though.
Right now the VS Code plugin is very bare and has hardly any features (syntax
highlighting, latex completion, and one command to open a package in a new
window). Right now I
Of Eric Forgy
Sent: Wednesday, June 22, 2016 5:05 PM
To: julia-users <julia-users@googlegroups.com>
Subject: Re: [julia-users] Re: VS code extension
Hi David,
This is awesome. Thanks for this. Out of curiosity, is this the same syntax
highlighting used in Juno? It feels a little dif
Hi David,
This is awesome. Thanks for this. Out of curiosity, is this the same syntax
highlighting used in Juno? It feels a little different and I've gotten used
to Juno.
I was able to get the same Julia.tmBundle to work in Visual Studio (not VS
Code) and filed an issue here
The VS code extension now lives here
https://github.com/JuliaEditorSupport/julia-vscode.
Cheers,
David
From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On
Behalf Of Lyndon White
Sent: Tuesday, June 21, 2016 7:53 PM
To: julia-users