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

Dedicated VSCode Extension #447

Open
saem opened this issue Oct 9, 2022 · 3 comments
Open

Dedicated VSCode Extension #447

saem opened this issue Oct 9, 2022 · 3 comments
Labels
good first issue Easy-to-start-with issue with no in-depth knowledge or complex implementation required.

Comments

@saem
Copy link
Collaborator

saem commented Oct 9, 2022

Many people use VSCode or the like. At present most can make do with the Saem's Nim extension for Nimskull. Things are starting to diverge, however.

Roughly what needs to happen:

  • start a new repo for the new extension (we can move it to the Nimskull org later)
  • do some renaming/clean-up
  • get it on various marketplaces
  • link it into various docs
  • support cyo and whatever other file extensions/tools are required

Then the it can evolve over time.

@saem saem added the good first issue Easy-to-start-with issue with no in-depth knowledge or complex implementation required. label Oct 9, 2022
@saem saem added this to the project-rename milestone Oct 9, 2022
@haxscramper haxscramper removed this from the project-rename milestone Nov 20, 2022
@omentic
Copy link
Contributor

omentic commented May 9, 2023

For just about every other editor: #448 and a tree-sitter grammar should be enough. aMOPel and alaviss did heavy lifting on grammars for Nim which should be drop-in / easily adaptable.

@saem
Copy link
Collaborator Author

saem commented May 9, 2023

Treesitter grammar is nascent and incomplete, not to mention incredibly memory intensive. I'm not familiar with the other person or work.

@omentic
Copy link
Contributor

omentic commented May 9, 2023

alaviss's version is a complete, more idiomatic grammar: but they're running into some issues with the size of the generated parser (and presumably memory issues from there).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Easy-to-start-with issue with no in-depth knowledge or complex implementation required.
Projects
None yet
Development

No branches or pull requests

3 participants