This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-20
Channels
- # announcements (3)
- # babashka (7)
- # beginners (36)
- # calva (71)
- # cider (25)
- # clj-commons (5)
- # cljdoc (19)
- # cljs-dev (5)
- # clojure (223)
- # clojure-austin (2)
- # clojure-bay-area (1)
- # clojure-europe (31)
- # clojure-france (6)
- # clojure-nl (2)
- # clojure-norway (19)
- # clojure-spec (13)
- # clojure-uk (7)
- # clojurescript (127)
- # core-logic (2)
- # cursive (21)
- # datalevin (53)
- # datomic (9)
- # emacs (37)
- # events (1)
- # graphql (8)
- # jobs (12)
- # lsp (8)
- # off-topic (92)
- # pathom (49)
- # pedestal (1)
- # polylith (3)
- # re-frame (25)
- # releases (2)
- # sci (11)
- # shadow-cljs (13)
- # vim (10)
Dear vimmers, I noticed that when I have a poor connection or network trouble of some sort, I'm unable to open some type of files (for example, clj
but also Dockerfile) as Vim hangs while opening the buffer. Sometimes I can get around it by repeatedly ctrl+C on it until it stops doing whatever is connecting to. Any hints about debugging what is trying to connect to what and why?
Try -X
. Vim will try to connect to an X server on startup. A slow connection can make that noticeable. That flag will turn off that feature, at the cost of some of the X integration not working.
Local files. I'm able to replicate if I open up a Clojure project for example, but only the first time I open it. The second time it's instant. I think I've seen it happening with a Dockerfile as well as ruby files. But at the moment, I'm concentrating on Clojure projects. So as suggested by @U09LZR36F I've used the :profile
function and then asked vim to open a project.clj
file. This is the only thing that seems to have consumed 90 seconds:
FUNCTION <SNR>42_scrape_path()
Defined: ~/.vim/bundle/vim-salve/plugin/salve.vim:166
Called 1 time
Total time: 97.017427
Self time: 0.022392
count total (s) self (s)
1 0.000002 let cd = exists('*haslocaldir') && haslocaldir() ? 'lcd' : 'cd'
1 0.000002 let cwd = getcwd()
1 0.000000 try
1 0.000008 execute cd fnameescape(b:salve.root)
1 97.017363 0.022328 let path = matchstr(system(b:salve.classpath_cmd), "[^\n]*\\ze\n*$")
1 0.000006 if v:shell_error
1 0.000004 return []
endif
return map(s:split(path), 's:absolute(v:val, b:salve.root)')
1 0.000001 finally
1 0.000029 execute cd fnameescape(cwd)
1 0.000002 endtry
Which seems to point at https://github.com/tpope/vim-salve pluginI assume your problem is having a snapshot dependency, and it's being checked against maven for the latest version.
that sounds plausible. I'm not even sure why I'm using salve, will investigate. Hopefully it is the only problem and I should assume other slowness was because I had a project.clj in the folder