-
Notifications
You must be signed in to change notification settings - Fork 16
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
Editor modes for Raku #37
Comments
This question feels like a call for contributors. I'm not sure this issue is a good fit for the problem-solving repo. Is there a question that needs concensus to be reached? |
There's also this ticket: Raku/user-experience#19 Not entirely sure if the existence of user-experience repo is justified, maybe we should instead have a label here. On the other hand, the current 22 tickets are not very |
It is lack of contributors, not an issue that can be resolved as a single-shot action. |
@Altai-man Personally I dislike the idea of saying that some issue exists simply because of the lack of contributors. There's always something that can be improved, and sometimes that can attract more people. Maybe we can provide some guidelines, or describe common pitfalls, or list some tips and tricks, or maybe we can create a test suite… For example, the issue of unicode quotes comes to mind: hinrik/perl6-mode#12 vim-perl/vim-perl#223. Then there's also a thing about replacing ascii ops with unicode ops: Raku/atom-language#72 vim-perl/vim-perl6#8 Raku/raku-mode#14. Notice how the same ticket needs to be submitted for every project separately, it is painful. |
I have a feeling that language server is exactly what was meant to solve such issues. So Raku/user-experience#38 is highly related. We may want to clarify the status of started implementations and suggest some actions regarding what to do next based on it. |
I'm afraid the state of editor modes for Perl 6 is not very good.
So the situation is that we have a mode (Atom) that is community (not) maintained, and 3 others that are author-maintained. Most of them with varying degrees of obsolescence and bitrot. Shouldn't we do something about this?
The text was updated successfully, but these errors were encountered: