# Tag Info

25

It would help to know which, if any, LaTeX plugin you're using for vim. (E.g., the latex-suite, vim-auctex, latex-box, etc.) Next, as far as viewer choice, the only widely used open source PDF viewer for Linux which currently supports SyncTeX well out of the box is Okular. That's probably your best choice. There are instructions fo setting up SyncTeX with ...

25

I suppose you already have Vim installed in your operating system. Usually, the installation is very straightforward for every operating system. For Macs, we have MacVim, and AFAIK two options are available: Getting the correct MacVim version for your operating system in the project website, unzip the archive file and drag MacVim.app to your Applications ...

23

I would highly recommend the vim latex-suite, which you can get either from http://vim-latex.sourceforge.net/index.php?subject=manual&title=Manu or (on an Ubuntu machine) using sudo apt-get install vim-latexsuite sudo vim-addons -w install latex-suite It provides many shortcuts. If I were going to type your first summation ...

23

Disclaimer: I usually edit .tex files in Vim, but I don't use the Vim-LaTeX suite. I wouldn't say the following suggestions are tricks per se - they are provided by third-party plugins - but they actually help me with my usual TeX workflow: snipMate Created by Michael Sanders From the manual: snipMate.vim aims to be an unobtrusive, concise vim script ...

22

The Vim-LaTex / LaTeX-Suite for Vim adds these markers automatically and by intension. You can jump to the next such marker using CTRL+J, which removes this marker. The idea is to speed things up by allowing you to jump to the end of the group or environment which was just added. This is also useful for templates where you can add <+name+> markers ...

21

I have the following function in my $VIM/ftplugin/context.vim file to format ConTeXt paragraphs (same as LaTeX: the environments are enclosed in \start... and \stop... instead of \begin{...} and \end{...}. It should be easy to adapt this to LaTeX (In fact, I think that I copied it originally from someone who had written it for LaTeX and adapted it to ... 16 If you write "... this was written by \ref{foo}" the following output is possible: ... this was written by [1] which looks ugly in fact of the linebreak. This is the reason why vim is very nice to you and told you that you should write: "... this was written by~\ref{foo}". Then your output is at least: ... this was written by [1] So it is not a ... 14 The following hopefully answers your "abbreviated questions": vim suggests inserting \@ before . in ...GRIP/ABP. So, do it! The reason here is that GRIP/ABP or any capitalized word before a period is usually an abbreviation. And, in some instances, abbreviations have periods, while some don't. To treat the end-of-abbreviation period as an end-of-sentence ... 13 Your question is a little confusing. What you mean is compiling a LaTeX document manually (into a PDF). You might want to adjust your title. Creating one would be the process of writing the document. This can be done in the command line using pdflatex <filename>. In VIM you could just use ESC:!pdflatex % (% can be used instead of the current filename) ... 11 Quick and dirty solution :syn match texStatement "\\[a-zA-Z_:]\+" or add @ :syn match texStatement "\\[a-zA-Z_:@]\+" It isn't enough, but looks much better. But better Modify$VIM/syntax/tex.vim, search b:tex_stylish, and modify all expressions about it.

11

With the vim-latexsuite spell-checking works fine. Since it makes typing latex files a lot easier and faster I can only recommend it to every LaTeX-writing vim user.

11


7

The following solution only applies to paragraph formatting, it will properly work depending on the LaTeX styling settings. Another possible solution would be to set a hard wrap of 80 characters. http://vimcasts.org/episodes/hard-wrapping-text/ formatoptions: t - Auto-wrap text using textwidth c - Auto-wrap comments using textwidth, ...

7

A quite long comment... I don't think your question is specific to Vim or any other editor. Whether you are given a code completion, auto-environment closing tool or not it is quite important to reduce the mental load while writing your code. A short-term loss can be a long-term benefit if you can spend extra seconds to write-up with a better indentation. I ...

7

There are no real standards, but here are some tips I’ve found handy: Don’t indent parts of a paragraph, but do break lines between sentences and after significant phrases within a sentence. As I posted at http://tex.stackexchange.com/a/64538/2966, this makes it easier for small edits to have small diffs. (You are using a VCS, aren’t you?) To exaggerate my ...

7

If I understand your question correctly, you're having problems to get Alt-i working in the console version of vim, right? At least, with gvim it works as expected on my system. Some terminals send different character codes when using Alt key combinations so that vim is unable to recognize them properly. To fix this, it might help to enable the meta key ...

7

I stumbled upon this one today, as also already posted above. http://michaelgoerz.net/refcards

7

I use the vim-latex suite, and absolutely love it. However, I've found the following tweaks quite useful to help me compile my documents. (These commands will be most useful to Linux users) I like to 'toggle' between seeing the compiler output and not. With the setup below, I simply press t which toggles between 'silent' and 'verbose' mode I like to be ...

Only top voted, non community-wiki answers of a minimum length are eligible