-
Notifications
You must be signed in to change notification settings - Fork 21
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
Linter errors #139
Comments
Oh, it's okay. Thank you for the answer :) |
I filed #140 to track the LSP implementation. I'd like to get something working for it for 0.7, but I haven't been able to find much information out there on how you'd make a "derived" LSP language; all I really need is a way to say "this file is in Python syntax with these extra builtin symbols", but that seems to be nontrivial (or at least no one else has tried to do this, so there's no documentation on how to do it). |
Maybe forking an existing python LSP, and adding the bfg stuff to it? |
Yeah, that's about what I'm thinking. Maybe there are even some hooks in one or another Python LSP implementation that I could use... |
Wouldn't it have been easier to just have bfg9000 be a ordinary python module, that we could just import in the build script and run it with python? What are the advantages of doing it like this? |
The main advantage is that the .bfg script evaluation is only one phase of all the work necessary to generate the Makefiles for an actual build. While it's easy enough to do stuff before the .bfg script when it's just a module, it's not easy to do stuff after it. |
Is there a way to make the linter happy by importing a dummy package or something when opening
.bfg
files in an ide?The text was updated successfully, but these errors were encountered: