Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure that all editors play well with Perl 6 #10

Closed
AlexDaniel opened this issue Mar 25, 2018 · 17 comments
Closed

Make sure that all editors play well with Perl 6 #10

AlexDaniel opened this issue Mar 25, 2018 · 17 comments

Comments

@AlexDaniel
Copy link
Member

AlexDaniel commented Mar 25, 2018

⚠ Ticket moved to Raku/user-experience#19

@cfa
Copy link

cfa commented Mar 25, 2018

@AlexDaniel updated NeoVim to point at the Vim (rather than Emacs) plugin.

@AlexDaniel
Copy link
Member Author

@cfa oh. I think it should be pointing to https://github.com/neovim/neovim/blob/master/runtime/ftplugin/perl6.vim instead?

@cfa
Copy link

cfa commented Mar 25, 2018

@AlexDaniel looks like that's an older version (bundled with vim-perl).

Perhaps both links can be provided—(i) builtin support, (ii) the more up to date plugin?

@zoffixznet
Copy link
Contributor

Sublime text | 🤷 unknown

It has a really awful and unusable Perl 6 highligher, so I'd say it's unsupported. I forget where I installed it from, but lack of support in sublime is the only reason I'm using Atom for P6.

@MasterDuke17
Copy link

I'm pretty sure vim supports Perl 6 by default now.

@Tyil
Copy link
Member

Tyil commented Mar 26, 2018

@MasterDuke17 Perl 6 has decent support by default in vim, but the vim-perl6 plugin enhances it.

@AlexDaniel
Copy link
Member Author

Yeah, I think I fixed that.

@nxadm
Copy link

nxadm commented Mar 26, 2018

Maybe this could be turned into a Wiki page?

@cfa
Copy link

cfa commented Mar 26, 2018

@nxadm good idea.

We could also potentially snapshot it periodically at https://github.com/perl6/doc so that it's more discoverable for users. Thoughts?

@AlexDaniel
Copy link
Member Author

AlexDaniel commented Mar 26, 2018

Well, anyone in perl6 github org (≈300 people) should be able to edit the comment, so functionally any comment is like a shitty wiki page (which is often good enough). And that's not the first time we do that. In fact, we probably get more edits here than on the whole rakudo wiki. Also, here you have an option to just write a comment instead of editing.

so that it's more discoverable for users. Thoughts?

This ticket was meant to be a marketing issue… but yes, I see it outgrowing itself a bit.

We already list editor plugins on https://perl6.org/whatever/, maybe we should just extract the useful parts from that table.

@zoffixznet
Copy link
Contributor

edit the comment, so functionally any comment is like a shitty wiki page

But that leaves the non-issue Issue open. In the wrong repo too. This stuff has little to do with marketing, but is perfect for our user-experience repo.


FWIW, here's a user asking for nano support, if anyone has any advice for them: https://www.reddit.com/r/perl6/comments/881svu/nano_syntax_highlighting_for_perl6/

@AlexDaniel
Copy link
Member Author

@zoffixznet you're right! I totally forgot that we had a user-experience repo.

@zaucker
Copy link

zaucker commented Apr 3, 2018

Comma should be added to the list (perhaps not before the beta is started in May 2018).

@AlexDaniel
Copy link
Member Author

Sure, once it's out.

@nxadm
Copy link

nxadm commented Apr 3, 2018

A new column may be needed collecting the license information. Something line FOSS/Commercial with Free Usage/Paid License.

C.

@AlexDaniel
Copy link
Member Author

OK, added it right away as a plugin for IntelliJ IDEA (I hope that's right). Don't know what to do with Comma as standalone IDE, because this ticket has a different purpose. Maybe we can list it on https://perl6.org/whatever/ once it is out.

@AlexDaniel
Copy link
Member Author

Thanks everyone for your comments! This ticked was moved to Raku/user-experience#19.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants