Re: [Vim-latex-devel] "jump to error" doesn't jump

2007-06-12 Thread Martin Sander
Hey list. Like others I have been annoyed by the non-working "jump to error" behaviour in the quickfix window, and although I am not a hacker I found a workaround (it hasn't undergone any testing yet, but it works for my little project now). I do :let g:Tex_CompileRule_dvi='latex -interaction=n

Re: [Vim-latex-devel] same target file, different ways to compile?

2007-06-17 Thread Martin Sander
If you use some *nix, you can do what I did with a similar problem. You may know that when you use more than one source file, you can specify the main (lets say its foo.tex) file by creating an empty foo.tex.latexmain file. So just create this file, and put a string in it describing your change, e.

[Vim-latex-devel] jump to error suggestion explained in detail

2007-08-29 Thread Martin Sander
Hey. I'm glad that somebody read my mail. On Wed, Aug 29, 2007 at 01:06:59AM -0400, Jushan Bai wrote: > I notice that you proposed a solution to the "jump to error" problem. > But I'm a novice about the latexsuite setups and environment variables > etc. I'm using vim78.0 + miktex 2.5 + windows xp

Re: [Vim-latex-devel] Tex_RunLaTeX() does not compile new dvi

2007-11-12 Thread Martin Sander
Do you have a file called "makefile" or "Makefile" in your working directory? If so, do a :let Tex_UseMakefile=0 in vim and try again. See :help Tex_UseMakefile Cheers Martin On Mon, Nov 12, 2007 at 02:29:55PM +0100, Kai Lessmann wrote: > Hello, I'm looking for help with invoking latex from V

Re: [Vim-latex-devel] output of xdvi shows in tex-file

2007-11-16 Thread Martin Sander
Hey. Workarounds: a) use gvim. Usuallally I use terminal-vim all the time, but for LaTeX I prefer gvim because it does not show console output and because I found it easier to set up forward and backward searching. b) $ head .Xdefaults xdvi.hushStdout: true some other useful (for me at

Re: [Vim-latex-devel] text clobbered in vim (but not gvim)

2007-11-18 Thread Martin Sander
Hey, this annoyed me to (a lot). I don't remember that this has always been like this, maybe it has been introduced by vim 7.1. Anyways, my workaround was using gvim, but now you got me motivated to search for a real solution, and I found it: $ tail -2 .vim/after/ftplugin/tex.vim "

Re: [Vim-latex-devel] text clobbered in vim (but not gvim)

2007-11-20 Thread Martin Sander
On Tue, Nov 20, 2007 at 01:29:41PM +, Stephen Wilkinson wrote: > I don't know how to > test for "if not" so I've put the statement in > the "else" part if !has("gui_running") :nnoremap Tex_Compile :call Tex_RunLaTeX()\|redraw! endif by the way, I added another to the end of the line

Re: [Vim-latex-devel] Installation on Ubuntu

2007-12-19 Thread Martin Sander
On Wed, Dec 19, 2007 at 11:55:43AM +0100, Sebastian Menge wrote: > the version is outdated. Current version in > Ubuntu (and probably Debian) is "20060325-3". No it is not, see [1]: Latest version of Latex-Suite: * latexSuite20060325.tar.gz (212.3 Kb; March 25, 2006) > Is there no active pack

[Vim-latex-devel] F9 bibtex completion

2007-12-19 Thread Martin Sander
> I have some trouble with the F9 completition of my bibtex items under Ubuntu > 7.10. > When I write \cite{ and F9 an empty preview window comes up. (My bib file is > setup correctly) > For the \ref{ command it works. > > I also installed the latest version in my .vim folder (removing the ubuntu

[Vim-latex-devel] annoying press-enter-or-command message when inverse searching

2008-01-23 Thread Martin Sander
Hey list. I have spent some time now and it is really annoying. When I do inverse searching from xdvi (which was hard to set up in the first place..), I get this awful annoying "Press ENTER or type command to continue" message most of the time, although there is no long message shown. I

Re: [Vim-latex-devel] Extra double quote within align environments

2008-03-07 Thread Martin Sander
On Fri, Mar 07, 2008 at 05:19:27PM -0600, Rhys Ulerich wrote: > Is anyone else experiencing an extra double quote within align* > environments? E.g., > \begin{align*} > " > \end{align*}<++> > after the environment insertion ends. > > It occurs when hitting F5 and selecting align or alig

Re: [Vim-latex-devel] calling makeindex during compilation

2008-04-10 Thread Martin Sander
If you are familiar with make(1) and Makefiles, I would recommend giving them a try. It should't be to big of a hassle to write one, and latex-suite automatically uses the Makefile if it exists in your working directory. I think your Makefile would look like this (I did not test it, never used no

Re: [Vim-latex-devel] compiling with wrong cross-references

2008-05-28 Thread Martin Sander
Felipe G. Nievinski wrote: >> I was wondering if it wouldn't be a good idea to have the vim-latex >> suite incorporating that? We'd have to take into account portability, too. I don't know if all versions of latex support -file-line-error. Ted Pavlic wrote: > Personally, I think it definitely wou

[Vim-latex-devel] fixing bugs in vim-latex

2008-05-30 Thread Martin Sander
On Sat, May 31, 2008 at 12:20:33AM +0200, Till Maas wrote: > Hi Martin, > > About the bug I asked you to reproduce: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460555 > > I can reproduce it, when I use these settings: > se showcmd" and "se columns=50" It gets stranger by the minute. I rem

Re: [Vim-latex-devel] [ vim-latex-Bugs-1997889 ] `[, `(, `{ shortcuts mess up identation

2008-06-19 Thread Martin Sander
On Thu, Jun 19, 2008 at 02:02:09PM +, SourceForge.net wrote: > Summary: `[,`(,`{ shortcuts mess up identation > > Initial Comment: > this is a matrix i tried to add parentheses or brackets to Thanks for the minimal example... Anyways, just wanted to mention that the bug disappears using :set

Re: [Vim-latex-devel] Compilation

2008-06-19 Thread Martin Sander
On Wed, Jun 18, 2008 at 01:14:10PM -0400, Ted Pavlic wrote: > >>> :map \lz \ll\lv > > By putting that in there, it should get you passed some of the > "Press enter to continue" prompts after compilations. I don't use this > method. It's just a guess. In .vim/after/ftplugin/tex.vim: if !has("gui_