chore: update readme and changelog

Author: aminya

CHANGELOG.md

@@ -1,3 +1,6 @@
+## 0.9
+* Rewrote for StaticLint.jl (#119)
+
 ## 0.8.2
 * Making it work again on Julia v.1 >
 

README.md

@@ -4,8 +4,6 @@ This linter plugin for [AtomLinter](https://atomlinter.github.io/)
 provides an interface to [StaticLint.jl](https://github.com/julia-vscode/StaticLint.jl).
 It will be used with files that have the `Julia` syntax.
 
-This is a fork that replaces Lint.jl with StaticLint.jl from the Julia VSCode plugin.
-
 ![screenshot](https://raw.githubusercontent.com/takbal/linter-julia/master/Screenshot.gif)
 
 ## Developed on
@@ -15,31 +13,11 @@ This is a fork that replaces Lint.jl with StaticLint.jl from the Julia VSCode pl
 * [linter](https://atom.io/packages/linter)
 * tested on Ubuntu 18.04 and Windows
 
-## Caveats
-
-* The server needs a minute to spin up, then also some time to parse new Julia environments that this Atom instance
-  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
-  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.
-* 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)
-* The environment for each file is guessed from its path. If this fails, Julia's default environment is assumed.
-* The symbols are rebuilt if the modification time of the Project.toml or the Manifest.toml files change, for example,
-you add, remove or update packages. Linting is not available during this rebuild.
-
-## Internals
-
-The code generates its private shared environment at the Julia depot in 'environments/linter-julia'. It also places a logfile there.
-
-Guessing the environment works by walking upwards in the path and looking for Project.toml. If nothing found, the default
-environment is assumed. The project's root file is then looked for at the canonical X/src/X.jl etc. locations.
-
-I know nothing of Atom development or js, so the changes are likely messy there, please revise. Atom seems to be
-unable to shut down the server process, so the server exits by polling Atom's PID right now.
-
 ## Installation
 
 - Install the package through Atom's UI. You can also use the `apm` tool in the CLI:
-```bash
-$ apm install takbal/linter-julia
+```
+apm install linter-julia
 ```
 
 - You may need to tell linter-julia where to find the Julia executable
@@ -59,6 +37,27 @@ $ apm install takbal/linter-julia
 [Issues](https://github.com/AtomLinter/linter-julia/issues) and [pull requests]
 (https://github.com/AtomLinter/linter-julia/pulls) are welcome.
 
+
+## Caveats
+
+* The server needs a minute to spin up, then also some time to parse new Julia environments that this Atom instance
+  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
+  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.
+* 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)
+* The environment for each file is guessed from its path. If this fails, Julia's default environment is assumed.
+* The symbols are rebuilt if the modification time of the Project.toml or the Manifest.toml files change, for example,
+you add, remove or update packages. Linting is not available during this rebuild.
+
+## Internals
+
+The code generates its private shared environment at the Julia depot in 'environments/linter-julia'. It also places a logfile there.
+
+Guessing the environment works by walking upwards in the path and looking for Project.toml. If nothing found, the default
+environment is assumed. The project's root file is then looked for at the canonical X/src/X.jl etc. locations.
+
+I know nothing of Atom development or js, so the changes are likely messy there, please revise. Atom seems to be
+unable to shut down the server process, so the server exits by polling Atom's PID right now.
+
 ## CHANGELOG
 
 [See the full CHANGELOG here.](https://github.com/AtomLinter/linter-julia/blob/master/CHANGELOG.md)