vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project

Re: [Vim-latex-devel] jump to error problem (a screen shot is attached)

[Jushan B. <jus...@ny...>]

Hi Franco,

Thanks for the quick reply.  Quickfix recognizes the errors and is able to detect the location of errors, it sounds odd that it cannot deduce the file name that is being compiled?

Jushan


> Jushan,
>  
>  On 8/26/07, Jushan Bai <jus...@ny...> wrote:
>  
>  > Hi Franco,
>  >
>  > Thanks for your willingness to help. Both the file name  and and 
> line number appear to be correct.
>  > A simple screen shot is attached (MS doc file).
>  >
>  > Here is the orginal program, no empty lines at the beginning. On 
> the 4th line "lpha" is undefined,
>  > the Quickfix recognize the error, but no jump.
>  >
>  > \documentclass[12pt]{article}
>  > \begin{document}
>  > This is my first paragraph.
>  > Consider the equation  $\lpha = \beta$, here ``lpha'' is undefined 
> on purpose.
>  >
>  > This is my second paragraph.
>  > \end{document}
>  
>  As I suspected, the filename is not deduced correctly by latex-suite.
>  In the quickfix window you should see the line
>  
>    ivnote.tex|4 error| Undefined control sequence. \lpha  Consider the
>  equation ...
>  
>  but your line is missing "ivnote.tex" at the beginning.
>  
>  I tried your example on my machine, a linux box with vim7, and I have
>  no problem. But I do see this problem sometimes on other files
>  (especially when I am using certain packages). It seems that the
>  latex-suite procedures to detect the errors (including finding the
>  filenames and line numbers) from the latex output isn't satisfactory.
>  
>  I took a look at the code, but was not able to find a way to quickly
>  fix it. The problem is that the latex compilation messages are not
>  consistent across all packages, so the currently defined procedure
>  doesn't always work. I have problems with the xypic package. If the
>  package is loaded and if there is an error in my file, then vim always
>  jumps to the some file that belongs to the xypic package (some .sty
>  file, I think).
>  
>  I'm sending this reply to the list in case someone has any
>  suggestions. But the list seems to be very quite these days.
>  
>  Take care,
>  Franco
>  
>  --
>  

Re: [Vim-latex-devel] jump to error problem (a screen shot is attached)

[Franco S. <sa...@gm...>]

Jushan,

On 8/26/07, Jushan Bai <jus...@ny...> wrote:

> Hi Franco,
>
> Thanks for your willingness to help. Both the file name  and and line number appear to be correct.
> A simple screen shot is attached (MS doc file).
>
> Here is the orginal program, no empty lines at the beginning. On the 4th line "lpha" is undefined,
> the Quickfix recognize the error, but no jump.
>
> \documentclass[12pt]{article}
> \begin{document}
> This is my first paragraph.
> Consider the equation  $\lpha = \beta$, here ``lpha'' is undefined on purpose.
>
> This is my second paragraph.
> \end{document}

As I suspected, the filename is not deduced correctly by latex-suite.
In the quickfix window you should see the line

  ivnote.tex|4 error| Undefined control sequence. \lpha  Consider the
equation ...

but your line is missing "ivnote.tex" at the beginning.

I tried your example on my machine, a linux box with vim7, and I have
no problem. But I do see this problem sometimes on other files
(especially when I am using certain packages). It seems that the
latex-suite procedures to detect the errors (including finding the
filenames and line numbers) from the latex output isn't satisfactory.

I took a look at the code, but was not able to find a way to quickly
fix it. The problem is that the latex compilation messages are not
consistent across all packages, so the currently defined procedure
doesn't always work. I have problems with the xypic package. If the
package is loaded and if there is an error in my file, then vim always
jumps to the some file that belongs to the xypic package (some .sty
file, I think).

I'm sending this reply to the list in case someone has any
suggestions. But the list seems to be very quite these days.

Take care,
Franco

--

Re: [Vim-latex-devel] jump to error problem

[Franco S. <sa...@gm...>]

On 8/25/07, ahmet nurlu <ahm...@ya...> wrote:

> I wonder anyboyd has fixed "jump to error" problem in
> multi-file projects.

I think I have experienced what you are talking about, but to be sure,
can you explain the problem in more detail?

Franco

--

[Vim-latex-devel] jump to error problem

[ahmet n. <ahm...@ya...>]

I am an addicted user of vim-latex. I can't think any
other choice other than it. I have even tried
emacs+latex macros but I am not satisfied at all(due
to complex keybord keys to complete your job.) I am
much faster with vim-latex.

I wonder anyboyd has fixed "jump to error" problem in
multi-file projects. 

thanks,
Ahmet


       
____________________________________________________________________________________
Sick sense of humor? Visit Yahoo! TV's 
Comedy with an Edge to see what's on, when. 
http://tv.yahoo.com/collections/222

[Vim-latex-devel] Latex Suite utf8 problem (LookupCharacter error)

[Stephen W. <sw...@gm...>]

Hello All,

I've encountered a problem when using encoding=utf-8 with filetype=tex. I
use Vim 7.1 and I've upgraded to the latest LatexSuite (March 25, 2006). In
insert mode, if I type \ (backslash) I get the following error message:

Error detected while processing function <SNR>28_LookupCharacter:
line 12:
E54: unmatched \(

I can only reproduce the problem when the filetype is tex (so I presume the
problem is in vim-latex plugins) AND encoding is utf-8.

If encoding=latin-1 and fileencoding=utf-8, I encounter no problem (the file
is converted to uft-8 on writing). But on my home machine I normally have
encoding set to utf-8 (same as locale)... so I can get around this by adding
the comment line at the end of the file:
% vim:encoding=latin-1:fileencoding=utf-8:

I searched the VIM mailing list for a similar problem: in the thread
entitled " new weirdness with vim-latex" started on 23/03/2006
(http://marc.info/?l=vim&m=114307450126576&w=2
) it was said the problem is with plugin/imaps.vim . I had a look at line 12
of the function LookupCharacter in that file, but I must admit I don't
understand it (despite the comments) and I can't tell if there is a problem.

For the moment, I get around this with the comment line at the end of my
latex files, but I was wondering if there's a more permanent and better
solution, and if anyone else has encountered this problem.

Thanks,
Steve

[Vim-latex-devel] MacVim and MORE forward searches

[Ted P. <te...@te...>]

I've modified the compiler.vim file to (additionally) support viewing 
and forward searching in Skim, TeXniscope, PDFView, and any UNIX viewer 
that has the command-line syntax:

viewer TARGET_FILE LINE_NUMBER SOURCE_FILE

Because of the existence of PDFSync, I have removed the restriction that 
forward searches require a DVI target.


See:

http://phaseportrait.blogspot.com/2007/07/vim-latex-modification-forward.html

for the compiler.vim patch file and instructions. This patch does work 
with multiple file projects as long as the main file has been marked by 
a dummy file with the same root name ending in the extension ".latexmain".


The patch, alone, is at:

http://links.tedpavlic.com/patch/VIM-LaTeX-osx-inverse-search-compiler.patch

Applying:

patch -p0 < VIM-LaTeX-osx-inverse-search-compiler.patch

in the ~/.vim/ftplugin/latex-suite/ directory should work.



--Ted

-- 
Ted Pavlic <te...@te...>

[Vim-latex-devel] MacVim and inverse searches (and pdfsync)

[Ted P. <te...@te...>]

The VIM-LaTeX quickstart guide has information on setting up inverse 
searches for DVI's in Windows at:

http://vim-latex.sourceforge.net/documentation/latex-suite-quickstart.html#lsq-quick-inverse-searching

A couple remarks:


1.) This probably should be updated. After all, you can use pdfsync:

http://itexmac.sourceforge.net/pdfsync.html

to get the same features for PDF files.


2.) I have posted information on how to do this in OS X as well. See:

http://phaseportrait.blogspot.com/2007/07/pdfsync-inverse-searches-on-vim-for-os.html

The script uses AppleScript to manually key in the entries required to 
reload a file at a particular line. I also give information about how to 
use this script with Skim, a powerful new PDF viewer in OS X (that 
supports PDFSync).


-- 
Ted Pavlic <te...@te...>

[Vim-latex-devel] F9 completion

[Peter M. <Pet...@gm...>]

Hi,

I have some trouble with the F9 completion under WinXP.

If I type \ref <F9>, I get two addtional buffers - liked descripted in 
the manual.
The shown content seems to be valid, too.
I can scroll down the lines containing references and view the content 
in the third buffer.

The problem is now the insertion of the reference.
When I press <ENTER> with the selected line, I cursor always jumps to 
the selected reference
in the code. It doesn't insert the value in \ref{}.

How can I solve this issue?

Thanks
   Peter

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

[Martin S. <fo...@un...>]

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.g. "beamer".
Then put something like this in your ~/.vim/after/ftplugin/tex.vim

if ( system("echo -n `cat *.tex.latexmain`") =~ 'beamer' )
	unlet g:Tex_FormatDependency_pdf
	let g:Tex_CompileRule_pdf = 'pdflatex -interaction=nonstopmode $*'
endif

This is very fragile (you should only have one latexmain file, it should
only contain this one word, it has to be in the directory where you
started vim, etc etc), but it works for me.
I know there are certainly are a lot of much more elegant ways to parse
a file though..


Martin
P.S.: why don't you use dvi for all you previewing and ONE call of
dvips/ pstopdf in the end when you want to print your doc?

On Sun, Jun 17, 2007 at 10:53:48AM +0800, anhnmncb wrote:
> hello list,
>         I prefer the way "dvi->dvips->pdf" to generate my ordinary document, I find in this way the size of pdf i
> s small. But latex-suite compiles pdf using pdflatex by default, So I have to set:
>         let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
>         let g:Tex_DefaultTargetFormat = 'pdf'
>         let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'
>         
>         When I prepare my slides using  beamer class, I prefer pdflatex to latex because I find the graphics qual
> ity is higher than dvips. As you know, I have set the compilerule for pdf, so I can't generate pdf using pdflatex
>  conventionally. I want to know how to resolve such problem?

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

[anhnmncb <anh...@gm...>]

hello list,
        I prefer the way "dvi->dvips->pdf" to generate my ordinary document, I find in this way the size of pdf i
s small. But latex-suite compiles pdf using pdflatex by default, So I have to set:
        let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
        let g:Tex_DefaultTargetFormat = 'pdf'
        let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'
        
        When I prepare my slides using  beamer class, I prefer pdflatex to latex because I find the graphics qual
ity is higher than dvips. As you know, I have set the compilerule for pdf, so I can't generate pdf using pdflatex
 conventionally. I want to know how to resolve such problem?
        Sorry for my really poor English, but I don't know if I have expressed myself clearly.
        Thanks for any advise.
        
Best regards,
-- 
	an...@gm...

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

[Martin S. <fo...@un...>]

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=nonstopmode 
-file-line-error $*'

(the difference to the default is the -file-line-error)
this gives output like this:

...
./foo.tex:8: Undefined control sequence.
l.8   \foo
...

instead of
! Undefined control sequence.
l.8 \foo

So one does not need all that pushing and popping 
filenames at all, just another statement in 
compiler/tex.vim to match the new format:

--- /usr/share/vim/addons/compiler/tex.vim      2007-06-12 
15:32:12.000000000 +0200
+++ tex.vim     2007-06-12 15:44:27.000000000 +0200
@@ -202,6 +202,7 @@
  
         setlocal efm+=%E!\ LaTeX\ %trror:\ %m
         setlocal efm+=%E!\ %m
+       setlocal efm+=%E%f:%l:\ %m
  
         setlocal efm+=%+WLaTeX\ %.%#Warning:\ %.%#line\ 
%l%.%#
         setlocal efm+=%+W%.%#\ at\ lines\ %l--%*\\d


I guess one can get rid of some other rules that are not 
needed anymore.
This could be a good simplification, but I don't know how 
portable it is (maybe not every "latex" has 
-file-line-error ..).

btw. I am using version 20060325-1 on ubuntu edgy eft.

Cheers Martin

Re: [Vim-latex-devel] vim vs gvim Menus on Empty .tex File

[Donnie P. <don...@ma...>]

Ahh . . . that did the trick.  Thanks.
-- 
Donnie Pennington

---On Mon, Jun 04, 2007 at 10:54:42PM -0400, Aditya Mahajan wrote---
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 documented here:
>
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377453
>
>This problem occurs because vim sees the empty file's filetype as
>'plaintex' rather than 'tex'.

This was changed recently (around Vim 7). See

See :he ft-tex-plugin

If you only use latex, add the following to your .vimrc

 let g:tex_flavor = "latex"

Probably needs to be added to latex-suite's FAQ.

Aditya

Re: [Vim-latex-devel] vim vs gvim Menus on Empty .tex File

[Aditya M. <ad...@um...>]

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 documented here:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377453
>
> This problem occurs because vim sees the empty file's filetype as
> 'plaintex' rather than 'tex'.

This was changed recently (around Vim 7). See

See :he ft-tex-plugin

If you only use latex, add the following to your .vimrc

  let g:tex_flavor = "latex"

Probably needs to be added to latex-suite's FAQ.

Aditya

[Vim-latex-devel] vim vs gvim Menus on Empty .tex File

[Donnie P. <don...@ma...>]

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 documented here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377453

This problem occurs because vim sees the empty file's filetype as
'plaintex' rather than 'tex'.  You can prove this with the results of
vim's ':set ft' command.  It will come back 'plaintex' rather than
'tex'.  Therefore, another solution is to use vim's ':set ft=tex'
command on the new, empty file to wake up latexsuite. See:

http://lists.alioth.debian.org/pipermail/pkg-vim-maintainers/2006-August/003267.htm 

-- 
Donnie Pennington

[Vim-latex-devel] [vim-latex - Help] Checking for vim-latex

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=4341707
By: yangzhang

Hi, I like to use the same .vimrc in multiple environments, but if I have something
like "au VimEnter * call IMAP('`o', '\overset{<++>}{<++>}<++>', 'tex')", I will
get errors when running vim without vim-latex installed. How do I condition
on vim-latex's presence? Thanks in advance.

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=173627

[Vim-latex-devel] Weird behavior with Makefiles

[Marius K. <kle...@gm...>]

I have encountered a weird behavior of vim-latex when there exists a
Makefile in the current directory. It appears that upon hitting '\ll',
Vim calls 'make pdf'. However, in general there is no such target in
my Makefiles.

On the other hand, the ':make' command shows a weird behavior. If I
open a file using 'vim test.tex', 'set makeprg?' returns
  makeprg=pdflatex -interaction=nonstopmode $*
However, when I enter ':make', it seems that the $* in the above
expression is empty, since I just get a latex prompt:
  This is pdfTeX, Version 3.141592-1.40.3 (Web2C 7.5.6)
  **

I would much prefer ':make' have its default meaning, and '\ll' simply
compiling the tex file using pdflatex. How can I achieve this?

I am using latex-suite with Vim version 7.0 on Mac OS X 10.4.9.

Marius

-- 
Marius Kleiner
kl...@gm...

[Vim-latex-devel] :mksession

[Sebastian <seb...@un...>]

Hi all

I have a problem with :mksession. I always get this error when reopening a
session file with vim -S

Fehler beim Ausführen von "/home/menge/.vim/ftplugin/latex-suite/folding.vim":
Zeile   11:
"settings_preamble.tex" 47L, 721C
Fehler beim Ausführen von "/home/menge/Diss/sketches/sketches.vim":
Zeile  739:
"settings_preamble.tex" 47L, 721C
Zeile  885:
E165: Kann nicht über die letzte Datei hinausgehen

Could someone test that please? im using vim7.0 but i dont know the version of
latex-suite. if i remember correctly, i installed it by hand last ysear ...

Thanks, Sebastian.

[Vim-latex-devel] Patch: avoid initial whitespace in bibtex key completion

[Cristian R. <cr...@li...>]

Hi, I've noticed that if your *.bib files are formatted in the following way:

@book{    key,
          ...
}

(i.e. with some spaces/tabs preceding the key)

the F9 automatic \cite completion will insert the unwanted initial whitespace.

The attached patch (against the current vimfiles/ftplugin/latex-suite/texviewer.vim
in svn) will fix this problem (i.e. no spaces/tabs will be inserted).

(usual disclaimer: it works for me, YMMV...)

Cri

-- 
GPG/PGP Key-Id 0x943A5F0E      -    http://www.linux.it/~cri/cri.asc
Free software, free society    -    http://www.fsfeurope.org

Re: [Vim-latex-devel] xy-pic

[Sebastian M. <seb...@un...>]

Thanks for the answers.

Hooman, you are right, math-mode is needed to fix syntax-highlighting. I
have developed two solutions:

1) in the syntax file tex.vim one can define a new "texMathZoneXY" (i
simply adapted texMathZoneZ) (~line 340). And add a "texMathZoneXY" next
to each other occurence of texMathZoneZ.

2) A collegue of mine suggested to put these diagrams in an
equation-environment (to get eqn-numbers and labels). That also fixes it
without touching the syntax.

regards, Sebastian.




Am Samstag, den 05.05.2007, 15:06 -0400 schrieb coupled cores:
> I have noticed this behaviour. When you use raw TeX code inside a
> LaTeX document, the _(underscore) and ^ and @ are highlighted with a
> red background. I think the syntax highlighting of the LaTeX files
> expects these special characters to appear only inside math
> environment such as $$ or \begin{equation} \end{equation}.
> 
> All being said, I don't have any solution for that. I just let them be
> with the red backgrounds.
> 
> Peace,
> Hooman
> 
> On 5/3/07, Sebastian Menge <seb...@un...> wrote:
> > Hi
> >
> > Im using the package xy-pic for drawing some diagrams. The TeX-code
> > looks like this:
> >
> > \centerline{
> > \xymatrix{
> >   E \ar@/^/[r]^s \ar@/_/[r]_t & V
> >   } }
> >
> > or
> >
> > \centerline{
> > \xymatrix{
> >   & S \times I \ar@/_/[dl]_t \ar[dl]_{\pi_1} \ar[d]^{\pi_2} \ar[dr]^o& \
> > \
> >   S  & I & O
> >   } }
> >
> >
> > Syntax highlighting gets wrong for this: I get a lot of ugly characters
> > with red background (looks like errorenous code). This occurs at "@" and
> > "_".
> >
> > Oh, while i write a get an idea. Inside \xymatrix  is math-text.
> > Probably latex-suite does not recognize this and treats it as standard
> > text !?
> >
> > How can i change that?
> >
> > Sebastian.
> >
> >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Vim-latex-devel mailing list
> > Vim...@li...
> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> >

Re: [Vim-latex-devel] xy-pic

[Franco S. <sa...@gm...>]

On 5/3/07, Sebastian Menge <seb...@un...> wrote:

> Oh, while i write a get an idea. Inside \xymatrix  is math-text.
> Probably latex-suite does not recognize this and treats it as standard
> text !?
>
> How can i change that?

I haven't tried this, but maybe you can create a new environment
called xymath and then use that environment in place of \xymatrix{}.

\begin{xymath}
 % xymatrix code goes here.
\end{xymath}

Perhaps this would work?

Franco

--

Re: [Vim-latex-devel] xy-pic

[coupled c. <cou...@gm...>]

Dear Sebastian,

I have noticed this behaviour. When you use raw TeX code inside a
LaTeX document, the _(underscore) and ^ and @ are highlighted with a
red background. I think the syntax highlighting of the LaTeX files
expects these special characters to appear only inside math
environment such as $$ or \begin{equation} \end{equation}.

All being said, I don't have any solution for that. I just let them be
with the red backgrounds.

Peace,
Hooman

On 5/3/07, Sebastian Menge <seb...@un...> wrote:
> Hi
>
> Im using the package xy-pic for drawing some diagrams. The TeX-code
> looks like this:
>
> \centerline{
> \xymatrix{
>   E \ar@/^/[r]^s \ar@/_/[r]_t & V
>   } }
>
> or
>
> \centerline{
> \xymatrix{
>   & S \times I \ar@/_/[dl]_t \ar[dl]_{\pi_1} \ar[d]^{\pi_2} \ar[dr]^o& \
> \
>   S  & I & O
>   } }
>
>
> Syntax highlighting gets wrong for this: I get a lot of ugly characters
> with red background (looks like errorenous code). This occurs at "@" and
> "_".
>
> Oh, while i write a get an idea. Inside \xymatrix  is math-text.
> Probably latex-suite does not recognize this and treats it as standard
> text !?
>
> How can i change that?
>
> Sebastian.
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] xy-pic

[Sebastian M. <seb...@un...>]

Hi

Im using the package xy-pic for drawing some diagrams. The TeX-code
looks like this:

\centerline{
\xymatrix{
  E \ar@/^/[r]^s \ar@/_/[r]_t & V
  } }

or

\centerline{
\xymatrix{
  & S \times I \ar@/_/[dl]_t \ar[dl]_{\pi_1} \ar[d]^{\pi_2} \ar[dr]^o& \
\
  S  & I & O
  } }


Syntax highlighting gets wrong for this: I get a lot of ugly characters
with red background (looks like errorenous code). This occurs at "@" and
"_".

Oh, while i write a get an idea. Inside \xymatrix  is math-text.
Probably latex-suite does not recognize this and treats it as standard
text !?

How can i change that?

Sebastian.

[Vim-latex-devel] Bug in GotoError

[Franco S. <sa...@gm...>]

Hello,

I started using latex-suite a few days ago and I am quite pleased with
the software. But I have come across some very annoying behaviour. I
am using vim-7.0 on an Ubuntu Feisty Fawn system.

I am working on a "project", so I have multiple input files I am
editing. I have an incorrect \ref{blah} in the file I am editing. When
I hit \ll, the following things happen:

 expected: the quickfix window opens;
 slightly unexpected: no log file window opens;
 extremely unexpected: the file I am editing is replaced with my
project.bbl file!

This is a bug: the error is not contained in the bibliography file.
When I hit enter in the quickfix window, it complains that it cannot
find the error -- which is no surprise since the file containing the
error has been closed and replaced with some other file.

I have been closing the windows and reopening the file that I was
editing. Quite annoying. Is there a command that will return me to the
file and spot that I was editing?

Here is another bug: I set Tex_GotoError to 0, but this doesn't help.
Same behaviour.

Note: I haven't tried, but it seems that this might happen even with a
non-"project" as long as you have an external bibtex file.

Any suggestions?
Franco

--

Re: [Vim-latex-devel] Does vim-latex show a general problem of OS?

[Simon P. <pre...@gm...>]

Rather than ruminate on the woes of open source software, it would be much
more sensible to describe to the list the details of your problems - e.g.
your operating system, what error messages you get, etc.

Then hopefully somebody will be able to help.


On 3/27/07, Heiko Schr=F6der <hei...@vo...> wrote:
>
> Dear list,
>
> vim and LaTeX are genius inventions not only because of their great
> functionality, but also because of their splendid documentation. It is
> like a
> great forest where it is *not* possible to hide any non-documented eggs.
> What about the latex-vim suite?  :-|
>
> It is said that the suite runs with vim6+. Obviously it is meant vim6.x,
> not
> version 7.x. I did *exactly* what is said in the installation instruction=
s
> on
> different machines -- with vim7.0. Exactly with no exception. Nothing
> happens.
>
> I  know and I appreciate it very much that the suite is work done by free
> will. Indeed! And that the members of this list help by their free will.
> That
> is great, but it does not solve IMHO the general problem. It is clear tha=
t
> a
> software has its development stage. But if something is called stable, it
> *must* have a good installation instruction (more important than a user
> manual). Otherwise it IS in development.
>
> Especially in this case if the software  is aimed to *help* users. Which
> users? Those who are lucky to have requirement no. 6.1.1-2 (and not
> 6.1.1-2.1
> where the usage *sometimes* fails)? Sureley not those who celebrate Easte=
r
> again, searching for the non documented eggs hidden *between* the lines o=
f
> the instructions, meaning perhaps that 7.0 is not 6.+ but obviously 6.++.
> And -- if you really think, think right -- we *did* say 6.+ ONLY, nothing
> more     ;-).
>
> And: *See those lucky people. Can't you imagine, that you DID a mistake?
> They
> can run it, so everyone *could* run it, if one only uses its brain -- Yes=
,
> you have to think, but think right.  Find out WHAT is meant, not what is
> NOT
> meant or what we mean that it should be clear that it IS not meant.*  And
> if
> you do not succeed read the FAQ (Feigned Annoying Questions -- which have
> never been asked) ;-)
>
> Please apologize for coming a bit too steep out of the hedge. But
> OpenSource
> is by a too great amount of people still  regarded as *software for
> specialists* -- and that shows IMHO that there is something wrong; but no=
t
> about OpenSource! Nobody cares about the free willing work done by the
> user
> (and it *is* sureley not important). Software *cannot* be free of bugs.
> That
> is clear.But a suite which sometimes works and sometimes with not hints
> what
> could be wrong is use-less (in the exact meaning).
>
> Best regards
> Heiko Schroeder
>
> --
> Heiko Schroeder
> Praha, Ceska Republica
> http://home.foni.net/~heikos
> http://www.od.shuttle.de/evb-1
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] Does vim-latex show a general problem of OS?

[Christian E. <bla...@gm...>]

* Heiko Schröder on Tuesday, March 27, 2007 at 21:03:01 +0200:
> It is said that the suite runs with vim6+. Obviously it is meant vim6.x, not 
> version 7.x. I did *exactly* what is said in the installation instructions on 
> different machines -- with vim7.0. Exactly with no exception. Nothing 
> happens. 

Hm, I, as simple user, can't contribute here, as latex-suite just
works for me with Vim7+ -- as it did before the transition.

I understand your frustration, but I didn't read about anyone
attacking you for being stupid on this list. Nor did I see asking
a question before, for that matter.

The only way I found with OS in this situation is to dig out more
debugging data, and hope/pray that someone finds the mistake ;)

Otherwise you're always free to use eg. Emacs and Auctex ;)

c
-- 
Vim plugin to paste current GNU Screen buffer in (almost) any mode:
<http://www.vim.org/scripts/script.php?script_id=1512>