I have installed the Syntastic vim plugin using Pathogen and am attempting to have my puppet files validated using puppet and puppet link checker.
I can see errors and warning from puppet-lint, but in addition to that I would expect the puppet validation to run to highligh syntax errors. Would you know what might cause only puppet-lint to run?
FYI, I am trying to get this to work in gVim
I have a similar setup and the puppet-lint checker as well as the puppet run fine for me.
Issuing the :SyntasticInfo command for a .pp file gives me the following:
I am pretty sure that this just might be a case of the puppet executable not being on the path, and hence not available for the validation.
Related
I'm currently using Vim 7.4 on Ubuntu 16.04. I have the Syntastic plugin installed via pathogen.
I'm currently doing some coding in C using the mpi library. When I write my code using Vim, syntastic seems to believe that there is an error and tells me that "'mpi.h' file not found" (this is for #include <mpi.h>). I know that this program compiles as I'm able to run mpicc successfully.
When I run a locate mpi.h this is what I get back:
/usr/lib/openmpi/include/mpi.h
/usr/lib/openmpi/include/openmpi/ompi/mpi/fortran/mpif-h/prototypes_mpi.h
/usr/src/linux-headers-4.4.0-62/include/linux/mpi.h
/usr/src/linux-headers-4.4.0-66/include/linux/mpi.h
How can I get Vim to stop giving me these errors?
Create a file .syntastic_cpp_config in your project home folder.
Have all your include folders listed in it. In your case,
-I/usr/lib/openmpi/include
Or the other folder with mpi.h, whichever you use in your build.
I'm trying to compile geany-plugins-1.28. The debugger plugin (the only one I need) gives the error:
debug.c:53:21: fatal error: vte/vte.h: No such file or directory
#include <vte/vte.h>
Clearly it needs to know where this file is located to compile. I found the vte.h file in the src directory of the main program geany-1.28. When running
sudo ./configure cflags=-I/home/pi/Desktop/geany-1.28/src
I get the same error about the missing header later trying to compile the debugger plugin.
I ran
./configure --help
to get all the flag options. The output is here
How do I get this to configure correctly so that it compiles. I need to compile the debugger version 1.28 myself because apt only installs 1.24 which I think has a bug because it crashes when I run my code with the error:
close failed in file object destructor:
sys.execpthook is missing
lost sys.stderr
CFLAGS is case-sensitive environment variable, so you should set it before running configure, not try to pass it as a command line argument. This variant:
$ export CFLAGS=-I/home/pi/Desktop/geany-1.28/src
$ ./configure
leaves CFLAGS set for current shell until you leave it. While this:
$ CFLAGS=-I/home/pi/Desktop/geany-1.28/src ./configure
sets variable only for current command, i.e. configure.
Some other issues:
You do not need sudo to configure and make. It is also unnecessary for make install if you set PREFIX to a path you have privileges to write to.
Does plugin's build system also builds all it's dependencies? If not, you may face linker errors a bit later.
Update:
I have tried to build debugger plugin and got rid of your error. It seems that vte.h coming with Geany is it's intrinsic, while the plugin requires full-featured file from the library. So I just installed vte and vte-devel from repos. Nevertheless, I got some other unrelated errors coming from Glib. I will not continue my attempts to build all this right now. Hope my effort will be helpful at least a little.
As in this answer stated, vte.h is not the file you are looking for. Install libvte(-dev) package on your system and rerun configure.
Just for the record: vte.h on Geany is a dummy to allow Geany to kind of dynamical enable vte or disable it depending on vte is installed on the system or not.
My setup
I already installed gocode with the command go get github.com/nsf/gocode.
I use Pathogen to manage my Vim plugins. I installed vim-gocode with git clone git#github.com:Blackrush/vim-gocode.git.
What I’m seeing
The :Fmt command works ok, but I can’t autocomplete my golang code. It reports an error like in this image:
Can someone help me?
Please ensure you have YCM or neocomplete installed. You need some additional binaries to get all features. Following on the vim-go repo tells you how to install them.
All necessary binaries should be installed (such as gocode, godef, goimports, etc.). You can easily install them with the included :GoInstallBinaries command, by running command in your vim.
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.
Syntastic works for me in general (say, if I edit C/C++ files then I get syntax error notifications), but I can't get it to show syntax errors for OCaml.
My OCaml install seems fine otherwise, and the binaries that are mentioned in the header of Syntastic's ocaml.vim file are in my path.
Any ideas?
The most likely reason is that none of the syntax checkers that it requires is installed. For example: python requires either flake8, pyflakes or pylint to be installed and in $PATH. To see which executables are supported, just look in syntax_checkers//*.vim. Note that aliases do not work; the actual executable must be available in your $PATH. Symbolic links are okay. You can see syntastic's idea of available checkers by running :SyntasticInfo.
Another reason it could fail is that either the command line options or the error output for a syntax checker may have changed. In this case, make sure you have the latest version of the syntax checker installed. If it still fails then create an issue - or better yet, create a pull request
Source:
https://github.com/scrooloose/syntastic
Merlin provides much more complete checking than Syntastic's included checker and will give proper type errors and let you use packages outside of core.