Closed UnkindPartition closed 1 year ago
I concur. Same exact issue after a recent system update.
My system info: Debian Linux NVIM v0.6.1
## Ruby provider (optional)
- INFO: Ruby: ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux]
- INFO: Host: /usr/local/bin/neovim-ruby-host
- OK: Latest "neovim" gem is installed:
Have you tried rebuilding Command-T? Something like:
cd ~/.config/nvim/pack/bundle/opt/command-t/ruby/command-t/ext/command-t
make clean
ruby extconf.rb
make
(exact path to the ruby/command-t/ext/command-t
is going to be system-dependent)
Thanks Greg, yes I tried that too after I updated the plugin but I'm still having the problem.
Given the big rewrite for v6.0.x, I'm closing all older issues as there is unlikely to be anything significant happening on the 5-x-devel
branch from here on[^patches]. Feedback issue for 6.0.x is here:
[^patches]: Patches and PRs would be welcome, but my personal efforts are going to be directed towards main
.
Unfortunately I couldn't' get this to work so I gave up and switched to another similar extension (fzf) last week. I hope the new version of command-t addresses this issue though.
@mkayyash I stumbled upon the exact same issue and this comment provides a very simple working solution, which is very fortunate since I find it very hard to live without this lovely plugin! (in a nutshell: for reasons beyond my humble comprehension, your Vim plugin manger needs to delay loading of this plugin to the VimEnter event)
After a recent system update, command-t is no longer usable with neovim; I get the following message:
My command-t version is up to date (6a00a2cabfb5ee3f49ff556ceea56892825c03970) and the C extension is recompiled.
System info:
Arch Linux NVIM v0.6.0