I'm proud to announce that I've released lint+, a linter for lite. It actually started out as a Nim-only linter, but I decided to distill it to something a bit more generic with a separate Nim support plugin.
You can grab lint+ from its GitHub repository: https://github.com/liquid600pgm/lintplus
I consider it to be a bit better than the VS Code extension and ALE for Vim, since it uses nim c rather than nim check, eliminating most weird errors that happen when not compiling Nim normally. One thing I would still like to add is project support, where the Nim plugin would be capable of detecting the main file in the project (or just letting the user specify it), thus eliminating any errors that may arise from using include.
For those of you curious, I'm planning on making lite fully usable as a Nim IDE, including syntax (done), error reporting (done), and autocomplete (soon™). It's quite a nice text editor, though it can be hard to get used to if you're used to a more "full-fledged" solution like VS Code (for instance, lite can only have one folder open at a given time).
I'm afraid setting --errorMax:1 will make for a bad user experience, you usually want to see as many errors as possible – not have to play whack-a-mole with the compiler.
Er, but nim c defaults to --errorMax:1 too.
Here is what you said:
I consider it to be a bit better than the VS Code extension and ALE for Vim, since it uses nim c rather than nim check, eliminating most weird errors that happen when not compiling Nim normally.
Now it happens that I know exactly how nim c and nim check work and the most important difference in error checking/reporting is the default setting of --errorMax. If nim c works better for you than nim check then that must be the reason. Hence my suggestion to use nim check --errorMax:1 for the editor.
hello, Actually very light LITE, roughly it takes half a day to put it in the hand.
I would have liked to do like the vs code (maybe I didn't understand) explanation I am using strformat and I would have liked that fmt came out in shine like the functions on the other hand the highlighting of {.. (....
`` $ fmt" file: {getCurrentDir ()} / {element.arg} .html " ``
in a thong did not take into account ...
it's true I nitpick BUT your THING is very light and sporty (fast and does a good job)
I'm not sure I understood correctly, but you're mentioning the lack of highlighting in fmt, right?
Well unfortunately, due to the limitations of lite's highlighter, that's not really possible without incorporating a custom highlighting engine to the plugin. Personally I don't use fmt that much, and after all it's just a macro – why treat it specially? It takes a string, it outputs some other AST. How it interprets the string is none of the lexer's (or highlighter's) business.