Add some plugins.
This commit is contained in:
parent
66b6ea585e
commit
8c6e932470
6 changed files with 16 additions and 0 deletions
|
@ -12,3 +12,13 @@
|
||||||
2022.05.18 23:59:53 INFO time: initialize in 2.4s[0m
|
2022.05.18 23:59:53 INFO time: initialize in 2.4s[0m
|
||||||
2022.05.18 23:59:54 WARN Build server is not auto-connectable.[0m
|
2022.05.18 23:59:54 WARN Build server is not auto-connectable.[0m
|
||||||
2022.05.18 23:59:54 WARN no build tool detected in workspace '/home/kurtis/.vim_runtime'. The most common cause for this problem is that the editor was opened in the wrong working directory, for example if you use sbt then the workspace directory should contain build.sbt. [0m
|
2022.05.18 23:59:54 WARN no build tool detected in workspace '/home/kurtis/.vim_runtime'. The most common cause for this problem is that the editor was opened in the wrong working directory, for example if you use sbt then the workspace directory should contain build.sbt. [0m
|
||||||
|
2022.05.19 01:08:18 INFO Started: Metals version 0.11.2 in workspace '/home/kurtis/.vim_runtime' for client coc.nvim 0.0.80.[0m
|
||||||
|
2022.05.19 01:08:18 WARN Can't instantiate JavaInteractiveSemanticdb (version: None, jdkHome: /usr/lib64/jvm/java, javac exists: true)[0m
|
||||||
|
2022.05.19 01:08:20 INFO time: initialize in 2.53s[0m
|
||||||
|
2022.05.19 01:08:21 WARN Build server is not auto-connectable.[0m
|
||||||
|
2022.05.19 01:08:21 WARN no build tool detected in workspace '/home/kurtis/.vim_runtime'. The most common cause for this problem is that the editor was opened in the wrong working directory, for example if you use sbt then the workspace directory should contain build.sbt. [0m
|
||||||
|
2022.05.19 01:09:13 INFO Started: Metals version 0.11.2 in workspace '/home/kurtis/.vim_runtime' for client coc.nvim 0.0.80.[0m
|
||||||
|
2022.05.19 01:09:13 WARN Can't instantiate JavaInteractiveSemanticdb (version: None, jdkHome: /usr/lib64/jvm/java, javac exists: true)[0m
|
||||||
|
2022.05.19 01:09:15 INFO time: initialize in 2.46s[0m
|
||||||
|
2022.05.19 01:09:16 WARN Build server is not auto-connectable.[0m
|
||||||
|
2022.05.19 01:09:16 WARN no build tool detected in workspace '/home/kurtis/.vim_runtime'. The most common cause for this problem is that the editor was opened in the wrong working directory, for example if you use sbt then the workspace directory should contain build.sbt. [0m
|
||||||
|
|
Binary file not shown.
2
autoload/.metals/metals.log
Normal file
2
autoload/.metals/metals.log
Normal file
|
@ -0,0 +1,2 @@
|
||||||
|
2022.05.19 01:08:17 INFO tracing is disabled for protocol LSP, to enable tracing of incoming and outgoing JSON messages create an empty file at /home/kurtis/.vim_runtime/autoload/.metals/lsp.trace.json or /home/kurtis/.cache/metals/lsp.trace.json[0m
|
||||||
|
2022.05.19 01:08:18 INFO logging to file /home/kurtis/.vim_runtime/.metals/metals.log[0m
|
1
sources_non_forked/coc.nvim
Submodule
1
sources_non_forked/coc.nvim
Submodule
|
@ -0,0 +1 @@
|
||||||
|
Subproject commit 56f4bdf5f00c0ac4ebdf3a3511dfda80c273e79c
|
1
sources_non_forked/vim-elixir
Submodule
1
sources_non_forked/vim-elixir
Submodule
|
@ -0,0 +1 @@
|
||||||
|
Subproject commit edf880c41ec1768faafc480433ae72ceffaf4362
|
2
vimrcs/.metals/metals.log
Normal file
2
vimrcs/.metals/metals.log
Normal file
|
@ -0,0 +1,2 @@
|
||||||
|
2022.05.19 01:09:12 INFO tracing is disabled for protocol LSP, to enable tracing of incoming and outgoing JSON messages create an empty file at /home/kurtis/.vim_runtime/vimrcs/.metals/lsp.trace.json or /home/kurtis/.cache/metals/lsp.trace.json[0m
|
||||||
|
2022.05.19 01:09:13 INFO logging to file /home/kurtis/.vim_runtime/.metals/metals.log[0m
|
Loading…
Reference in a new issue