diff --git a/.metals/metals.log b/.metals/metals.log index 6c012801..06a37e3f 100644 --- a/.metals/metals.log +++ b/.metals/metals.log @@ -12,3 +12,13 @@ 2022.05.18 23:59:53 INFO time: initialize in 2.4s 2022.05.18 23:59:54 WARN Build server is not auto-connectable. 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.  +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. +2022.05.19 01:08:18 WARN Can't instantiate JavaInteractiveSemanticdb (version: None, jdkHome: /usr/lib64/jvm/java, javac exists: true) +2022.05.19 01:08:20 INFO time: initialize in 2.53s +2022.05.19 01:08:21 WARN Build server is not auto-connectable. +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.  +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. +2022.05.19 01:09:13 WARN Can't instantiate JavaInteractiveSemanticdb (version: None, jdkHome: /usr/lib64/jvm/java, javac exists: true) +2022.05.19 01:09:15 INFO time: initialize in 2.46s +2022.05.19 01:09:16 WARN Build server is not auto-connectable. +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.  diff --git a/.metals/metals.mv.db b/.metals/metals.mv.db index 657c13c8..c6be8612 100644 Binary files a/.metals/metals.mv.db and b/.metals/metals.mv.db differ diff --git a/autoload/.metals/metals.log b/autoload/.metals/metals.log new file mode 100644 index 00000000..5a87636f --- /dev/null +++ b/autoload/.metals/metals.log @@ -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 +2022.05.19 01:08:18 INFO logging to file /home/kurtis/.vim_runtime/.metals/metals.log diff --git a/sources_non_forked/coc.nvim b/sources_non_forked/coc.nvim new file mode 160000 index 00000000..56f4bdf5 --- /dev/null +++ b/sources_non_forked/coc.nvim @@ -0,0 +1 @@ +Subproject commit 56f4bdf5f00c0ac4ebdf3a3511dfda80c273e79c diff --git a/sources_non_forked/vim-elixir b/sources_non_forked/vim-elixir new file mode 160000 index 00000000..edf880c4 --- /dev/null +++ b/sources_non_forked/vim-elixir @@ -0,0 +1 @@ +Subproject commit edf880c41ec1768faafc480433ae72ceffaf4362 diff --git a/vimrcs/.metals/metals.log b/vimrcs/.metals/metals.log new file mode 100644 index 00000000..bda74116 --- /dev/null +++ b/vimrcs/.metals/metals.log @@ -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 +2022.05.19 01:09:13 INFO logging to file /home/kurtis/.vim_runtime/.metals/metals.log