On Sat, 21 May 2011, Przemysław Pawełczyk wrote:
### Issue
For larger LaTeX documents splitting text between many files is a
common practice. And here comes the problem with package detection in
Vim-LaTeX. If I open the main `.tex` file (i.e. the one including
other `.tex` files), where `\usepa
On Tue, 15 Feb 2011, Ted Pavlic wrote:
> (I guess someone(?) could add a feature that looks for "blah.jobname"
> files that function similar to "blah.latexmain" but sets up the right
> jobname instead...)
Isn't it better to make blah.latexmain a configuration file, so that it
may contain
jobnam
On Sat, 13 Mar 2010, Nicholas Laszlo Frazer wrote:
> I did not get any responses. Is there somewhere else I should ask? Is
> there more information I should provide?
Your minimal example works fine here. \ll compiles the document without
any errors. But I am using texlive 2009 on arch linux (a
On Fri, 21 Aug 2009, rocku wrote:
> Ted Pavlic pisze:
>> Without giving it much thought, try something like...
>>
>> \begin{verbatim}
>> \endverbatim
>> \begin{code}
>> ...
>> \end{code}
>> \verbatim
>> \end{verbatim}
>
> This does not work, I receive the following after \ll in vim (using
> texliv
that When I compile "intro.tex" file, latex
> compiles "main.tex" but somehow the job is aborted.
main.tex is compiled because of main.tex.latexmain.
>
> The output of ":cl" gives:
> E42:No Errors
This is because emergency stop is not captured by the errorfo
On Wed, 29 Aug 2007, ahmet nurlu wrote:
> I recently have a problem with multiple file latex
> projects. It was not happening before and has appeared
> suddenly. My directory layout such as the following:
>
> thesis/
>main.tex
>main.tex.mainlatex
On Mon, 4 Jun 2007, Donnie Pennington wrote:
> It would be helpful to vim and latex newbies if the vim-latexsuite
> documentation could make clear that vim (as opposed to gvim) will not
> load the latexsuite plugin when you first create a new empty .tex file.
> You have to "prime the pump" as docu
On Wed, 7 Feb 2007, Sandeep wrote:
> Hi,
> I am using GVIM 7.0 + Miktex. This installation had some hiccups. GVIM
> complains at the startup which disappears too quickly to make sense.
Try :message to see the output. The exact error message may be useful
to determine what is going wrong.
Aditya
On Tue, 8 Aug 2006, Christian Ebert wrote:
> * Aditya Mahajan on Monday, August 07, 2006 at 18:18:19 -0400:
>> On Mon, 7 Aug 2006, Christian Ebert wrote:
>>> * Manu Hack on Monday, August 07, 2006 at 15:17:33 -0400:
>>>> After I updated to Vim 7, I cannot use
On Mon, 7 Aug 2006, Christian Ebert wrote:
> * Manu Hack on Monday, August 07, 2006 at 15:17:33 -0400:
>> After I updated to Vim 7, I cannot use the command because if I add the
>> usepackage line, it appeared like
>>
>> <++>]{amsmath}``usepackage[X
>
> I can confirm this. Exept I get double quot
On Tue, 1 Aug 2006, Gastón Araguás wrote:
> Hello
>
> how can i do to put the *.log and *.aux *.toc in the same directory
> where i'm compiling but under tmp/?
>
> what i'm doing now is (my ~/.vim/ftplugin/tex.vim)
>
> let g:Tex_DefaultTargetFormat = 'pdf'
> let g:Tex_FormatDependency_pdf = 'dvi,p
On Sat, 15 Jul 2006, Mark Gesing wrote:
> Hi,
>
> I am in the habit of splitting my latex sources into several files so that
> the source is easier to manage.
>
> How can I set up the suite so that all files with filenames ending in *.tex
> enable the vim-latex suite? Currently only the document c
On Wed, 17 May 2006, Andreas Wagner wrote:
Hello Kim, hello list,
* Kim Schulz wrote on Mai/15/2006:
Whenever I execute one of the insert mode commands (like EIT) then it
inserts the template correctly but the text in the entire document changes
syntax coloring to have white background. I can
13 matches
Mail list logo