16
16
- [[#elm-format][elm-format]]
17
17
- [[#elm-test][elm-test]]
18
18
- [[#configuration][Configuration]]
19
- - [[#choosing-a-backend][Choosing a backend]]
20
- - [[#company-elm][Company-elm]]
21
- - [[#elm-oracle][elm-oracle]]
19
+ - [[#backend][Backend]]
22
20
- [[#lsp][LSP]]
21
+ - [[#none][None]]
23
22
- [[#basic-usage-tips][Basic usage tips]]
24
23
- [[#compilation][Compilation]]
25
24
- [[#reactor][Reactor]]
35
34
- [[#elm-test-runner][elm-test-runner]]
36
35
- [[#elm-package][elm-package]]
37
36
- [[#package-list-buffer][package list buffer]]
38
- - [[#elm-oracle-1][elm-oracle]]
39
37
- [[#elm-format-1][elm-format]]
40
38
- [[#refactoring][Refactoring]]
41
39
@@ -126,37 +124,10 @@ To install =elm-test= run below command:
126
124
All layer configurations can be done by setting layer variables in your dotfile.
127
125
No custom user config lines are necessary
128
126
129
- ** Choosing a backend
130
- This layer provides two alternative backends to choose from.
131
-
132
- *** Company-elm
133
- This is the default choice if nothing is set and no lsp layer
134
- is loaded in your dotfile. This mode only provides very
135
- limited IDE capabilities. Used best if only small programs
136
- are edited. To set explicitly set the following in your
137
- dotfile:
138
-
139
- #+BEGIN_SRC emacs-lisp
140
- (elm :variables elm-backend 'company-elm)
141
- #+END_SRC
142
-
143
- **** elm-oracle
144
- =elm-oracle= can be used to show type signatures and docs for tokens under the
145
- cursor and provide support for auto-completion, but it is not part of the
146
- standard elm-platform.
147
-
148
- Both the "company" and "auto-complete" backends are supported, but this layer
149
- is configured with company.
150
-
151
- To install =elm-oracle=, install =node.js= and =npm=, then
152
- run this command:
153
-
154
- #+BEGIN_SRC sh
155
- npm install -g elm-oracle
156
- #+END_SRC
127
+ ** Backend
157
128
158
129
*** LSP
159
- For proper IDE support this backend should be used. It is
130
+ For proper IDE support the =lsp= backend should be used. It is
160
131
based on an external server which will be started automatically
161
132
by emacs, once an elm file is opened. The key bindings are
162
133
the same for all lsp modes so if you are already familiar with
@@ -182,6 +153,14 @@ LSP layer. Also it is advisable to have a look
182
153
at the autocomplete layer for an optimal
183
154
intellisense config for LSP.
184
155
156
+ *** None
157
+ If the =lsp= layer is loaded in your dotfile and nothing is set for =elm-backend=, =lsp= will be
158
+ automatically selected. To explicitly disable the =lsp= backend set the following in your dotfile:
159
+ #+BEGIN_SRC emacs-lisp
160
+ (elm :variables elm-backend nil)
161
+ #+END_SRC
162
+
163
+
185
164
* Basic usage tips
186
165
** Compilation
187
166
To control the name of the compiled JavaScript file, use ~SPC m c B~ instead of
@@ -304,13 +283,6 @@ using a =dir-locals.el= file.
304
283
| ~x~ | elm-package-install |
305
284
| ~q~ | quit-window |
306
285
307
- ** elm-oracle
308
-
309
- | Key binding | Description |
310
- |-------------+--------------------------|
311
- | ~SPC m h h~ | elm-oracle-doc-at-point |
312
- | ~SPC m h t~ | elm-oracle-type-at-point |
313
-
314
286
** elm-format
315
287
316
288
| Key binding | Description |
0 commit comments