New answers tagged filetype-tex
4
You might want to consider adopting the vimtex plug-in, which improves support for TeX files in Vim.
Among its features, it supports custom folding, which is able to recognize LaTeX blocks delimited with \begin{...} and \end{...} and use them to define folding.
Furthermore, it recognizes {{{ and }}} but only within comments.
See vimtex's documentation under :...
1
I hope it's OK to answer my question once again, the answer is easy once you know about the existence of the vim-pandoc plugin, but somehow I couldn't find it directly . I use Vundle to install plugins, added the following to my .vimrc:
" Markdown citation and syntax
Plugin 'vim-pandoc/vim-pandoc'
Plugin 'vim-pandoc/vim-pandoc-syntax'
" Disable ...
3
First you need to create your command as local to a buffer, :h :command-buffer tells us that is what the argument -buffer is for.
Then I think it's better to use ftplugins (:h ftplugin) to do this kind of things rather and a Filetype autocommand which just duplicate a built-in mechanism.
So you could create ~/.vim/after/ftplugin/rmd.vim and put that in it:
...
0
I now use the vimtex plugin with the :VimtexTocOpen command to open a table of content for latex files.
See also :help vimtex-nf-tag-nav:
One may navigate by tags with the |CTRL-]| mapping, e.g. from
\eqref{eq:example} to the corresponding \label{eq:example}. However,
this requires that a tag file has been generated with |ctags|. I recommend
that one uses ...
4
why is stderr redirected to stdin,
In order to have both end up in the quickfix list.
what is that second command with tee doing,
man tee. It redirects stdin into a file and into stdout. It's an extremely useful command to log and watch the execution of commands that send a massive amount of lines into stdout and/or stderr.
and how do I remove both ...
Top 50 recent answers are included
