Vim latex: disable quickfix

latexvim

How can I disable latex's quickfix feature when editing tex files (having vimlatex installed). But I want to keep it for any other language…

Pretty sure this is just a small flag, didn't find it 'though.

Best Answer

_{Note: I do not have vim-latex installed. I have just looked at likely parts of the plugin’s code.}

What behavior do you want to avoid?

The documentation says that you can set g:Tex_GotoError to prevent automatically jumping to the first error after using \ll to compile.

let g:Tex_GotoError = 0

Also, the code indicates that you can inhibit the log file preview-mode window (below the quickfix window) by setting Tex_ShowErrorContext:

let g:Tex_ShowErrorContext = 0

I did not see an option for controlling whether the quickfix window itself is left open, however. You can close it manually with :cclose (which can be shortened to :ccl).

For both of the above variables, you can use a buffer-local (b:…) or window-local (w:…) instead of the global (g:…) to localize the effect if you do not want to change the behavior globally.

Related Solutions

“No protocol specified” when running vim with sudo

A recent upgrade changed default settings for sudo. If anyone have this problem check your sudoer configuration. From an example in the man page:

# Run X applications through sudo; HOME is used to find the
# .Xauthority file.  Note that other programs use HOME to find
# configuration files and this may lead to privilege escalation!
Defaults env_keep += "DISPLAY HOME"

Make sure you have something like that in /etc/sudoers (use visudo to edit the file if you need to).

EDIT: I don't know exactly since when, but at least xauth 1.0.9 supports the environment variable XAUTHORITY. Setting that and leaving HOME untouched, also fixes the protocol warning and is the better solution, as no world-writeable IPC resources (sockets/pipes) are created pointing to root resources (one avenue for privilege escalation). xauth doesn't automatically export the variable to the environment, so the best way is to set it in your shell's initialization.

Become Root from Inside Vim – How to Use Sudo in Vim

sudo cannot change the effective user of an existing process, it always creates a new process that has the elevated privileges and the original shell is unaffected. This is a fundamental of UNIX design. I most often just save the file to /tmp as a workaround. If you really want to save it directly you might try using a feature of Vim where it can pipe a file to another process. Try saving with this command:

:w !sudo dd of=%

Tested and works. Vim will then ask you to reload the file, but it's unnecessary: you can just press o to avoid reloading and losing your undo history. You can even save this to a Vim command/function or even bind it to a key for easy access, but I'll leave that as an exercise to the reader.

Best Answer

Related Solutions

“No protocol specified” when running vim with sudo

Become Root from Inside Vim – How to Use Sudo in Vim

Related Question