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

Re: [Vim-latex-devel] environments

[Javier R. <jer...@gm...>]

> Which files should I modify to get the desired behaviour (especially having
> the placeholder below the environment name) ?
I didn't liked the default expansion for the figure environment, so I 
redefined it.

create (or modify) the file ~/.vim/ftplugin/tex.vim, and put a line (don't 
split it like my email client does) like this on it

let 
Tex_Env_{'figure'}="\\begin{figure[htbp]\\centering\<CR>\\includegraphics[width=<++>]
{<++>}\<CR>\\caption{<+caption+>}\\label{fig:<+label+>}\<CR>\\end{figure}\<CR><++>"

the stuff between double quotes is the way you'll redefine the environment, in 
this case figure, in yours, equation. Don't forget the scape backslash. You 
can define too new environments this way, and get the expansion with the <F5> 
key

All this I've explained is in the docs of vim-latex, although, in my opinion, 
a bit not so well presented, because you sort of know what to write but don't 
where to put it. Read the docs,

Greets
-- 
Javier

[Vim-latex-devel] environments

[Baris E. <be...@an...>]

Dear All,

I have a (simple) question about inserting environments using shortcuts such
as EEQ, EEA, and such. When I use EEQ the following is inserted:

\begin{equation}

            

            \label{<++>}

\end{equation}<++>

 

the cursor being between \begin{equation} and \label{.}.  However I dont
want the \label{<++>}  and also I want the last placeholders below the
\end{equation} line.

Which files should I modify to get the desired behaviour (especially having
the placeholder below the environment name) ?

 

Thanks

 

Baris

[Vim-latex-devel] Another completion issue

[Shawn Y. <spa...@gm...>]

Hello,

    It appears that I am having similar problems to those of Dan Pemstein:

                From: Dan Pemstein <dan@lc...>
                Some issues with completion
                2005-11-20 20:18

I also use tcsh, but use Fedora Core 2,3, and 4 on various machines.=20
I have tried both fixes mentioned in the above cited email, and found
that the both fix the problem equally well.  That is, without the
fixes if I type \citet{<F9>  the screen flashes, all my BibTeX files
are added to the buffer list, but nothing else changes in the file or
on the screen.  With the double quotes mentioned by Dan, or setting
'shell' to bash in my vimrc if I type \citet{<F9> I get what I had
been getting a couple of years ago.  Three windows, with one of them
showing a list of keywords and another showing the context of the
highlighted keyword!  I think this is the expected behavior.  Great,
but, if I type \citet{foo<F9>, I get the same results as before, that
is a screen flash and then the bibtex files added to the buffer list,
but nothing else.  Very much unlike Dan, I don't have any idea how to
proceed.  What kind of information would be relavent?

Also, as with Dan, I want to say thanks for the effort you've put into
this great tool!

Shawn Young

Re: [Vim-latex-devel] Error reporting problem with dependency chain

[Jason K. H. <jho...@ma...>]

Srinath,

I was using 1.5. I checked out the CVS version and took a look at the
code and this problem has been fixed. I am now using the CVS version and
all seems well.

Thanks for your response.

Jason


Srinath Avadhanula wrote:

>Hi,
>
>On 12/12/05, Jason K. Howlett <jho...@ma...> wrote:
>  
>
>>I observed the following problem with latex suite. When compiling with a
>>dependency chain, say (dvi, ps) for example, if an error occurs in the
>>dvi compile, it is not correctly reported. What happens is that the loop
>>in Run_Latex continues to call Tex_CompileLatex or
>>Tex_CompileMultipleTimes even after a previous error has occurred. By
>>    
>>
>
>Thanks for bringing this to my attention... I am travelling right now
>and will be able to get to this in a week or later. In the meanwhile,
>are you using the latest developement release? I remember fixing
>something like this a while ago. version 1.5 is really out-dated. (I
>need to do something about the web-page).
>
>Srinath
>
>  
>

-- 
Jason K. Howlett
U.S. Army Aeroflightdynamics Directorate
NASA Ames Research Center       Phone:  650-604-5374
Mail Stop 243-11                Fax:    650-604-0181
Moffett Field, CA 94035-1000    mailto: jho...@ma...

Re: [Vim-latex-devel] Error reporting problem with dependency chain

[Srinath A. <sri...@gm...>]

Hi,

On 12/12/05, Jason K. Howlett <jho...@ma...> wrote:
> I observed the following problem with latex suite. When compiling with a
> dependency chain, say (dvi, ps) for example, if an error occurs in the
> dvi compile, it is not correctly reported. What happens is that the loop
> in Run_Latex continues to call Tex_CompileLatex or
> Tex_CompileMultipleTimes even after a previous error has occurred. By

Thanks for bringing this to my attention... I am travelling right now
and will be able to get to this in a week or later. In the meanwhile,
are you using the latest developement release? I remember fixing
something like this a while ago. version 1.5 is really out-dated. (I
need to do something about the web-page).

Srinath

[Vim-latex-devel] Error reporting problem with dependency chain

[Jason K. H. <jho...@ma...>]

I observed the following problem with latex suite. When compiling with a
dependency chain, say (dvi, ps) for example, if an error occurs in the
dvi compile, it is not correctly reported. What happens is that the loop
in Run_Latex continues to call Tex_CompileLatex or
Tex_CompileMultipleTimes even after a previous error has occurred. By
the time Tex_SetupErrorWindow is called, the previous :cwindow errors
have been replaced (erased) by the latest :make command. One possible
fix to this problem is attached. Tex_SetupErrorWindow was modified to
return a true value if an error is detected in :cwindow.
Tex_SetupErrorWindow is also called after every iteration of the
dependency chain loop. If an error is detected, then a flag is set which
prevents future calls to the Compile functions, and thus preserves the
:cwindow information. Since bailing out of the dependency chain
while-loop prematurely will leave s:target having the incorrect value,
the loop iteration continues through the dependency list, but with no
calls to the Compile functions. Perhaps there is a more elegant way of
doing all this, by knowledge of vim programming is limited. Hope it helps.
 

-- 
Jason K. Howlett
U.S. Army Aeroflightdynamics Directorate
NASA Ames Research Center       Phone:  650-604-5374
Mail Stop 243-11                Fax:    650-604-0181
Moffett Field, CA 94035-1000    mailto: jho...@ma...

[Vim-latex-devel] vimspell + latex-suite

[Hugh A. <hug...@ya...>]

The syntax highlighting of these two packages aren't playing together 
very well.  Spelling errors within the TeX document are unrecognized 
without some modification.

I've hacked vimspell's SpellError rule in after/syntax/tex.vim so that,
	syn match texStatement	"\\[a-zA-Z@]\+" contains=SpellErrors
But it's a bit ghetto.

Is there complete solution out there?  A better behaved spelling 
package?  Or some blindingly obvious solution that I've missed in a fit 
of abject stupidity?

Thanks much.

Re: [Vim-latex-devel] url package syntax error

[Gabriel F. <gs...@pa...>]

On Thu, Dec 08, 2005 at 02:59:22PM -0800, Srinath Avadhanula wrote:
> The latest dev version on the web-site should have this fix.

Thanks for the response and the temp fix--certainly better than
nothing at all.


> In the long term, it would be nice to include them without the
> bugginess. 

I'll look into it more when I get a chance and see if I can help.

Re: [Vim-latex-devel] url package syntax error

[Srinath A. <sri...@gm...>]

Hi,

On 12/6/05, Gabriel Farrell <gs...@pa...> wrote:
> I dug around in the ftplugin files.  The problem is, say I have
> \usepackage{url} in the preamble and somewhere in the article a
> paragraph like so:
>
>         The Library of Congess Thomas site (\url{http://thomas.loc.gov/})
>         is a good source of information from the federal government.
>
> For some reason, the bracket immediately following \url isn't noticed
> by the syntax highlighting, so everything after is highlighted

This was caused by a couple of faulty syntax definitions in the
packages/url file which gets sourced once when you insert the
\usepackage{url} in the preamble using the <F5> command.  For now, I
just commented out the syntax commands. The latest dev version on the
web-site should have this fix.

 In the long term, it would be nice to include them without the
bugginess. A general question to those who are good with syntax stuff:

How does one go about putting :syn commands in a file (which gets
sourced only once) so that the commands are invoked whenever the
syntax is loaded. I was thinking there might be some nice autocommand
which we can catch, but I have had no luck so far.

Thanks,
Srinath

[Vim-latex-devel] url package syntax error

[Gabriel F. <gs...@pa...>]

Greetings,

I just installed latex-suite on my Debian box, running Vim 6.3.86, and
it's caused an error in syntax highlighting that I can't solve, though
I dug around in the ftplugin files.  The problem is, say I have
\usepackage{url} in the preamble and somewhere in the article a
paragraph like so:

	The Library of Congess Thomas site (\url{http://thomas.loc.gov/})
	is a good source of information from the federal government.

For some reason, the bracket immediately following \url isn't noticed
by the syntax highlighting, so everything after is highlighted
(purple, on my screen).  This continues until the end of the document,
or until another open bracket "{" is reached.  In other words, it
seriously screws with the highlighting.  Just to make sure it was
latex-suite causing the problem, I apt-get removed it, and the
highlighting was fine again.  I also tried to reproduce the error with
other packages and other latex commands, but no luck, so I think it's
specifically the url file in the latex-suite ftplugin directory.

gsf

Re: [Vim-latex-devel] latexsuite with cygwin

[Srinath A. <sri...@gm...>]

Hi,
On 12/2/05, Ben Schuchard <ben...@gm...> wrote:
>  The web page below says that "Latex-suite on windows has been tested wit=
h
> cygwin".  I currently have cygwin installed but couldn't find a cygwin
> package for latexsuite.  Could someone point me in the right direction fo=
r
> setting up latexsuite for cygwin?

There is no cygwin package for latex-suite. By "...testing with
cygwin..." I meant that latex-suite operates well with the cygwin
tools such as grep, cat etc which latex-suite occassionally calls upon
(and needs). Therefore, if you install cygwin, install latex-suite in
the standard manner (i.e unzipping the latest (development) version
into your ~/vimfiles directory) as detailed in

http://vim-latex.sourceforge.net/index.php?subject=3Ddownload&title=3DDownl=
oad

In addition, you could set

set shell=3Dbash

which will be an added advantage of using cygwin.

HTH
Srinath

[Vim-latex-devel] latexsuite with cygwin

[Ben S. <ben...@gm...>]

Hello,

I am new to vim-latexsuite and have a couple of questions...

The web page below says that "Latex-suite on windows has been tested with
cygwin".  I currently have cygwin installed but couldn't find a cygwin
package for latexsuite.  Could someone point me in the right direction for
setting up latexsuite for cygwin?
Thanks,

Ben

http://vim-latex.sourceforge.net/index.php?subject=3Dfaq&title=3DFAQ

Re: [Vim-latex-devel] Problem with environment insert

[Javier R. <jer...@gm...>]

El Dom 27 Nov 2005 02:10, escribi=F3:
> I tried to install gvim6.3 from source. But it still does wrong.
> Can it be a system problem or one of shared libaries ?
> I just did basic compilation: ./configure && make && make install.
> Could you send me your compile option ?

this options are for the vim 6.4 that doesn't work with the compile multipl=
e=20
times function:

:version
VIM - Vi IMproved 6.4 (2005 Oct 15, compiled Nov  3 2005 15:27:29)
Compilado por jerojasro@telemedic238
Versi=F3n =ABenorme=BB con GUI GTK2.  Aspectos incluidos (+) o no (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cinden=
t=20
+clientserver +clipboard +cmdline_compl
+cmdline_hist +cmdline_info +comments +cryptv +cscope +dialog_con_gui +diff=
=20
+digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra
 +extra_search +farsi +file_in_path +find_in_path +folding -footer +fork()=
=20
+gettext -hangul_input +iconv +insert_expand
+jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +local=
map=20
+menu +mksession +modify_fname +mouse
+mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_xter=
m=20
+multi_byte +multi_lang +netbeans_intg
=2Dosfiletype +path_extra -perl +postscript +printer -python +quickfix=20
+rightleft -ruby +scrollbind +signs +smartindent -sniff
+statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_whit=
e=20
=2Dtcl +terminfo +termresponse +textobjects +title
+toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +vimin=
fo=20
+vreplace +wildignore +wildmenu +windows
+writebackup +X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save
     fichero =ABvimrc=BB del sistema: "$VIM/vimrc"
     fichero =ABvimrc=BB del usuario: "$HOME/.vimrc"
      fichero =ABexrc=BB del usuario: "$HOME/.exrc"
    fichero =ABgvimrc=BB del sistema: "$VIM/gvimrc"
    fichero =ABgvimrc=BB del usuario: "$HOME/.gvimrc"
     fichero de men=FA del sistema: "$VIMRUNTIME/menu.vim"
            localizaci=F3n de $VIM: "/usr/local/share/vim"
Compilaci=F3n: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK =20
=2DI/opt/gnome/include/gtk-2.0 -I/opt/gnome/lib/gtk-2.0/include -
I/opt/gnome/include/atk-1.0 -I/opt/gnome/include/pango-1.0=20
=2DI/usr/X11R6/include -I/usr/include/freetype2 -I/opt/gnome/include/g
lib-2.0 -I/opt/gnome/lib/glib-2.0/include     -g -O2  -I/usr/X11R6/include
Enlazado: gcc  -L/usr/X11R6/lib   -L/usr/local/lib -o vim  =20
=2DWl,--export-dynamic -L/opt/gnome/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -
latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0=20
=2Dlgobject-2.0 -lgmodule-2.0 -lglib-2.0   -lXt -lncurses -lgpm



this are the options for the vim 6.3 that I've compiled, and that works fine
:version
VIM - Vi IMproved 6.3 (2004 June 7, compiled Oct  8 2005 15:18:27)
Compiled by julot@abu
Normal version with GTK2 GUI.  Features included (+) or not (-):
=2Darabic +autocmd +balloon_eval +browse +builtin_terms +byte_offset +cinde=
nt=20
+clientserver +clipboard +cmdline_compl
+cmdline_hist +cmdline_info +comments +cryptv +cscope +dialog_con_gui +diff=
=20
+digraphs +dnd -ebcdic -emacs_tags +eval
+ex_extra +extra_search -farsi +file_in_path +find_in_path +folding -footer=
=20
+fork() -gettext -hangul_input +iconv
+insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent=20
+listcmds +localmap +menu +mksession
+modify_fname +mouse +mouseshape -mouse_dec +mouse_gpm -mouse_jsbterm=20
=2Dmouse_netterm +mouse_xterm +multi_byte
+multi_lang +netbeans_intg -osfiletype +path_extra +perl +postscript +print=
er=20
+python +quickfix -rightleft -ruby
+scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax=20
+tag_binary +tag_old_static -tag_any_white
=2Dtcl +terminfo +termresponse +textobjects +title +toolbar +user_commands=
=20
+vertsplit +virtualedit +visual +visualextra
+viminfo +vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfonts=
et=20
+xim +xsmp_interact +xterm_clipboard
=2Dxterm_save
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK =20
=2DI/opt/gnome/include/gtk-2.0 -I/opt/gnome/lib/gtk-2.0/i
nclude -I/opt/gnome/include/atk-1.0 -I/opt/gnome/include/pango-1.0=20
=2DI/usr/X11R6/include -I/usr/include/freetype2 -I/opt
/gnome/include/glib-2.0 -I/opt/gnome/lib/glib-2.0/include     -g -O2 =20
=2DI/usr/X11R6/include  -D_REENTRANT -D_GNU_SOURCE
=2DDTHREADS_HAVE_PIDS  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=3D64 =20
=2DI/usr/lib/perl5/5.8.1/i586-linux-thread-multi/CORE  -
I/usr/local/include/python2.4 -pthread
Linking: gcc  -L/usr/X11R6/lib   -rdynamic=20
=2DWl,-rpath,/usr/lib/perl5/5.8.1/i586-linux-thread-multi/CORE   -L/usr/loc=
al/
lib -o vim   -Wl,--export-dynamic -L/opt/gnome/lib -lgtk-x11-2.0 -lgdk-x11-=
2.0=20
=2Dlatk-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=20
=2Dlncurses -lgpm -rdynamic -Wl,-rpath,/usr/lib/
perl5/5.8.1/i586-linux-thread-multi/CORE  /usr/lib/perl5/5.8.1/i586-linux-t=
hread-multi/auto/DynaLoader/DynaLoader.a=20
=2DL/
usr/lib/perl5/5.8.1/i586-linux-thread-multi/CORE -lperl -lutil -lc=20
=2DL/usr/local/lib/python2.4/config -lpython2.4 -lutil
 -lm -Xlinker -export-dynamic


Javier

Just go with the flow control, roll with the crunches, and, when you get a=
=20
prompt, type like hell.

Re: [Vim-latex-devel] Problem with environment insert

[Srinath A. <sri...@gm...>]

On 11/26/05, Min Klugh <klu...@ho...> wrote:
> I installed latexSuite20051119.tar.gz and have problem with inserting
> environments with <F5> for eqnarray(*), equation, and align(*) which
> have "label{}" tag in it. When I do <F5> + number to choose one of them,
> or type "eqnarray" and type <F5>, it looks like the followings :
>
> \begin{eqnarray}
> [cursor]
> \label{<++>}
> \end{eqnarray}<++>
>
> where [cursor] means the position of the cursor, which is wrong.
> I installed the same package to another machine and it works.
> I suspected vim version (6.3), so installed 6.4 but the same.

It looks like you are talking about "place holders". See

http://vim-latex.sourceforge.net/index.php?subject=3Dfaq&title=3DFAQ#faq-pl=
aceholders

As of vim 1.5, the single character which looks like "<<" has been
replaced by the two characters "<+".

HTH,
Srinath

Re: [Vim-latex-devel] Problem with environment insert

[Javier R. <jer...@gm...>]

> where [cursor] means the position of the cursor, which is wrong.
> I installed the same package to another machine and it works.
> I suspected vim version (6.3), so installed 6.4 but the same.
I'm having a similar problem. The "compile multiple times" feature works on 
some machines, and on some others it doesn't
> The machine with trouble is redhat fedora core 4 and vim version is
> "VIM - Vi IMproved 6.3 (2004 June 7, compiled Apr 27 2005 02:21:46)".
> The other machine working fine is Gentoo.

a vim 6.3 compiled from source works fine. But a 6.3 bundled with the distro 
(SuSE 9.2), doesn't. Besides, a 6.4 compiled from source doesn't work either

email me if you need the compilation flags (but I think that all the compiled 
from source things where compiled with all the options)
-- 
Javier

The more we disagree, the more chance there is that at least one of us is 
right.

[Vim-latex-devel] Problem with environment insert

[Min K. <klu...@ho...>]

I installed latexSuite20051119.tar.gz and have problem with inserting
environments with <F5> for eqnarray(*), equation, and align(*) which
have "label{}" tag in it. When I do <F5> + number to choose one of them,
or type "eqnarray" and type <F5>, it looks like the followings :

\begin{eqnarray}
[cursor]
\label{<++>}
\end{eqnarray}<++>

where [cursor] means the position of the cursor, which is wrong.
I installed the same package to another machine and it works.
I suspected vim version (6.3), so installed 6.4 but the same.

The machine with trouble is redhat fedora core 4 and vim version is
"VIM - Vi IMproved 6.3 (2004 June 7, compiled Apr 27 2005 02:21:46)".
The other machine working fine is Gentoo.

Let me know if you need other information to resolve this problem.

Thank you

[Vim-latex-devel] Re: How to use cite completion with \nobibliography ?

[Ryan L. <rd...@gm...>]

I just wanted to post a follow up.  Nobody has any idea about this problem?

Cite completion should not depend on whether or not one wishes to create a
separate bibliography.  Either I'm missing something obvious or latex-suite
should check for \nobibliography as well as \bibliography when searching fo=
r
the .bib file.

Thanks,
Ryan

On 11/9/05, Ryan Long <rd...@gm...> wrote:
>
> Hello folks.
>
> I could never get cite completion (with F9) to work, until I noticed that
> latex-suite treats \bibliography differently from \nobibliography.
>
> If my file has a \bibliography{filename} command, cite completion works.
>
> If my file has a \nobibliography{filename} command, cite completion does
> not work, even if the BIBINPUTS setting in my texrc points directly at my
> .bib file.
>
> Can someone suggest a solution to this problem?  In the humanities, you
> usually do not use a bibliography in articles, but rather all citations g=
o
> into footnotes.  I would like to be able to use cite completion without
> having a bibliography in my file.
>
> Thanks for any assistance.
>

Re: [Vim-latex-devel] Some issues with completion

[Dan P. <da...@lc...>]

Srinath,

I'm surprised my little kludge worked at all, to be honest.  I
initially just added a

let retVal =3D escape(retVal, "{")

to Tex_EscapeForGrep.  I thought I'd gotten things all worked out
because it fixed the issue with label-searching, but bibtex was still
a problem.  Actually, this escape actually messes things up when used
in concert with the double-quotes.

My shell is tcsh.  If I switch to bash in my .vimrc (or any time
before loading the latex-suite stuff) the original code works fine.
Interestingly, so does my double-quoted version.

My OS is simply GNU/Debian Linux using the testing (etch) distribution.
I originally was working with the packaged .deb (based on a late 2004
release) of latex-suite, but ran into the same difficulty and decided
to upgrade to the newest snapshot before tinkering.

tcsh version:
tcsh 6.14.00 (Astron) 2005-03-25 (i486-intel-linux) options
wide,nls,bye,al,ng,rh,nd,color,filec

bash version:
GNU bash, version 3.00.16(1)-release (i486-pc-linux-gnu)
Copyright (C) 2004 Free Software Foundation, Inc.

grep version:
grep (GNU grep) 2.5.1

The short summary is, use tcsh and you should be able to reproduce
this issue.  Yet another reason for me to finally switch to bash.

cheers,
Dan

On Sun, Nov 20, 2005 at 09:11:13PM -0800, Srinath Avadhanula wrote:
> Hi Dan,
>=20
> Thanks for pointing this out... I am afraid that adding doublequotes
> isn't a very portable solution. There are multiple ways in which the
> grep command finally gets to the underlying operating system. One of
> the most common way is:
>=20
> bash -c "grep -nH pattern filelist"
>=20
> In this invokation, having double quotes in the pattern would
> definitely screw things up. What would be better is escaping the
> characters which grep treats specially. Is this whats happening in
> your case? It will help if you can supply an example of when things go
> wrong for you.. Also, I am curious about your OS and your 'shell'
> setting.
>=20
> Thanks,
> Srinath
>=20
> On 11/20/05, Dan Pemstein <da...@lc...> wrote:
> > Hi there,
> >
> > \ref and \cite completion did not work for me out of the box with the
> > 2005.11.19 release and vim 6.3.86 on a debian testing linux machine.
> > The issue is with grep: curly brackets were not being correctly
> > escaped.  This is with the line
> >
> > set grepprg=3D/bin/grep\ -nH\ $*
> >
> > in $VIM/ftplugin/tex.vim.  It might be my version of grep...I'm not
> > sure.  In any case, two changes to
> > $VIMRUNTIME/ftplugin/latex-suite/texview.vim got things working for
> > me.  In both cases, I added double-quotes to expressions to fix the
> > issue.  First, I changed line 543 to
> >
> > call Tex_Grepadd('"@.*{'.a:prefix.'"', "%")
> >
> > Second, on line 625:
> >
> > call Tex_Grepadd('"\label{'.a:prefix.'"', "%")
> >
> > I wanted to express my appreciation for the work you guys put into
> > latex-suite.  It is immensely convenient.  Hopefully the info above
> > will be useful to you.
> >
> > cheers,
> >
> > Dan
> >
> > --
> > Daniel Pemstein
> > Email: db...@ui..., da...@lc...
> > Web:   http://www.danpemstein.com
> > PGP:   http://www.danpemstein.com/files/pgp.txt
> >
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.2 (GNU/Linux)
> >
> > iD8DBQFDgUmIItxEqhMqILgRAnkQAJ4hjSQ26dXgZSWgbz9UYWTKVmk0bQCfWQ/6
> > fIIvrn27Uq3yxuYNFHvtjIs=3D
> > =3DS8Ii
> > -----END PGP SIGNATURE-----
> >
> >
> >
>=20

--=20
Daniel Pemstein
Email: da...@lc...
Web:   http://www.danpemstein.com
PGP:   http://www.danpemstein.com/files/pgp.txt

Re: [Vim-latex-devel] Some issues with completion

[Srinath A. <sri...@gm...>]

Hi Dan,

Thanks for pointing this out... I am afraid that adding doublequotes
isn't a very portable solution. There are multiple ways in which the
grep command finally gets to the underlying operating system. One of
the most common way is:

bash -c "grep -nH pattern filelist"

In this invokation, having double quotes in the pattern would
definitely screw things up. What would be better is escaping the
characters which grep treats specially. Is this whats happening in
your case? It will help if you can supply an example of when things go
wrong for you.. Also, I am curious about your OS and your 'shell'
setting.

Thanks,
Srinath

On 11/20/05, Dan Pemstein <da...@lc...> wrote:
> Hi there,
>
> \ref and \cite completion did not work for me out of the box with the
> 2005.11.19 release and vim 6.3.86 on a debian testing linux machine.
> The issue is with grep: curly brackets were not being correctly
> escaped.  This is with the line
>
> set grepprg=3D/bin/grep\ -nH\ $*
>
> in $VIM/ftplugin/tex.vim.  It might be my version of grep...I'm not
> sure.  In any case, two changes to
> $VIMRUNTIME/ftplugin/latex-suite/texview.vim got things working for
> me.  In both cases, I added double-quotes to expressions to fix the
> issue.  First, I changed line 543 to
>
> call Tex_Grepadd('"@.*{'.a:prefix.'"', "%")
>
> Second, on line 625:
>
> call Tex_Grepadd('"\label{'.a:prefix.'"', "%")
>
> I wanted to express my appreciation for the work you guys put into
> latex-suite.  It is immensely convenient.  Hopefully the info above
> will be useful to you.
>
> cheers,
>
> Dan
>
> --
> Daniel Pemstein
> Email: db...@ui..., da...@lc...
> Web:   http://www.danpemstein.com
> PGP:   http://www.danpemstein.com/files/pgp.txt
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (GNU/Linux)
>
> iD8DBQFDgUmIItxEqhMqILgRAnkQAJ4hjSQ26dXgZSWgbz9UYWTKVmk0bQCfWQ/6
> fIIvrn27Uq3yxuYNFHvtjIs=3D
> =3DS8Ii
> -----END PGP SIGNATURE-----
>
>
>

[Vim-latex-devel] Some issues with completion

[Dan P. <da...@lc...>]

Hi there,

\ref and \cite completion did not work for me out of the box with the
2005.11.19 release and vim 6.3.86 on a debian testing linux machine.
The issue is with grep: curly brackets were not being correctly
escaped.  This is with the line

set grepprg=3D/bin/grep\ -nH\ $*

in $VIM/ftplugin/tex.vim.  It might be my version of grep...I'm not
sure.  In any case, two changes to
$VIMRUNTIME/ftplugin/latex-suite/texview.vim got things working for
me.  In both cases, I added double-quotes to expressions to fix the
issue.  First, I changed line 543 to

call Tex_Grepadd('"@.*{'.a:prefix.'"', "%")

Second, on line 625:

call Tex_Grepadd('"\label{'.a:prefix.'"', "%")

I wanted to express my appreciation for the work you guys put into
latex-suite.  It is immensely convenient.  Hopefully the info above
will be useful to you.

cheers,

Dan

--=20
Daniel Pemstein
Email: db...@ui..., da...@lc...
Web:   http://www.danpemstein.com
PGP:   http://www.danpemstein.com/files/pgp.txt

Re: [Vim-latex-devel] Some problems, no answers found

[Srinath A. <sri...@gm...>]

Hi,

I fixed the problems in CVS. Latex-suite should now behave as follows:

In insert mode, if the cursor is touching a word, then that word is
replaced by a command constructed with that word. If the cursor is
located on a white-space character, then you will be prompted with a
list of commands to choose from. [...] Pressing <F7> in normal mode is
equivalent to pressing i to go to insert mode and then pressing <F7>.

The problem was in a buggy implementation of Tex_DoCommand. I don't
think this should be affected by other plugins/ftplugins.

Srinath

On 11/16/05, Jorge Scandaliaris <j_s...@ya...> wrote:
> Hi,
> As I work more on latex, latexSuite is becoming essential to me.
> Initially I just used a couple of features, but now I am spending some
> time reading the docs to fully use latexSuite's power.
> The problem I face now (I already fixed some others like alt keys
> macros, remapping them to ctrl) is the behaviour of the F7 key.
>
> Description of the problems:
>
> 1. It works in insert mode if <F7> is pressed just after the word.
> 2. If pressed in the middle of a word, in insert mode, then a command is
> made with the part of the word to the left of the cursor. (this might
> not be a bug, but the way the feature has been designed?).
> 3. If pressed in insert mode over a blank, it inserts a "0" (zero). The
> exception to this is when the line is empty, then the menu appears.
> 4. In normal mode, I can't find a logical pattern. Sometimes, if pressed
> over a word, then the word is used as a command. Pressing it in blanks
> doesn't bring the menu and, what's worst, it seems to leave the function
> stucked in a sense that it will only insert 0s (zeroes) every time the
> <F7> key is pressed.
> 4. Visual mode seems to do what's advertised on the docs.
>
> Any ideas? I use linux and vim 6.4, latexSuite 20041219. Do you know of
> other vim plugins or settings that might interfere with latexSuite?
> List of used plugins (I think the list is complete):
> plugin                  vim.org's script number
>
> xsl-syntax              257
> xquery-syntax           803
> wikipedia-syntax        na
> taglist                 273
> showmarks               152
> selinux-syntax          na
> pgn-syntax              677
> pam-syntax              778
> nagios-syntax           na
> multiplesearch          479
> latexsuite              na
> info                    21
> help-extra-syntax       570
> gentoo-syntax           na
> genindent               678
> fluxbox-syntax          679
> ebnf-syntax             545
> doxygen-syntax          5
> colorschemes            693
> cfengine-syntax         na
> cecutil                 1066
> brainfuck-syntax        716
> bnf-syntax              250
> ant                     155
> align                   294
> vimcommander            808
> gtags                   na
> NERD_comments           na
> vimspell                na
> manpageview             na
>
> Thanks in advance,
>
> Jorge
>
>
>
>
>
>
>
>
> ______________________________________________
> Renovamos el Correo Yahoo!
> Nuevos servicios, m=E1s seguridad
> http://correo.yahoo.es
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] Tex_MathBF()

[Srinath A. <sri...@gm...>]

Hi,

Both these suggestions make sense. I just changed the documentation
and brackets.vim.

Srinath

On 11/16/05, Jorge Scandaliaris <j_s...@ya...> wrote:
> Hi,
> According to the doc (latex-suite.txt 20041219):
>
> <Alt-M>                   *ls_3_10_2* *ls_a_by* *Alt-M*
>
> This insert-mode mapping encloses the previous character in \mathbf{}.
> Looking at brackets.vim, I actually see that the case is changed to
> upper-case:
>
> function! Tex_MathBF()
>         return "\<Left>\\mathbf{\<Right>}\<Esc>hvUla"
>
> I prefer that Tex_MathBF respects the case, because I need to enter
> upper and lower case letters very often. Does this make sense to you?
> By the way, the mapping is wrong in above quoted section of the doc, as
> it is defined as <M-B> later on.
>
> Cheers,
>
> Jorge
>
>
> ______________________________________________
> Renovamos el Correo Yahoo!
> Nuevos servicios, m=E1s seguridad
> http://correo.yahoo.es
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
> Register for a JBoss Training Course.  Free Certification Exam
> for All Training Attendees Through End of 2005. For more info visit:
> http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] using pdflatex and dvi->ps->pdf concurrently

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

Hi

I wrote something on this topics some day ago. Well i read the docs and
tried myself:

I defined new rules "_pdfl" (for pdfLatex). Compiling works fine, but
the viewer seeks for *.pdfl. As workaround I use a symbolic link 
*.pdfl -> *.pdf.

Any ideas for a real solution to that?

Thanks. Sebastian.

[Vim-latex-devel] How can I use my own latex distribution with LaTeX-Suite

[Jeremy C. <jer...@gm...>]

I recently discovered LaTeX-Suite and am excited about using it.=20
However, I already have LaTeX installed on my machine with  my own
collection of packages and such.  I don't want to have to set up all
my preferences again for LaTeX-Suite.  Is there somewhere I can just
tell it where my LaTeX distribution is located?
Thanks,
Jeremy

[Vim-latex-devel] Tex_MathBF()

[Jorge S. <j_s...@ya...>]

Hi,
According to the doc (latex-suite.txt 20041219):

<Alt-M>                   *ls_3_10_2* *ls_a_by* *Alt-M*

This insert-mode mapping encloses the previous character in \mathbf{}.
Looking at brackets.vim, I actually see that the case is changed to 
upper-case:

function! Tex_MathBF()
	return "\<Left>\\mathbf{\<Right>}\<Esc>hvUla"

I prefer that Tex_MathBF respects the case, because I need to enter 
upper and lower case letters very often. Does this make sense to you?
By the way, the mapping is wrong in above quoted section of the doc, as 
it is defined as <M-B> later on.

Cheers,

Jorge

		
______________________________________________ 
Renovamos el Correo Yahoo! 
Nuevos servicios, más seguridad 
http://correo.yahoo.es