Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2021-12-08

Channels

#vim
<
2021-12-08
>
reborg09:12:56

I also have a sudden jumping to symbol source problem, but totally unrelated environment to the above. I'm using neovim, vim-fireplace. I use [+CTRL-D all the time to jump to the source of a function in core or elsewhere. It now works properly for project files only, but it shows an empty page if I try to jump to a function in clojure/core.clj for example. I can see the correct path in the status bar (for example, zipfile:/home/ren/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar::clojure/core.clj ) but the screen is empty. Any idea where I should look to bring this back to working?

timo10:12:50

Did you deactivate the zip plugin in neovim?

reborg10:12:52

Don't think so? So if I for example do: :e /home/ren/.m2/repository/org/clojure/clojure/1.10.1/clojure-1.10.1.jar I can see inside the jar, navigate to core.clj and open it.

dominicm11:12:24

Hmm, I thought I'd broken something myself.

dominicm11:12:28

I wonder if this is something in neovim 0.6.0?

dominicm11:12:36

lemme just double check I can repro

dominicm11:12:33

Yep, I see the same thing

dominicm11:12:56

I'm pretty sure that fireplace was patching the zip stuff to make it work..

dominicm11:12:25

Only difference I can spot is that when I do it via the zip plugin I end up at zipfile:/// rather than zipfile:/.

reborg11:12:26

I see, yes that could be. It also does the same with normal Vim (just FYI)

dominicm11:12:49

That's good to know

dominicm11:12:45

yep, looks like they changed this!

reborg11:12:56

Ah thanks for pinpointing. So am I on a old version? It seems they actually fixed the issue by adding the slashes

dominicm11:12:56

Fireplace is opening the "wrong" path, but it used to be the right path

dominicm11:12:11

You'll need to open an issue/pr at fireplace.

dominicm11:12:12

I think @UKFUXQMU3 likes to support old versions of vim so the change will likely need to check g:loaded_zip to determine if it's <32 and use the old way if so...

reborg11:12:47

Happy to open, but you also seem to be better positioned to explain the problem :)

dominicm11:12:37

I'll sort it 🙂

reborg11:12:46

many thanks!

tpope11:12:19

backwards compatibility aside, i'm happy to hear they fixed it to look like a proper url

dominicm11:12:34

Yeah, I remember poking around the source and being frustrated by that.

dominicm11:12:34

this might be fixed now, which would be cool

dominicm11:12:01

ah, it won't, because the existence check presumably still doesn't work.

dominicm11:12:05

but, we're a bit closer.

Jan K12:12:04

I also encountered this problem (with regular vim, not neovim). I downgraded my vim to fix it. The problem also manifests if you simply do vim something.zip and choose a file to open (any non-empty file in the zip), which works fine in older vim.

dharrigan15:12:44

This bug is a bummer 😞

tpope16:12:43

your face is a bummer

😂 1