I seem to have to run RopeGenerateAutoimportCache every time I open my python project in vim before RopeAutoImport will work. If I run RopeAutoImport before caching the projects modules I get the following error:
Global name my_func not found!
Is there a way of either generating the cache on each vim startup, or preferably, saving the cache to be reread on startup?
I went back to python-mode (which is the suggested plugin for python) and found a problem in the code for which, at the time writing this, I have a patch to be merged: github.com/klen/python-mode/pull/488
I am no longer seeing this problem with the patched code.
Related
I recently was looking into nvim, and was Downloading the vim-airline-gruvbox-git from the AUR, which resulted in this error, even after multiple tries of uninstalling the package/plugins and reinstalling everything:
Error detected while processing function <SNR>29_on_window_changed[22]..<SNR>29_init[29]..<SNR>29_on_colorscheme_changed:
line 4:
E117: Unknown function: airline#init#gui_mode
And I sadly have no Idea what I can take from this and how I should go about fixing it.
I know I should of looked if there was a github for this and added it to my configs, but here I am.
Edit: I resolved it by deleting some Folders named nvim, looked if it worked, maybe reinstalling here and there. Sorry for not remembering what Folders I deleted, but if you make this exact mistake, a probably cleaner solution is in the Comments (thanks TornaxO7).
A quick look into its PKGBUILD:
# ...
url="https://github.com/morhetz/gruvbox"
# ...
source=("$pkgname::git+https://github.com/morhetz/gruvbox.git")
# ...
it looks like that it's actually just installing the gruvbox (this is the link from url in the PKGBUILD!) theme for airline:
install -Dm755 ${srcdir}/${pkgname}/autoload/airline/themes/gruvbox.vim ${pkgdir}/usr/share/vim/vimfiles/autoload/airline/themes/gruvbox.vim
but it does not install vim-airline itself. So all you need to do is installing vim-airline as well.
I had an unrelated problem with vim a while back, that I thought deleting all vim files would help. It did not, but now I have a new problem. Whenever I try to put syntax on, it says:
Error detected while processing /home/jonah/.vimrc:
line 16:
E484: Can't open file /usr/share/vim/syntax/syntax.vim
I've tried reinstalling fully, but it doesn't fix the issue.
You still have a broken Vim installation with missing runtime files. The file $VIMRUNTIME/syntax/syntax.vim needs to be there. You should never modify / remove system runtime files in /usr/share/vim yourself! Use your distribution's package manager (you didn't tell which Linux disto you're using) to completely reinstall Vim, and ensure that the file is there.
I would really like to use easytags, but after following Odding's installation instructions, that is first installing misc and then installing easytags, at startup vim is throwing the "misc is not installed,easytags is broken" error. I am just unzipping them into my vim directory as I have always done with other plugins.. Any suggestions? thanks!
Installation is indeed a simple unzipping of both misc.zip and easytags.zip into the same ~/.vim/ directory.
Check out the :scriptnames command from Vim to see whether all files got successfully sourced. After a manual :runtime autoload/xolox/misc.vim, it should contain entries like:
205: ~/.vim/autoload/xolox/misc.vim
278: ~/.vim/plugin/easytags.vim
If you're still facing problems, please open an issue on the plugin's issue tracker.
I have a problem with installing SuperTab from vimball. I get an error:
E739: Cannot create directory: C:\Users\Pawe<b3>\vimfiles
I guess the problem is the directory name which is C:\Users\Paweł\vimfiles. Is there a way to solve it without changing directory name? Btw: I have set encoding=UTF-8 in my vimrc.
Edit:
The way I install it is so: download .vmb file, open it with vim (using context menu: 'edit with vim') and then I write :so %. And the error occurs.
Using :set verbose=20 I get http://pastebin.com/BLaeLzuU (those are things I found interesting).
And here's the wider story. I was trying to install plugins using vimballs, because I failed running plugins with pathogen (identical case as here: https://github.com/tpope/vim-pathogen/issues/110. In fact my output of :scritpnames is here: http://pastebin.com/YBTBvsvz). To tell you the truth I even tried to copy folder plugin form plugins git repo to my ~\vimfiles. With no success (they are not mentioned in scriptnames). And so I don't have any clue what is going on. Only that output from vimball tells me that it could be the path name. Other then that, I'm hopeless.
Btw: using Windows 8 if that's a deal breaker.
Eventually I have renamed the user name and user folder because the directory name was a problem for other aplications too. Here are the instructions: https://superuser.com/questions/495290/how-to-rename-user-folder-in-windows-8
I just downloaded and installed vim74 on to my linux box. I'm only installing locally, for the user. When I go into vim, and do :help, I get the error.
I tried adding:
let $VIM='home/myuser/vim74'
let $VIMRUNTIME='home/myuser/vim74/runtime'
to my .vimrc but it didn't help. How can I fix this?
When building vim yourself and installing locally it seems that you need to generate the helptags manually from within vim since the build process doesn't seem to do it. I ran into this very same issue when building the latest vim version 8.0.311. I followed the link in Ben Klein's comment above, but both my &helpfile and &runtimepath were correct, yet I still received the E149 error when doing :help which I assume is your situation as well postelrich.
I found the helptags solution here:
https://github.com/Homebrew/homebrew-core/issues/1087
Even though I was installing vim locally on a centos system and not a mac, the issue seems to be universal. I just replaced $VIMRUNTIME with the path to the local vim runtime installed from make install, which in your case may be something like /home/myuser/vim74/runtime
Specifically I ran this from within vim:
:helptags ~/share/vim/vim80/doc
In your case you will probably run something like:
:helptags ~/vim74/runtime/doc
Once done, :help should immediately start working again without having to restart vim.
You can get the same “E149 Sorry no help for help.txt” error if you have a long-running Vim session and the Vim program files were upgraded in the meantime.
This happened to me: I had started an editing session in a GNU screen window on my Debian testing system using Vim 8.1. Some time later, unattenttended-upgrades upgraded Vim 8.1 to 8.2 with the result that the run-time paths were now no longer valid. I could have saved the session and restarted Vim, but it was simpler/easier to run the following command (specific to 8.2):
:set helpfile=/usr/share/vim/vim82/doc/help.txt