latex-box-team / latex-box Goto Github PK

Pressing an arrow key closes the TOC and inserts a character in the main text. That should be fixed so that arrow keys behave like hjkl.

I do not want the quick-fix window opened automatically post-compilation. Could an option be added to disable this behaviour?

Currently the calls to latexmk and the viewer don't seem to work on Windows. Not sure whether that is something that can be fixed easily. I am hoping to find some time to look into that myself, but maybe you can give me a few hints what kind of adjustments would be necessary and which functions are affected. Great plugin otherwise! Would like to be able to use it for my work.

when the document includes a .ps file and epstopdf program is called, it detects (epstopdf) as an error

the :copen result is attached

|| This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012) (format=pdflatex 2012.9.9)  27 SEP 2012 01:41
.
.
.
. (skipped)
.
(epstopdf)                    date: 2011-08-25 13|46 error| 26
|| (epstopdf)                    size: 341420 bytes
|| (epstopdf)             Output file: <ch01/01x01.pdf>
(epstopdf)                    date: 2012-06-22 15|2 error| 25
|| (epstopdf)                    size: 5927 bytes
|| (epstopdf)             Command: <repstopdf ch01/01x01.eps>
.
.
.(skipped)

Any plans to support folding?

Using omnicompletion for citations stops for my latex project, which includes about 10 files in the main file.
For smaller projects of just a single file it works without any problems, although it is slow sometimes.

Error detected while processing function LatexBox_Complete..LatexBox_BibComplete..LatexBox_BibSearch..41_FindBibData..41_FindBibData..41_FindBibData..
...
E132: Function call depth is higher than 'maxfuncdepth'

One question. Would it be possible to define the bib-files manually just the same as for the main file?

1. I wonder why the standard mappings like ll etc. are "hard-mapped" to \ as leader and not to etc. ll?!
2. Also (and more importantly) I can't get forward searching using Mac Os X's Skim to work. Your suggestion to create a "latex-search" mapping with

map ls :silent !/Applications/Skim.app/Contents/SharedSupport/displayline
\ =line('.') "=LatexBox_GetOutputFile()" "%:p"

does not work (nothing happens). When I try to execute the command from the vim command line, I get a parse error...

Thanks,

J

I am reviewing the code for the LaTeXMk commands, to be able to port it to windows.

It seems that latex-box uses vimserver for background compilation. This requires the plugin to manage things like PIDs, program names, LaTeXMk running status and so on. Most of the commands uses "bashism" that are not always available on Linux and definitely not on windows.

I was asking me a question, I forward it to the @LaTeX-Box-Team

What are the benefits of using the current method instead of something like this : http://blog.chmd.fr/continuous-background-compilation-within-vim.html (with some adaptations obviously)

In that second method, I see the advantage of having a single command working on each systems. Furthermore, it seems to be lighter than the actual system. No need for vimserver, no need to check for LaTeXMk running status.

What do others devs think about this?

Hey,

in order to make LaTeX-Box compatible with biblatex, it would be nice to have F9-omni-completion not only parse documents for the \bibliography command in order to find the currently used bibtex file, but also for the following commands:
\addbibresource
\addglobalbib
\addsectionbib

I guess this would have to be incorporated somewhere in complete.vim near lines 137-138, but I don’t know ho to implement that.

Best,

Jakob

I'm not trying to be snarky, but is this supposed to work at the moment? I couldn't get it to work with my thesis project, which uses a tex subdirectory for all the different chapters and a single top-level main.tex file. It also uses \include and \includeonly (the latter of which is probably irrelevant here).

I've managed to get label completion with \@input in .aux files in a working state on my refcomplete_with_include branch, but it's slow as molasses, and I'm not sure I can improve it much further. I believe I somehow messed up the caching while playing around. If anyone wants to take a look, it'd be much appreciated.

E.g.

section{A}
subsection{One}

section{B}
subsection{One}

If I select the second subsection, I am taken to the first.

Hi,

First of all, thanks! LaTeX-Box seems to be a very good replacement of LaTeX-Suite!

To the issue: When I use the ToC command on a file where I use 80 columns, it goes back to 77 columns after I hit enter on one of the ToC entries.

Hi, when the omni complete menu is shown, pressing should select the next candidate downwards , while is upwards. But this behavior in Latex-box seems to be reversed.

If I yank a line and then move do a different place in the document using the TOC, I cannot past the yanked line using p - this would only paste an empty line. Instead, I need to paste using "0p.

Hi, all. I find that I cannot use :Latexmk to do background compilation in a tmux vim environment. While :Latexmk works fine in MacVim's GUI.

When I try to invoke :Latexmk in tmux vim, vim says:

"Error detected while processing function LatexBox_Latexmk: cannot run latexmk in background without a VIM server"

I don't know whether it has anything to do with vim "server" mode. So I try to start vim as a server like this:

vim --servername vimwork my.tex

I try :Latexmk again, but the same error appears.

Normally in vim, if the cursor is at the end of a long line, and the up arrow is pressed to go to a short line, then the down arrow pressed to go back to the long line, the cursor returns to the original column towards the end of the long line. LaTeX-Box breaks this. I don't know where the problem arises specifically, but as a workaround commenting out the augroup LatexBox_HighlightPairs section in motion.vim fixes it.

The current documentation simply mentions that the variable "b:main_tex_file" should be set to the main document of a multi-file document. It appears that there are multiple other ways of setting this on a per-file or per-directory basis (e.g. issues #16 and #19) that aren't obvious until reading the closed issues or the source.

If I simply install LaTeX-Box and then run ":help" in a gvim with a .tex file open, the help window opens in the bottom (instead of in the top) and I can not switch back out of the help window.

BibTeX references keys are inserted into the ToC

Example

2.3.2   Revue littéraire des tatouages semi-fragiles
2.3.2.1 Gestion de l'intégrité
HaG06   
LPD00   
Fri98   

Autocompletion of labels does not work for neither item nor theorem labels in the following example:

\documentclass{article}
\usepackage{ntheorem}
\usepackage{enumitem}

\newtheorem{lemma}{Lemma}[section]
\begin{document}
\section{some title}
\begin{lemma}[Title]\label{lem:lalelu}
    Some Lemma.
\end{lemma}
Reference to \ref{lem:lalelu}

\begin{enumerate}[label=(\roman*)]
    \item\label{item:one} one 
    \item two
    \item three
\end{enumerate}

\end{document}

I worked out a fix to this issue in my fork. This fix additionally seems to speed up omnicompletion, but that may be an illusion. If you want to, I will request a pull.

for example when the title is
\section{ abc
edf}

When your tex file contains a lot of equations, you have a lot of parenthesis, brackets and braces which slows vim down significantly when you move around in the normal mode. So I wanted to disable the parenthesis matching and highlighting by :NoMatchParen but I found out LaTeX-Box made it not take effect.

MatchParen is a standard plugin and :NoMatchParen is a built-in command of Vim. I have no idea why LaTeX-Box makes it hard to turn this plugin off.

Also once LaTeX-Box is installed, the following line won't stop loading MatchParen plugin as suggested in Vim help

let g:loaded_matchparen=1

MatchParen still gets loaded when vim open a tex file with red error message popping up at the bottom

Hi,

i usually work with the TOC opened in vsplit. Due to the excellent coloring the TOC hierarchy is pretty obvious. Therefore, it would be great if i could save some screen space by omitting those numbers. Would it be possible to add a <key>: hide #s within the TOC window to toggle the chapter numbers?

The indentation does not occur when using OS.

Scenario:

\begin{itemize}
    \item test
        \en<C-x-o><C-x-o>

Results in :

\begin{itemize}
    \item test
        \end{itemize}

Hi,

I used to use matchit.vim and set my pair of map_words, but LaTeX-Box overwrites the % mapping. It looks like there is no possibility to add custom match parts aside from putting them into the code directly, would it be possible to add an option for that?

Thanks and regards,

Jonas

The in latest version of latex-box, the \cite{ omnicompletion does not work for me. I tested in fresh install, both for the MacVim from the website and from macports.

I am not experienced with git so I am not sure how to refer to a previous commit, but after "reverting" to the version from Jan 9th, it works. That's what I did:

git checkout 9580d0f1f679fb4ef38696dcc7b45c644945ecd4

When you are matching a single suggestion with OmniSense, it does not exit the OmniSense mode. Thus adds :update in place of the suggestion.

It could be improved to exit OS-mode on single suggestion.

I have installed LatexBox (fresh install via vundle, .vimrc in minimal for vundle working)

Onmi suggestions work perfectly for ~\ref{} and ~\eqref{}, but for \cite{} I have "Pattern not found" error.

Using LaTeX-BoX with cmake (UseLATEX.cmake file) will render ToC unavailable.

In fact, LTXBX is looking for the auxfile in the main directory, which is not possible with this cmake configuration.

We need an option in common.vim to be able to set the aux file directory (autodetect would be tricky).

When I have folding enabled via

let g:LatexBox_Folding = 1

pasting of longer texts (30 words) in insert mode (e.g. via ") takes multiple seconds.

I assume there is some insert hook for folding which slows things down. Can it be fixed?

The help system seems to want a file called latexhelp.txt in ~/.vim/doc/ but the only one there is latex-box.txt

I made a copy of the existing file to the name that it asked for and the help displays, but give me an error "E434: Can't find tag pattern"

Dear LaTeX-Box-Team,

there are currently three outstanding pull requests, that have been sitting there for weeks. What is your update policy?

If you need help, I would volunteer to contribute (e.g. merge), although I am no vim expert (yet) and also a bit of a git noob :-) .

Regards
Jonas

\citeauthor, \citeyear, and \citeyearpart are common commands in the natbib package (and compatible citation styles, such as apa.cls with natbibapa option), and it would be nice if ctrl-x ctrl-o also triggered autocomplete for these by default. it's straightforward to just put

let g:LatexBox_cite_pattern = '\C\\cite\(p\|t\|author\|year\|yearpart\)\=\*\=\(\[[^\]]*\]\)*\_\s*{'

in my vimrc, but you could just as easily put that in common.vim.

Omnicomplete works as expected after an open parenthesis.
However if the parenthesis is closed before the omnicompletion call it generates a new line above the one I am editing.

Example:

Starting with:

    Lorem ipsum dolor sit amet, consectetur adipiscing elit~\ref{<CTRL-X><CTRL-O>

Ends with:

    Lorem ipsum dolor sit amet, consectetur adipiscing elit~\ref{section}%<Cursor Here>

But starting with:

    Lorem ipsum dolor sit amet, consectetur adipiscing elit~\ref{<CTRL-X><CTRL-O>}

Ends with:

    %<Cursor Here>
    Lorem ipsum dolor sit amet, consectetur adipiscing elit~\ref{section}

The project has no LICENSE file. I think @mungerd has its idea on what to put in there.

I have a TeX project, where I fiddled with the table of contents. As a result, the @WriteFile{toc}{ ... } commands do not necessarily occur at the beginning of a line in the *.aux file.
I fixed this issue in my fork. Would be nice if it would be merged, too.

Is it possible to respect the $out_dir setting in latexmkrc file as the compilation command \ll does. For instance viewing the file, log, toc (\lv, \le, ...) does not work anymore.

Thanks

UPDATE: another latexmkrc variable is '@default_files' which allows running latexmk without a file name in the command line. This could also be used for compiling a multi tex file project without having to create an indicator file (....tex.latexmain) or adding comment lines to the texfiles (! TEX ROOT = ...).

The g:LatexBox_{open,close}_pats aren't mappings, but options which are only used in a single function (motion.vim's FindMatchingPair). Shouldn't they be set in motion.vim instead of mappings.vim?

Also, the :LatexMk* commands are defined in latexmk.vim. Applying the same reasoning, shouldn't the :LatexTOC command be defined in motion.vim as well?

If you guys agree, I'll submit a tiny pull request to implement that.

LatexBox_LatexErrors() basically just passes calls through to vim's cfile or cgetfile based on the log file, but this only works when the pwd is the directory that contains the main latex file.

If you don't open the file in its own directory, or if you have a complex project with a directory hierarchy (and aren't sitting at the top), then it will simply open the offending file from the PWD, which will likely open a blank file or possibly a different file with the same name.

This would be especially bad (and very misleading) if you had multiple projects with a similar structure, and were in the pwd of project B but your b:main_tex_file was set to project A. Calling LatexBox_LatexErrors() would open up a file from project B, even though the error was being generated from that file in project A.

One fix is to modify LatexBox_LatexErrors() to change pwd to the basedir of LatexBox_GetTexBasename(), but modifying the pwd doesn't seem highly sensible, so I guess another option would be to just provide a warning and not open the file if you're not in the right pwd?

Most cite commands for biblatex are missing omnicompletion cite pattern expression, for example \autocite. Below I have updated the g:LatexBox_cite_pattern variable to include some of them:

let g:LatexBox_cite_pattern = '\C\\\(auto\|foot\|footfull\|full\|paren\|text\|smart\|super\)\?cite\(p\|t\|author\|year\|yearpart\|title\|date\|url\)\=\*\=\(\[[^\]]*\]\)*\_\s*{'

Hi!

I have some main.tex and some dir/topic.tex. If I open the last one and try to autocomplete some reference, it asks for my main file (ok so far).
Now if I skip the command or enter main.tex, the :pwd has changed to inside dir.
Also, autocompletion does not work, neither if I enter main.tex nor ../main.tex.
Is this a bug or am I doing something wrong?

Best regards,

Jonas

When I hit enter inside the Quickfix Window, vim does not automatically jump to the affected line as it should.

Maybe the errorformat is not correct?

I use the IEEEeqnarray environment from IEEEtrantools for some equations. Folding breaks after the environment if I use this environment and try to use unbalanced brackets. An example:

\documentclass{article}
\usepackage{IEEEtrantools}

\begin{document}
\section{Blah}
This next equation messes up folding anything after it.
Seems to be a combination of the \texttt{IEEEeqnarray} environment and
the contents of the \texttt{smash\{\}}:

\begin{IEEEeqnarray}{rCl}
  f \left( x \right) & = & \smash{\left[\IEEEstrut[2\jot]\right.} \beta + 1^{23.25}
\end{IEEEeqnarray}

\section{Bluh}
Insert text here\dots

\end{document}

After the \end{} it won't fold any other sections.

If I exchange IEEEeqnarray for equation, it's fine. If I make the \right. into a \right] it's also fine (well, except that the equation itself doesn't fold, but that's another issue).

It would be nice if omni-completion of labels worked with the cleveref package, as in \cref{}.

The table of content works with include.

The input command is generating error : file is not known to be included as it does not appear anywhere in the aux file.

It seems the source file number is nowhere to be find in the aux file. This means Latex-Box computes it.

It should be possible to parse the file for \input and make this working.

we should avoid using return "=" in the folding method.
it can be very slow when the tex file is relatively large.

one fix is to use return foldlevel(a:lnum-1)

Vim defines text object motions for sections (]], [[, ][). These should be supported by LatexBox to move between ((sub)sub)sections.

Maybe it should be configurable whether movement is done only on \sections or includes also \subsections and (optionally) \subsubsections.

Hello, Im' using latex-box on macvim with great sucess except latexmk seems to not background and only rus when I press \ll to compile. This is not a dealbreaker but I wonder why.

When running vim from the command line and pressing cursor keys or any other "escape-sequence-generating key", the TOC will close and print strange and unwanted characters in the last opened buffer.

The "problem" is that is supposed to close the TOC as one can see here.

I am not sure, if this is a kind of wontfix since hjkl are working fine and running latex-box from command line gives you no compilation either as latexmk cannot be called without a vim server.

I updated to the newest version of LaTeX-Box using Vundle, and it seems that a lot of the commands won't work if called on the second (and subsequent) files opened during a single instance of Vim. Instead, I just get an error message telling me that there is no such command. It still works on the original TeX file opened during that instance, however.

Vim version is 7.3, OS is Arch Linux x86_64.