Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

incorrect detection of ruby neovim in checkhealth #28642

Closed
RageCPP opened this issue May 5, 2024 · 1 comment · Fixed by #28804
Closed

incorrect detection of ruby neovim in checkhealth #28642

RageCPP opened this issue May 5, 2024 · 1 comment · Fixed by #28804
Labels
bug issues reporting wrong behavior platform:wsl provider
Milestone

Comments

@RageCPP
Copy link

RageCPP commented May 5, 2024

Problem

image
image
image
I alse try set g.ruby_host_prog = "/home/rage/.rbenv/versions/3.3.1/lib/ruby/gems/3.3.0/gems/neovim-0.9.1/exe/neovim-ruby-host" but still not work

Steps to reproduce

:checkhealth

Expected behavior

like node

...
Node.js provider (optional) ~
- Node.js: v20.12.2
  
- Nvim node.js host: /home/rage/.local/share/pnpm/global/5/node_modules/neovim/bin/cli.js
- OK Latest "neovim" npm/yarn/pnpm package is installed: 5.1.0
...

Neovim version (nvim -v)

v0.10.0-dev-efb44e0

Vim (not Nvim) behaves the same?

VIM - Vi IMproved 9.1 (2024 Jan 02)

Operating system/version

wsl - open suse leap 15.5

Terminal name/version

windows terminal

$TERM environment variable

screen-256color

Installation

repo

@RageCPP RageCPP added the bug issues reporting wrong behavior label May 5, 2024
@justinmk justinmk added this to the backlog milestone May 6, 2024
@justinmk
Copy link
Member

justinmk commented May 6, 2024

Just for reference: after #27949 , neovim-ruby-host and cli.js will be obsolete and unnecessary. Instead, g:ruby_host_prog and g:node_host_prog will point to ruby and node interpreters directly (as g:python3_host_prog already does).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug issues reporting wrong behavior platform:wsl provider
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants