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

Add support for elisp #48

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Conversation

dyamito
Copy link

@dyamito dyamito commented Sep 14, 2022

I think this is superficially correct. I'm having trouble getting emscripten to run without giving me some obscure error. I wanted to at least open this as a draft PR sooner rather than later though.

@@ -28,6 +28,7 @@
"onLanguage:cpp",
"onLanguage:css",
"onLanguage:csharp",
"onLanguage:elisp",
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"elisp" isn't a known language identifier: https://code.visualstudio.com/docs/languages/identifiers#_known-language-identifiers. I checked the marketplace and there seems to be one extension that labels it as "lisp" https://github.com/mattn/vscode-lisp/blob/master/package.json#L26, so I'm not sure how to proceed here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huh. Looks like there's no formal identifier specified by lsp either 🤔

Fwiw you will need to install a VSCode extension that registers that language id in order for this to actually work. So I'd just pick a VSCode extension that you want to use with elisp, and then use whatever language identifier that extension uses

If there is no such extension, you could either:

  • Create your own simple extension that just registers the language id and associates it with a file extension
  • Add a contributes.languages block to this extension. Slightly mixed feelings about that, as it feels out of scope for this extension, but maybe the simplest path forward

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just wanted to follow up

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

Successfully merging this pull request may close these issues.

2 participants