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
Related
I'm trying to use Steel Bank Common Lisp with GVim.
I installed Steel Bank Common Lisp (AMD64) into 'C:\Program Files\Steel Bank Common Lisp'.
I unzipped SLIMV into 'C:\vimfiles'
I installed Python3 and put it in Windows PATH.
I installed Python 2.7 and put it in Windows PATH.
I installed 64-bit GVim and finally got Python recognized.
I ran ':helptags C:/vimfiles/doc' in Vim to generate help tags for SLIMV
I have a 'Slimv' menu at the top of the Vim window but no Repl menu.
g:slimv_lisp = sbcl
g:slimv_impl = sbcl
g:slimv_preferred not set
g:slimv_lisp not set
g:slimv_swank_cmd not set
Per webpages and manual, I put this in my vimrc file
let g:slimv_swank_cmd = '!start "c:\Program Files\Steel Bank Common Lisp\sbcl.exe" -l "c:\Users\epic\vimfiles\slime\start-swank.lisp"'
I don't know if that's supposed to be 'set' instead of 'let'.
(start_swank) doesn't do anything inside SBCL.
I assume '!start' is a Vim command, the first thing passed is the location of SBCL on my computer, don't know what the '-l' does, and the third parameter is where SLIMV put 'start-swank.lisp'.
At this point, the Vim command ',c' will open a command window running SBCL and wait. Typing '(exit)' in SBCL will take me back to Vim with a red error message saying 'SWANK server is not running, Press ENTER to continue."
Any other documentation I can find is for SLIME, not SLIMV.
How can I get SLIMV running so I can use Vim for SBCL?
EDIT:
Thank you for the help as to what I'm telling to do what, romaini. Thanks for the slimv help, Tamas.
I have removed the g:slimv_swank_cmd entry in .vimrc, as I believe it does the same thing by itself that it would if I had the command right.
Now, I think I'm back to the problem I was trying to fix with that command, and that might be that SBCL is not working for me (?). Without the g:slimv_swank_cmd setting in .vimrc, Vim starts SBCL which then fails because COMPILE-FILE returns NIL when evaluating line 16 of start-swank.lisp. Vim will then report "SWANK server not running" while SBCL is at a debug screen asking whether to RETRY, CONTINUE, ABORT,,,, or EXIT.
Could it be that slimv is working well but SBCL is not working? I'm still trying in Vim to either compile a program (* 3.0 4.0), evaluate the line, or just connect-server ',C'.
EDIT2:
Trying to install a newer version of slimv from GitHub, I'm afraid we've hit the end of my capabilities. The Readme says to install the zip, reading the whole thing says see internal docs for more, and the internal docs say unzip the zip file in the vimfiles directory. There are lots of files on Github but I don't see a zip.
EDIT3:
With slimv-master.zip from github extracted to .vimfiles, I get the same error that "COMPILE-FILE returned NIL" while evaluating line 16 of ./slime/start-swank.lisp.
EDIT4:
Apparently, the SBCL download went from v2.2.0 to V2.2.1 since 01-26-22. I'm on a 64-bit Windows 10 machine and my SBCL download is automatic from SourceForge after clicking Windows-AMD64 here. I have the same issue, ./slime/swank/sbcl.lisp returns NIL from line 16 where COMPILE-FILE returns NIL. It is starting SBCL v2.2.1 now.
EDIT5:
Both my versions of slimv were extracted to ./vimfiles/. My ./vimfiles/slime/slime.el is Version 2.19. Did the newer slimv version not overwrite files when extracting to ./vimfiles/? Is there an uninstall when we're just extracting zips to ./vimfiles/?
EDIT6:
I don't have a check mark next to comments to mark the last of Tamas Kovacs' responses as the answer (as was the rest of his help through the comments). I now have a REPL window in Vim and Tamas solved my issue.
I summarize the results of our investigation (see comments above):
No need to set slimv option g:slimv_swank_cmd, because slimv should autodetect sbcl and build the correct start command for the swank server.
If autodetection fails or you want to make your own start command for any other reason, then you should use the --load switch (instead of -l) for loading a script into sbcl (the switch depends on the lisp implementation). On Windows machines I also suggest adding /MIN to the !start command, that would start the swank server minimized. This is an example start command for starting sbcl on Windows:
'!start /MIN "c:\Program Files\Steel Bank Common Lisp\sbcl.exe" --load "c:\Users\epic\vimfiles\slime\start-swank.lisp"'
Unfortunately vim.org has an outdated version of slimv, and recent changes in sbcl broke compatibility with the swank server contained in that slimv version. Therefore I strongly recommend that you download or checkout slimv directly from the github repository: https://github.com/kovisoft/slimv
When downloading the slimv-master.zip file from github and manually installing it, make sure that you extract the files from the zip to the proper subdirectories of the vimfiles folder of vim. This means that the contents of slimv-master\ftplugin should go into vimfiles\ftplugin, slimv-master\slime should go into vimfiles\slime, etc. In other words the slimv-master directory in the zip represents the vimfiles directory on your system. Of course this also holds when you install slimv by checking it out from github.
I'm working with a fresh install of python-mode (installed with Vundle on Vim 8) and find that "go to definition" mapping never works no matter how I set g:pymode_rope_goto_definition_bind.
Then I found RopeGotoDefinition is not an editor command. How could this happen? I'm confused.
Solved it by myself before someone thinks I can't even do a git clone.
After digging into the plugin code, I found g:pymode_rope_goto_definition_bind is actually mapped to :call pymode#rope#goto_definition()<CR> rather than :RopeGotoDefinition which appears only once in the whole repo.
After verifying :call pymode#rope#goto_definition()<CR> command works as expected, I found my problem (failing to map) was caused by terminal emulator and Vim eating up all Ctrl+letter combinations. Something other than that works well, e.g. let g:pymode_rope_goto_definition_bind='<leader>pg'.
As for :RopeGotoDefinition, maybe it's just the remnant of old code lingering in the documentation.
When I use vim to open one markdown file. i meet the following issue.
My Vim version is 7.4 and i use it on MacBook Pro with OS X Yosemite.
The following are the vim plugins i installed:
Anybody can help on this? many thanks:-)
Adding runtimepath
I got this error after I installed the Vim plugin YouCompleteMe. After I updated my html5.vim Vim plugin the issue disappeared for me.
You're missing the $VIMRUNTIME/autoload/htmlcomplete.vim script; in your case, it should be at /usr/local/Cellar/vim/7.4.488/share/vim/vim74/autoload/htmlcomplete.vim. If it really isn't there, try reinstalling Vim. Else, it might be a problem with your 'runtimepath'.
Edit: It is the latter; your 'runtimepath' has ~/.vim twice, at the beginning and end, no after directories, and not the .../share/vim/vim74 global one. Find our what messed up your 'runtimepath'.
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 just installed gvim on fresh installation of ubuntu lucid. I've messed this up before that's why I want to start on the correct step here.
Where should I keep all my plugins and my .vimrc??
my current runtimepath on gvim is:
runtimepath=~/.vim,/var/lib/vim/addons,/usr/share/vim/vimfiles,/usr/share/vim/vim72,/usr/share/vim/vimfiles/after,/var/lib/vim/addons/after,~/.vim/after
one thing that i've never been able to get working on gvim is snipMate. Anyone has pointers on having that work with gvim?
I use pathogen with ~/.vimrc and plugins in ~/.vim/bundle, more details here. You can see an example here.
Plugin folder is always under ~home/.vim or ~home/vimfiles your vim configuration file or .vimrc always in your ~home/ as for example: ~home/.vimrc
Snipmate fully works for me under Ubuntu. unzip it correclty and it should work right. BTW a great great plugin.