psi-jack/ultimate-vim
1
0
Fork 0
mirror of synced 2024-11-04 16:38:59 -05:00
Code Issues Releases Wiki Activity

Update gitignore

Browse source
This commit is contained in:
Kurtis Moxley 2022-05-19 20:38:40 +08:00
parent bed26662fd
commit 0cde47b0dd
3 changed files with 1 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
.gitignore vendored
View file

@ -8,3 +8,4 @@ my_plugins/
my_configs.vim
tags
.DS_Store
.metals/

24
.metals/metals.log
View file

@ -1,24 +0,0 @@
2022.05.18 21:58:02 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/.metals/lsp.trace.json or /home/kurtis/.cache/metals/lsp.trace.json
2022.05.18 21:58:03 INFO logging to file /home/kurtis/.vim_runtime/.metals/metals.log
2022.05.18 21:58:03 INFO Started: Metals version 0.11.2 in workspace '/home/kurtis/.vim_runtime' for client coc.nvim 0.0.80.
2022.05.18 21:58:03 WARN Can't instantiate JavaInteractiveSemanticdb (version: None, jdkHome: /usr/lib64/jvm/java, javac exists: true)
2022.05.18 21:58:06 INFO time: initialize in 2.71s
2022.05.18 21:58:06 WARN Build server is not auto-connectable.
2022.05.18 21:58:06 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.18 23:59:50 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/.metals/lsp.trace.json or /home/kurtis/.cache/metals/lsp.trace.json
2022.05.18 23:59:51 INFO logging to file /home/kurtis/.vim_runtime/.metals/metals.log
2022.05.18 23:59:51 INFO Started: Metals version 0.11.2 in workspace '/home/kurtis/.vim_runtime' for client coc.nvim 0.0.80.
2022.05.18 23:59:51 WARN Can't instantiate JavaInteractiveSemanticdb (version: None, jdkHome: /usr/lib64/jvm/java, javac exists: true)
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. 

BIN
.metals/metals.mv.db
View file

Binary file not shown.