# Tag Info

21

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 ...

6

The following works on my end: Create a file called latexmk.vimrc in the current directory with the following content set nocompatible filetype plugin on set grepprg=grep\ -nH\ $* filetype indent on let g:tex_flavor='latex' let g:Tex_DefaultTargetFormat = 'pdf' let g:Tex_CompileRule_pdf = 'latexmk -pdf -f$*' set iskeyword+=: Call vim -u latexmk.vimrc ...

6

If you are using Adobe Reader or certain other PDF readers it locks the file. I don't know what OS you are on, but based on discussion in the chatroom Reader only locks the file on Windows. If you are indeed on Windows switch to Sumatra PDF, which does not lock the file. I don't know what linux or Mac PDF readers lock the file, but you should try switching ...

5

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 ...

4

Normally, you should have {}<++>, where <++> is a placeholder where you can jump using Ctrl+J. It seems like the delimiters for placeholders have been replaced by {}. From the documentation of latexsuite, maybe you should verify the value of the variables Imap_PlaceHolderStart and Imap_PlaceHolderEnd to check whether these have respectively been ...

3

Checkout your vim setting of backspace via :set backspace?. If it doesn't contain start you should add this :set backspace+=start (help :h 'backspace') to get the expected behavior of vim-latex. Honestly, I think this should be noted somewhere in the vim-latex documentation or even set automatically by the plugin since it relies on it.

3

I think this is the expected behaviour in vim-latexsuite and it may just be a bug in the quickstart tutorial. If you want to change to get this \begin{eqnarray} \label{}<++> \end{eqnarray}<++> with the cursor in between the label brackets, you can define the following variable and then type eqnarray followed by F5. let g:Tex_Env_eqnarray ...

3

It allows you to jump outside of the grouping operators by pressing CTRL J When you press CTRL J, the cursor takes you to the position, deletes the <++>, and leaves you in insert mode, ready to type. Once you get used to it, it is a very useful device and huge time saver. You'll also find the <++> device if you type enumerate and then press F5 ...

3

Something that is pretty much as useful is to type nameofenvironment then F5 which gives \begin{nameofenvironment} \end{nameofenvironment}<++> and puts the cursor in the body of the environment. You can leave the environment easily by pressing CTRL J

3

If your list of lines is surrounded by blank lines, the following mapping will work: :map <f6> {jV}:s/^../\\item/<cr>{jV}k<f5>itemize<cr> Place the cursor anywhere in your numbered list and press F6 Update A more general approach is to search backwards until the first line which does not start with a digit, and select from that ...

2

There are several tools which can can help you. arara The cool tool arara provides several rules to specify all compilation steps from inside the document. For example you want to compile with pdflatex+bibtex+pdflatex you need the following lines in the preamble of the main document: % arara: pdflatex % arara: bibtex % arara: pdflatex After this ...

2

LaTeX Suite's help provides quite a bit of information of such mappings. Quoting from the help file Changing commands *ls_3_2_3* *ls_a_br* *changing-commands* *ls-vmap-f7* *ls_a_dY* In both insert ...

2

You can use \lq and \rq for the left and right quote, respectively. It may be quicker than deleting one of keyboard quote signs, indeed. Probably a quicker solution is a definition for both quotes, e.q. \def\bsq#1{%both single quotes \lq{#1}\rq}

1

I have encountered the same problem as the OP, and I found that it is caused by the neosnippet configuration, which contains the folloing lines: " For snippet_complete marker. if has('conceal') set conceallevel=2 concealcursor=i endif The neosnippet plugin probably uses the 'conceal' feature of vim for some of its autocompletion functions. The solution ...

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