Re: [julia-users] Re: VS code extension

2016-10-28 Thread Zac 
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 code 
> (language server protocol vs everything in typescript vs mixed language 
> solutions) and it would be good to sort out what is the right strategy for 
> the extension, and how this new code fits in there.
>
>  
>
> *From:* julia...@googlegroups.com  [mailto:
> julia...@googlegroups.com ] *On Behalf Of *Zac
> *Sent:* Friday, October 28, 2016 8:40 AM
> *To:* julia-users 
> *Subject:* [julia-users] Re: VS code extension
>
>  
>
> Ok then, https://github.com/ZacLN/julia-vscode . I'll look into trying to 
> make a pull request on the main repo. 
>
>  
>
>  
>
>  
>
>  
>
> On Friday, October 28, 2016 at 3:29:17 PM UTC, Tony Kelman wrote:
>
> The repo's MIT licensed, so unless this person changed the license of 
> their additions, yes. Best to preserve git authorship attribution if you 
> can. Pull requests to the JuliaEditorSupport repository are encouraged, I 
> imagine.
>
>
> On Friday, October 28, 2016 at 3:31:56 AM UTC-7, Zac wrote:
>
> Hi, I'm using a fork of this that implements completions, function 
> parameter hints, documentation hovers, linting and definitions. I pulled it 
> from another fork that has subsequently disappeared (github.com/novatena). 
> This 
>
>  
>
> Given that someone else did most of the work is it ok to share it here? 
>
>
> On Tuesday, July 5, 2016 at 4:33:06 PM UTC, FANG Colin wrote:
>
> Thank you.
>
>  
>
> I used to use https://github.com/Mike43110/julia.vscode which 
> unfortunately doesn't provide the command for mark selection as comments. 
>
>

RE: [julia-users] Re: VS code extension

2016-10-28 Thread David Anthoff 
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) and it would 
be good to sort out what is the right strategy for the extension, and how this 
new code fits in there.

 

From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On 
Behalf Of Zac
Sent: Friday, October 28, 2016 8:40 AM
To: julia-users 
Subject: [julia-users] Re: VS code extension

 

Ok then, https://github.com/ZacLN/julia-vscode . I'll look into trying to make 
a pull request on the main repo. 

 

 

 

 

On Friday, October 28, 2016 at 3:29:17 PM UTC, Tony Kelman wrote:

The repo's MIT licensed, so unless this person changed the license of their 
additions, yes. Best to preserve git authorship attribution if you can. Pull 
requests to the JuliaEditorSupport repository are encouraged, I imagine.


On Friday, October 28, 2016 at 3:31:56 AM UTC-7, Zac wrote:

Hi, I'm using a fork of this that implements completions, function parameter 
hints, documentation hovers, linting and definitions. I pulled it from another 
fork that has subsequently disappeared (github.com/novatena 
 ). This 

 

Given that someone else did most of the work is it ok to share it here? 


On Tuesday, July 5, 2016 at 4:33:06 PM UTC, FANG Colin wrote:

Thank you.

 

I used to use https://github.com/Mike43110/julia.vscode which unfortunately 
doesn't provide the command for mark selection as comments.

RE: [julia-users] Re: VS code extension

2016-06-23 Thread David Anthoff 
I added a gitter room for the VS Code plugin, maybe best to move further 
discussion of the extension there: 
https://gitter.im/JuliaEditorSupport/julia-vscode.

 

I have a prototype  up and running for sending selected or individual lines of 
code from the editor to a REPL via Ctrl+Enter. All very rough at this point and 
for a smooth story it will need some work on Microsoft’s part, but generally it 
is pretty straightforward to get something up and running. 
https://github.com/JuliaEditorSupport/julia-vscode/pull/2

 

Cheers,

David

 

From: julia-users@googlegroups.com [mailto:julia-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.

 

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 mostly feel that it is good to have some bare bones 
support for VS Code. I don’t know whether there is enough man power/interest to 
ever try to get it into a polished thing that supports more of the VS Code 
extension points for languages. While I’ll maintain the extension, I have no 
plans for major development.

 

PRs are welcome, though!

 

Cheers,

David

 

From: julia-users@googlegroups.com <mailto:julia-users@googlegroups.com>  
[mailto:julia-users@googlegroups.com] On Behalf Of Tony Kelman
Sent: Wednesday, June 22, 2016 8:11 PM
To: julia-users <julia-users@googlegroups.com 
<mailto:julia-users@googlegroups.com> >
Subject: [julia-users] Re: VS code extension

 

VS Code feels much snappier and higher performance to me than Atom, especially 
on larger files. If you're on Windows especially, the installation and updating 
experience is just a lot more polished and customizable. The downside is 
there's been a lot less work on Julia-specific addin integration so far.


On Wednesday, June 22, 2016 at 10:36:58 PM UTC-4, Gabriel Gellner wrote:

Are there benefits to using this over atom? Why are people moving over? Pros, 
Cons?

On Tuesday, June 21, 2016 at 3:26:52 PM UTC-7, David Anthoff wrote:

Hi all,

 

I’ve created a new github repo for a VS code extension 
https://github.com/davidanthoff/julia-vscode and it is published here 
https://marketplace.visualstudio.com/items?itemName=julialang.language-julia. 
Be5invis will delete the old julia extension from the marketplace because he is 
no longer maintaining it. At this point my extension has zero additional 
features over his old one, except that there is a public github repo where in 
theory people could contribute.

 

Two questions:

1) could we move the github repo under some official julia organization? I know 
most other editor plugins are under julialang, but I also remember talk about 
creating something like a juliaeditor org or something like that? In any case, 
I would like to move the repo to something more official. I’m happy to maintain 
it for the foreseeable future, so no fear on that front.

2) I used the julia logo. I hope that is ok from a copyright point of view? I 
took it from the repo for the julia homepage, and that whole repo seemed to be 
under an MIT license, but just wanted to be sure.

 

And if anyone wants to add stuff to the extension, PRs are welcome! Especially 
a debug adapter would of course be fantastic.

 

Cheers,

David 

 

--

David Anthoff

University of California, Berkeley

 

http://www.david-anthoff.com

RE: [julia-users] Re: VS code extension

2016-06-23 Thread David Anthoff 
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 mostly feel that it is good to have some bare bones 
support for VS Code. I don’t know whether there is enough man power/interest to 
ever try to get it into a polished thing that supports more of the VS Code 
extension points for languages. While I’ll maintain the extension, I have no 
plans for major development.

 

PRs are welcome, though!

 

Cheers,

David

 

From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On 
Behalf Of Tony Kelman
Sent: Wednesday, June 22, 2016 8:11 PM
To: julia-users 
Subject: [julia-users] Re: VS code extension

 

VS Code feels much snappier and higher performance to me than Atom, especially 
on larger files. If you're on Windows especially, the installation and updating 
experience is just a lot more polished and customizable. The downside is 
there's been a lot less work on Julia-specific addin integration so far.


On Wednesday, June 22, 2016 at 10:36:58 PM UTC-4, Gabriel Gellner wrote:

Are there benefits to using this over atom? Why are people moving over? Pros, 
Cons?

On Tuesday, June 21, 2016 at 3:26:52 PM UTC-7, David Anthoff wrote:

Hi all,

 

I’ve created a new github repo for a VS code extension 
https://github.com/davidanthoff/julia-vscode and it is published here 
https://marketplace.visualstudio.com/items?itemName=julialang.language-julia. 
Be5invis will delete the old julia extension from the marketplace because he is 
no longer maintaining it. At this point my extension has zero additional 
features over his old one, except that there is a public github repo where in 
theory people could contribute.

 

Two questions:

1) could we move the github repo under some official julia organization? I know 
most other editor plugins are under julialang, but I also remember talk about 
creating something like a juliaeditor org or something like that? In any case, 
I would like to move the repo to something more official. I’m happy to maintain 
it for the foreseeable future, so no fear on that front.

2) I used the julia logo. I hope that is ok from a copyright point of view? I 
took it from the repo for the julia homepage, and that whole repo seemed to be 
under an MIT license, but just wanted to be sure.

 

And if anyone wants to add stuff to the extension, PRs are welcome! Especially 
a debug adapter would of course be fantastic.

 

Cheers,

David 

 

--

David Anthoff

University of California, Berkeley

 

http://www.david-anthoff.com

RE: [julia-users] Re: VS code extension

2016-06-22 Thread David Anthoff 
I just used this

 

https://github.com/JuliaLang/Julia.tmbundle/blob/696f630736669251a3cb56cb27741b5b07a4c093/Syntaxes/Julia.tmLanguage

 

file.

 

I don’t know what format atom uses to define grammars…

 

From: julia-users@googlegroups.com [mailto:julia-users@googlegroups.com] On 
Behalf 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 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 
<https://github.com/JuliaLang/Julia.tmbundle/issues/10> .

Thanks.


Best regards,

Eric

On Thursday, June 23, 2016 at 12:18:28 AM UTC+8, David Anthoff wrote:

The VS code extension now lives here  
<https://github.com/JuliaEditorSupport/julia-vscode> 
https://github.com/JuliaEditorSupport/julia-vscode.

 

Cheers,

David

 

From:   julia...@googlegroups.com [mailto:  
julia...@googlegroups.com] On Behalf Of Lyndon White
Sent: Tuesday, June 21, 2016 7:53 PM
To: julia-users <  julia...@googlegroups.com>
Subject: [julia-users] Re: VS code extension

 

I would be happy to transfer https://github.com/oxinabox/julia-vim-completions 
to an Org.
Though probably worth waiting til it is wrapped up into a form people who are 
not me can use.





On Wednesday, 22 June 2016 06:26:52 UTC+8, David Anthoff wrote:

Hi all,

 

I’ve created a new github repo for a VS code extension 
https://github.com/davidanthoff/julia-vscode and it is published here 
https://marketplace.visualstudio.com/items?itemName=julialang.language-julia. 
Be5invis will delete the old julia extension from the marketplace because he is 
no longer maintaining it. At this point my extension has zero additional 
features over his old one, except that there is a public github repo where in 
theory people could contribute.

 

Two questions:

1) could we move the github repo under some official julia organization? I know 
most other editor plugins are under julialang, but I also remember talk about 
creating something like a juliaeditor org or something like that? In any case, 
I would like to move the repo to something more official. I’m happy to maintain 
it for the foreseeable future, so no fear on that front.

2) I used the julia logo. I hope that is ok from a copyright point of view? I 
took it from the repo for the julia homepage, and that whole repo seemed to be 
under an MIT license, but just wanted to be sure.

 

And if anyone wants to add stuff to the extension, PRs are welcome! Especially 
a debug adapter would of course be fantastic.

 

Cheers,

David 

 

--

David Anthoff

University of California, Berkeley

 

http://www.david-anthoff.com

Re: [julia-users] Re: VS code extension

2016-06-22 Thread Eric Forgy 
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 
.

Thanks.

Best regards,
Eric

On Thursday, June 23, 2016 at 12:18:28 AM UTC+8, David Anthoff wrote:
>
> The VS code extension now lives here 
> https://github.com/JuliaEditorSupport/julia-vscode.
>
>  
>
> Cheers,
>
> David
>
>  
>
> *From:* julia...@googlegroups.com  [mailto:
> julia...@googlegroups.com ] *On Behalf Of *Lyndon White
> *Sent:* Tuesday, June 21, 2016 7:53 PM
> *To:* julia-users 
> *Subject:* [julia-users] Re: VS code extension
>
>  
>
> I would be happy to transfer 
> https://github.com/oxinabox/julia-vim-completions to an Org.
> Though probably worth waiting til it is wrapped up into a form people who 
> are not me can use.
>
>
>
>
>
> On Wednesday, 22 June 2016 06:26:52 UTC+8, David Anthoff wrote:
>
> Hi all,
>
>  
>
> I’ve created a new github repo for a VS code extension 
> https://github.com/davidanthoff/julia-vscode and it is published here 
> https://marketplace.visualstudio.com/items?itemName=julialang.language-julia. 
> Be5invis will delete the old julia extension from the marketplace because 
> he is no longer maintaining it. At this point my extension has zero 
> additional features over his old one, except that there is a public github 
> repo where in theory people could contribute.
>
>  
>
> Two questions:
>
> 1) could we move the github repo under some official julia organization? I 
> know most other editor plugins are under julialang, but I also remember 
> talk about creating something like a juliaeditor org or something like 
> that? In any case, I would like to move the repo to something more 
> official. I’m happy to maintain it for the foreseeable future, so no fear 
> on that front.
>
> 2) I used the julia logo. I hope that is ok from a copyright point of 
> view? I took it from the repo for the julia homepage, and that whole repo 
> seemed to be under an MIT license, but just wanted to be sure.
>
>  
>
> And if anyone wants to add stuff to the extension, PRs are welcome! 
> Especially a debug adapter would of course be fantastic.
>
>  
>
> Cheers,
>
> David 
>
>  
>
> --
>
> David Anthoff
>
> University of California, Berkeley
>
>  
>
> http://www.david-anthoff.com
>
>  
>
>

RE: [julia-users] Re: VS code extension

2016-06-22 Thread David Anthoff 
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 
Subject: [julia-users] Re: VS code extension

 

I would be happy to transfer https://github.com/oxinabox/julia-vim-completions 
to an Org.
Though probably worth waiting til it is wrapped up into a form people who are 
not me can use.





On Wednesday, 22 June 2016 06:26:52 UTC+8, David Anthoff wrote:

Hi all,

 

I’ve created a new github repo for a VS code extension 
https://github.com/davidanthoff/julia-vscode and it is published here 
https://marketplace.visualstudio.com/items?itemName=julialang.language-julia. 
Be5invis will delete the old julia extension from the marketplace because he is 
no longer maintaining it. At this point my extension has zero additional 
features over his old one, except that there is a public github repo where in 
theory people could contribute.

 

Two questions:

1) could we move the github repo under some official julia organization? I know 
most other editor plugins are under julialang, but I also remember talk about 
creating something like a juliaeditor org or something like that? In any case, 
I would like to move the repo to something more official. I’m happy to maintain 
it for the foreseeable future, so no fear on that front.

2) I used the julia logo. I hope that is ok from a copyright point of view? I 
took it from the repo for the julia homepage, and that whole repo seemed to be 
under an MIT license, but just wanted to be sure.

 

And if anyone wants to add stuff to the extension, PRs are welcome! Especially 
a debug adapter would of course be fantastic.

 

Cheers,

David 

 

--

David Anthoff

University of California, Berkeley

 

http://www.david-anthoff.com