You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 7, 2023. It is now read-only.
* The server needs a minute to spin up, then also some time to parse new Julia environments that this Atom instance
21
-
have not seen before. A pop-up is shown when parsing the environment starts, but not when it ends. After that, you need to
22
-
edit or reopen the files already in editing for linting to start. If the environment had been already parsed, linting new files is immediate.
21
+
have not seen before. A pop-up is shown when parsing a new environment starts (but not when it ends). After parsing finishes, you need to
22
+
edit or reopen those files that are already in the editor for linting to start. If the environment had been already parsed, linting new files is immediate.
23
23
* The edited file has to be saved at least once for linting to start. This is by design of the linter package (https://github.com/steelbrain/linter/issues/1235)
24
24
* The environment for each file is guessed from its path. If this fails, Julia's default environment is assumed.
25
25
* The symbols are rebuilt if the modification time of the Project.toml or the Manifest.toml files change, for example,
26
26
you add, remove or update packages. Linting is not available during this rebuild.
27
-
* It works on Windows, but does not shuts down correctly.
27
+
* It works on Windows, but the Julia server does not shuts down on its own there (yet).
28
28
29
29
## Internals
30
30
31
-
I know nothing of Atom development or js, so the changes are likely messy there, please revise. Atom seems to be
32
-
unable to shut down the server process, so the server exits by polling Atom's PID right now. This does not work on Windows yet.
33
-
34
31
The code generates its private shared environment at the Julia depot in 'environments/linter-julia'. It also places a logfile there.
35
32
36
33
Guessing the environment works by walking upwards in the path and looking for Project.toml. If nothing found, the default
37
34
environment is assumed. The project's root file is then looked for at the canonical X/src/X.jl etc. locations.
38
35
36
+
I know nothing of Atom development or js, so the changes are likely messy there, please revise. Atom seems to be
37
+
unable to shut down the server process, so the server exits by polling Atom's PID right now. This does not work on Windows yet.
38
+
39
39
## Installation
40
40
41
41
- Install the package through Atom's UI. You can also use the `apm` tool in the CLI:
42
42
```bash
43
43
$ apm install takbal/linter-julia
44
44
```
45
45
46
-
- You may need to tell linter-julia where to find the julia executable
46
+
- You may need to tell linter-julia where to find the Julia executable
47
47
(i.e. `/usr/bin/julia` or `C:\Julia-1.5.3\bin\julia.exe`). The default assumes 'julia' just works.
0 commit comments