[Vim-latex-devel] irritating interaction between vim-latex, pstricks and errors

[David E. <es...@fa...>]

Dear vim-latex

I'm having the most incredibly annoying interaction between pstricks and
vim-latex. 

Problem: Compiling a file with an error, and \usepackage{pst-all} causes
the current buffer to be closed and a new buffer with the following text
opened:

\ProvidesPackage{multido}[1997/03/25 package wrapper for multido.tex]
\input multido.tex
\endinput

Steps to reproduce: 

Compiling the following file will cause this to occur.

\documentclass[12pt]{article}
\usepackage{pst-all}
\begin{document}
  \begin{center}
    \begin{center}

      Joe
    \end{center}
%comment
\end{document}

This is a very subtle bug both the whitespace line, the extra
\begin{center}, and the %comment are needed to make this happen.

In the past I have noticed that in situations where the file which
compiles cleanly (ie no problem using \ll in vim) but which has an
overfull \hbox has a really nasty behavior.

Introducing an error like the one above will cause the buffer to be
closed and the multido buffer opened. Moreover correcting that error
WILL NOT fix the problem with \ll. The problem persists until the
overfull \hbox is fixed.

I was unable to reproduce that here.

Finally I have had  trouble with errors in general during compile. The
documentation states that: 

...This runs latex on the current file and displays the errors in a
|quickfix-window| below the file being edited. You can then scroll
through the errors and press <enter> to be taken to the location of the
corresponding error. Along with the errors being listed in the quickfix
window, the corresponding log file is also opened in |preview| mode
beneath the quickfix window. It is scrolled automatically to keep in
sync with the error being viewed in the quickfix window. You will be
automatically taken to the location of the first error/warning unless
you set the g:Tex_GotoError variable to 0...

Which has *never* worked for me (I use gVIM exclusively, but I gather it
might work on the console, although the pstricks problem  still there).
At best I had the program jumping to the line of the error, but it
wouldn't tell me what the error was-- which was irritating enough to
cause me to let g:Tex_GotoError=0.

If anyone has any hints or knows something I might be doing wrong I
would really appreciate it. I'm really tempted to throw my fist through
the monitor everytime I have to reopen the file.

Thanks David

A few tidbits that may be of use, let me know if there is anything else
of relevance:

My texrc is:

let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
let g:Tex_FormatDependency_ps = 'dvi,ps'
let g:Tex_DefaultTargetFormat = 'ps'
set grepprg=grep\ -nH\ $*
set sw=2
set iskeyword+=:
let g:Tex_ViewRule_ps = 'ggv'
let g:Tex_FoldedEnvironments = 'pspicture,'
let g:Imap_UsePlaceHolders = 0
let g:Tex_IgnoredWarnings = 0

gvim --version

VIM - Vi IMproved 6.2 (2003 Jun 1, compiled May  9 2004 21:07:16)
Included patches: 1-517
Compiled by escott@localhost
Huge version with GTK2 GUI.  Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+cryptv +cscope +dialog_con_gui +diff +digraphs +dnd -ebcdic +emacs_tags +eval
+ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer
+fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap
 +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession
+modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm
+mouse_netterm +mouse_xterm +multi_byte +multi_lang +netbeans_intg -osfiletype
+path_extra +perl +postscript +printer +python +quickfix +rightleft -ruby
+scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax
+tag_binary +tag_old_static -tag_any_white -tcl +terminfo +termresponse
+textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup
+X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save
   system vimrc file: "/etc/vim/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "/etc/vim/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/X11R6/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include     -O3 -march=athlon-xp -funroll-loops -pipe  -I/usr/X11R6/include  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -I/usr/lib/perl5/5.8.4/i686-linux/CORE  -I/usr/include/python2.3 -pthread
Linking: gcc  -L/usr/X11R6/lib   -rdynamic   -L/usr/local/lib -o gvim   -Wl,--export-dynamic -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0   -lXt -lncurses -lgpm -rdynamic  -L/usr/local/lib /usr/lib/perl5/5.8.4/i686-linux/auto/DynaLoader/DynaLoader.a -L/usr/lib/perl5/5.8.4/i686-linux/CORE -lperl -lutil -lc -L/usr/lib/python2.3/config -lpython2.3 -lpthread -lutil -lm -Xlinker -export-dynamic

I use Gentoo so this is compiled locally, and I have version 2.02 of the teTeX distribution.

-- 
David Wright Escott