This is an Atom package for the Nim language that integrates with the Nim compiler and Nimsuggest.
I forked it from Russ Power's repository. The last observed activity on that repository seems to be 2 years ago and the package had stopped working with recent versions of Atom.
I can barely write Coffeescript code, so the ideal scenario would be for Russ to revive his version. In the meantime, you're stuck with this one!
What I have done so far:
If you wish to submit a pull request, please do so here.
Or you could
And finally, install this package in Atom:
Install, then search for
nimsuggestare not in your PATH, then set the paths for them.
Run Commandfor your OS (at the bottom of the nim package settings, see instructions there).
Shift+ Click or
Shift+ Click -> Jump to definition under cursor
Shift+ B or
Shift+ B -> Build current file or the project it belongs to
F5-> Build and Run current file or the project it belongs to
Open Folder to open the root folder for a Nim project. You should have a main project
.nim file, which is autodetected using the following steps:
.nimblefile in the root folder. If found, use the
srcDirkeys to determine the project file (only the first
binkey will be used if multiple exist).
.nimfile with a corresponding
.nimsfile in the root folder.
If you have a main project, it will speed up autocompletions and jump-to-definition. However, keep in mind that a file must be included or imported either directly or indirectly by the main project file to be error checked.
Now works for all symbols, not just after you press dot. Supports fuzzy matching by using fuzzaldrin. Doc strings are truncated to fit into one line, mouseover to read the whole thing. Can be configured in settings to be on all the time, only after you press dot, or never.
By default, it will check files when you save them. You can also use on-the-fly checking by changing the value in settings. This will slow things down.
Note that if you have a main project file, error checking only occurs for files directly or indirectly imported or included by the main project file. So, if you don't see any errors and they should be there, be sure the file has been imported/included.
If there are a lot of errors/warnings when linting, Atom will slow down a lot. This is because it creates every error/warning box instead of reusing them. There is a pending issue for this in the Atom Linter package.
Shift + Left Click or, on MacOS,
Shift + Left Click to jump to the definition under the mouse cursor.
Shift + B or, on MacOS,
Shift + B to build, which compiles the current file or its project. If there are errors, they will show up normally. These may be different that the linting errors (and probably are more accurate). The status bar in the lower right will show if it was successful or failed.
F5 to build and run the current file or its project. If the build fails, it will not try to run anything. Be sure you set up the
Run Command first!
These commands can work on individual files or projects. If you are editing a file that's not in a project, these commands will just build/run that file. If it is part of a project, these commands will build/run the project root file.
Sometimes the nim compiler or nimsuggest crashes, and you'll see the error notification. It's not a big deal, and nimsuggest will auto-restart. You can view full error dumps in the developer tools console (
Alt + i or
Shift + i or
Shift + i). This can be annoying when doing on-the-fly error checking, so it is disabled by default.
If you want to hack on this package, just:
apm installin repo root
apm linkin repo root
Now you can edit the source directly in your repo clone and it will update any time you restart Atom.
This originally started as a fork of https://github.com/zah/nim.atom/, but it has changed so much that I just Russ Power a new project.
Then, the new project stopped working and I created yet another new one.
Good catch. Let us know what about this package looks wrong to you, and we'll investigate right away.