Closed pupbrained closed 1 year ago
Hello ! Thanks for reporting this bug. When does the error actually appears ? When you run neovim or when completion is supposed to happen ? I was not able to reproduce the error.
For a few weeks now, the python dependencies of coq-nvim have been included in the nix package.
Hence, you shouldn't have to run :COQdeps
as the dependencies should already be available.
Please, make sure that your nixpkgs
source is up to date.
Completely unrelated: You can simplify your keymap declaration by using mkMaps {silent = true;}
.
See an example in my config: https://github.com/GaetanLepage/dotfiles/blob/bbaf4ab590e3a50a39f1c859bb7255103dbac4d6/home/tui/neovim/keymappings.nix#L8
Hello ! Thanks for reporting this bug. When does the error actually appears ? When you run neovim or when completion is supposed to happen ? I was not able to reproduce the error.
The error occurs upon running neovim.
For a few weeks now, the python dependencies of coq-nvim have been included in the nix package. Hence, you shouldn't have to run
:COQdeps
as the dependencies should already be available.
I assume that this issue has something to do with this update, considering COQ has worked for me up until recently.
Please, make sure that your
nixpkgs
source is up to date.
I have made sure all of my sources are up to date. I have just now updated my flake again and rebuilt my configuration, and I'm encountering the same issue.
If it does make any difference, I have this same configuration on a different device running NixOS x86_64 and I do not have this issue. I only seem to have it with my MacBook running macOS aarch64 w/ nix-darwin.
If it does make any difference, I have this same configuration on a different device running NixOS x86_64 and I do not have this issue. I only seem to have it with my MacBook running macOS aarch64 w/ nix-darwin.
Very interesting. What is strange then, is that you don't experience any failure during the building process. Hence, the dependencies are installed correctly I guess. So maybe, it is a problem of the way COQ is looking for its dependencies on arm darwin.
Can you try the following ?
:checkhealth provider
import std2
.Then we will be able to see if the package has been installed at all.
No errors when importing. It seems that python is fine?
Hmmm, yes. Could you now try from std2.sys import autodie
?
Seems to import just fine... odd.
Ah, I think I've found the problem.
For some reason, the autodie
function is instead named suicide
on my machine.
After looking at std2's git repo I can see that the function was renamed a while back.
Oh nice catch. However, why isn't coq_nvim using the same version of std2 on both machines ? You suggest that you have an outdated version of std2 on your mac right ?
Oh nice catch. However, why isn't coq_nvim using the same version of std2 on both machines ? You suggest that you have an outdated version of std2 on your mac right ?
Yes, it was. After deleting .local/share/nvim/coqrt
COQ began to work just like before. I'm still not sure why that was out of date, though?
Yes, it was. After deleting
.local/share/nvim/coqrt
COQ began to work just like before. I'm still not sure why that was out of date, though?
Indeed it makes sense. What happened is that you had a local copy of the coq python dependencies in your ~/.local/share/nvim
which was being used instead of the one bundled in the derivation. Hence you had the bug.
By deleting it you made coq use the right one. You should be done with dependency installation now !
I am closing the issue.
Plugin affected: coq-nvim Nixpkgs channel: unstable Home-manager version: unstable
Description
As of the past week or two, coq-nvim has been completely broken for me with the error:
Attempting to run :COQdeps like said in the error message returns:
Config
https://github.com/pupbrained/nix-config/blob/mac/pkgs/nixvim/default.nix