I'm quite new to neovim and mostly use it for simple c++ development. Love the motions and customizability, however I cannot find what I'm doing wrong when trying to install the clang-formatter using Mason plugin.
Using the visual interface provided by Mason I navigate to the 'formatter' section, position my cursor on the clang-formatter option and press I. It starts something but always fails with the same error message:
Mason Error Message
(I get the same error when installing linters)
So far installing LSP's has been no problem, and I've tried to google what the 'Error: name cmd not found' meant but haven't found anything that seems related.
I've made sure to update both my python3 and python3-pip packages. I believe that the virtual environment package became standard since python3.3 so I haven't installed that separately.
':checkhealth mason' output
My Check Health
If anybody has experienced something similar I'd love to hear how you've solved it!
Did you installed pynvim? It is what makes the bridge between neovim and python stuff I guess, it is optional to have it but could fix your issue. My healthcheck looks like this :
provider: health#provider#check
========================================================================
## Clipboard (optional)
- OK: Clipboard tool found: xclip
## Python 3 provider (optional)
- INFO: `g:python3_host_prog` is not set. Searching for python3 in the environment.
- INFO: Multiple python3 executables found. Set `g:python3_host_prog` to avoid surprises.
- INFO: Executable: /usr/bin/python3
- INFO: Other python executable: /bin/python3
- INFO: Python version: 3.8.10
- INFO: pynvim version: 0.4.3
- OK: Latest pynvim is installed.
To install pynvim (in your shell):
pip3 install pynvim
Related
I'm trying to switch from vscode to neovim. I have coc.nvim configured for pyright but now neovim provides native support for language-server. So I tried to configure python-language-server. I have installed pyls by pip install python-language-server. I went through the documentation for lsp-quickstart. It says that I just need to add neovim/nvim-lspconfig to my plugins and then add lua require('lspconfig').pyls.setup{} to my init.vim. After refreshing I'm getting Error:
E5108: Error executing lua [string ":lua"]:1: attempt to index field 'pyls' (a nil value)
I tried googling it but didn't find any relevant answer. Please help me out if you've configured it.
Hey so it looks like there is a new fork of pyls. I had the same issue and the following worked for me!
See Here:
https://github.com/neovim/nvim-lspconfig/blob/master/CONFIG.md#pylsp
And Here:
https://github.com/python-lsp/python-lsp-server
Try:
pip install 'python-lsp-server[all]'
Then in init.vim change:
lua require('lspconfig').pyls.setup{}
to
lua require('lspconfig').pylsp.setup{}
Note: pyls changes to pylsp
Or you can install all packages with package manager in Linux, for instance:
sudo apt-get install python3-pylsp*
Notice * which will install all pylsp packages.
Environment
Ubuntu 20.04 (official Beta Version)
Visual Studio Code 1.44.2, installed via ubuntu-make (umake):
umake ide visual-studio-code
Node 12 via nvm install 12 && nvm alias default 12 && nvm use default
VS Code Extension: jest
Error
Restarting VS Code fails with:
Finished running all tests. Starting watch mode.
/bin/sh: 1: npm: not found
/bin/sh: 1: npm: not found
Starting Jest in Watch mode failed too many times and has been stopped.
see troubleshooting: https://github.com/jest-community/vscode-jest/blob/master/README.md#troubleshooting
I want to use nvm and want to avoid workaround like adjusting bashrc or similar.
Did not work:
Add to VS Code settings.json (via Ctrl+Shift+P, "Open Settings Json"):
entry "terminal.integrated.shell.linux": "/bin/bash"
Just had an issue running commands over ssh where the node binary from nvm would not be added to the non-login shell's path so couldn't be used. Can't figure out how to add it there and keep it relative to the installed user to be honest.
Removing nvm and installing apt install nodejs through the default repositories is quick workaround if you need.
I'm using Chromebook(asusu c101pa).
How I get VScode without [Community builds of
Visual Studio Code]1?
I've to try community builds of vscode, couldn't run. And, I'd like to use on linux.
I've downloaded deb file of vs code. But couldn't work. Error code sys
An error occurred during installation of your Linux aaplication
So, I do install Linux command(terminal), that too.
myname#penguin:~$ sudo dpkg -i code_1.29.1-1542309157_amd64.deb
dpkg:error processing archive code_1.29.1-1542309157_amd64.deb
(--install):
package architecture (amd64) does not match system (arm64)
rrors were encountered while processing:
code_1.29.1-1542309157_amd64.deb
code_1.29.1-1542309157_amd64.deb is vscode file.
How I fix this problem?
i try to install the hot reload module of jspm using the chokidar-socket-emitter. Installation works like charme, but after that it is not possible to start the watch task as described here: http://jspm.io/0.17-beta-guide/hot-reloading.html
Here is my install log:
XXXXXMacBookPro:dasding xxxxxx$ sudo npm i -g chokidar-socket-emitter
\
fsevents#1.0.12 install /usr/local/lib/node_modules/chokidar-socket-emitter/node_modules/chokidar/node_modules/fsevents
node-pre-gyp install --fallback-to-build
[fsevents] Success: "/usr/local/lib/node_modules/chokidar-socket-emitter/node_modules/chokidar/node_modules/fsevents/lib/binding/Release/node-v14-darwin-x64/fse.node" is installed via remote
chokidar-socket-emitter#0.3.1 /usr/local/lib/node_modules/chokidar-socket-emitter
├── socket.io#1.4.6 (has-binary#0.1.7, debug#2.2.0, socket.io-parser#2.2.6, socket.io-adapter#0.4.0, engine.io#1.6.9, socket.io-client#1.4.6)
└── chokidar#1.5.2 (path-is-absolute#1.0.0, inherits#2.0.1, glob-parent#2.0.0, async-each#1.0.0, is-binary-path#1.0.1, is-glob#2.0.1, readdirp#2.0.0, anymatch#1.3.0, fsevents#1.0.12)
XXXXXMacBookPro:dasding xxxxxx$ chokidar-socket-emitter
bash: chokidar-socket-emitter: command not found
XXXXXMacBookPro:dasding xxxxxx$
Does anyone has any idea why he is unable to find the command? i have no idea how to fix this, global installs always used to work without any problem.
thanks in advance
Ok, in case someone faces the same problem - my current node.js installation was unable to handle the latest version of chokidar-socket-emitter, so a lower version was installed, but the docs refered to the latest version, so there never was a command that could have been found. after updating my node.js installation everything worked like charme.
I updated gulp and this is what I am getting now when I try 'gulp watch'
CLI version 3.8.10
Local version 3.8.10
Image of error:
http://s3.postimg.org/e6usiz1k3/issue.png
Your gulpfile.coffee is being interpreted as a JavaScript file. Node complains about the first comment - # is not a valid character in JS.
A while ago, the proposed solution by the gulp folks to use CoffeeScript was to use a gulpfile.js that requires CoffeeScript and your gulpfile.js. For example, the approach discussed here: https://github.com/gulpjs/gulp/issues/103
However, it seems that since 3.7 transpilers are automagically detected, as long as they are installed in your node_modules/. See https://github.com/gulpjs/gulp/blob/ae98edfbfbe8341f20c7cb5d4d4b8ec339ee44ae/CHANGELOG.md#370
added support for transpilers via liftoff 0.11 and interpret just npm
install your compiler (coffee-script for example) and it will work out
of the box
So you should
Check that your gulp is more recent than 3.7 with npm ls
Try running npm install coffee-script