Closed alloc33 closed 1 year ago
What version of neovim are you using?
On which platform are you?
What does :checkhealth
say?
@Saecki I'm having the same issue.
I'm on Neovim nightly v0.10.0-dev-dfa8b58
This is the output of :checkhealth
:
can you share the problematic file?
[package]
name = "foo"
version = "0.1.0"
edition = "2021"
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies]
rand = {version = "*"}
This is the config that I'm using:
require('crates').setup({
popup = {
keys = {
toggle_feature = { '<space>lf' },
},
},
})
I can't reproduce this bug, even on nightly.
@Saecki Here's the full minimal config that I'm using:
You use it by running nvim -u path/to/init.lua
When I do :map <space>lf
there doesn't seem to be a <space>lf
mapping even created.
Oh, I see. When initially lazy loading the plugin on BufRead
the first update doesn't get triggered. Reopening the file using :e
will fix that. That bug was fixed some time ago, so if you don't use the stable v0.3.0
tag everything should word fine. It's probably time to make a new release anyway.
@Saecki I tried removing lazy loading and v0.3.0
tag, as well as updating, but I'm still having the same issue. This is what my minimal config looks like now:
I still don't see any key mapping when I do :map <space>lf
(I've tried changing to other key mappings as well).
The key mappings defined there only work inside the popup. To do anything from inside the Cargo.toml
file you'll have to add your own key mappings.
@Saecki Oh that's my bad for not reading the full documentation! Thanks for the help!
It shows me the version of the crates beside, but when I try to run some commands when I stay on the same line with crate name - it doesn't do anything at all. For example I try to call
lua require('crates').open_crates_io()
on any crate and it doesn't work. The only command which works -lua require('crates').show_versions_popup()