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

[Vim-latex-devel] [Contact] Testing...

[Srinath A. <vim...@so...>]

There has been a slight modification to the contact page. Just testing... Hopefully, 
this e-mail will get through without problems. 



Sorry for the spam.  

[Vim-latex-devel] [Contact] Main web page needs a spell-check

[R. W. v. C. f. <vim...@so...>]

Hi - a friendly bit of advice: spell-check you web page(s) and you will find errors  
:-)



Regards,

R.  

Re: [Vim-latex-devel] [Contact] vim-latex 2003 12 16 bug

[Srinath A. <sr...@fa...>]

On Tue, 2 Mar 2004, Contact form wrote:

>
> When a try to insert a /cite reference on a secundary file where the
> primary file is named master.tex and I have the file
> master.tex.latexmain the program opens a file called master instead of
> the usual complation window.
>
This looks like it was a recently fixed bug. I will make a new release
soon, but for the moment, I would advise keeping with 1.5

Thanks,
Srinath

Re: [Vim-latex-devel] [Contact] bug in win32 handling of master dvi documents

[Srinath A. <sr...@fa...>]

On Thu, 26 Feb 2004, Contact form wrote:

> document. Specifically, the windows command line does not handle
> correctly file paths with spaces, so that running \\lv fails with
> a message saying a file was not found.
>

Thanks! Fixed in CVS.

Srinath

Re: [Vim-latex-devel] \cite completion bug report & patch

[Srinath A. <sr...@fa...>]

On Wed, 25 Feb 2004, Volker Gaibler wrote:

> A patch against the development version latexSuite20031216 is attached.
>
Thanks! Applied to the latest CVS version


> BTW: IMHO the correction in the previous mail of an unknown person
> should be
>
> TexLet g:Tex_ItemStyle_description = '\item[<+label+>] <++>'
>
> to work correctly (line 880 in ftplugin/latex-suite/envmacros.vim of
> latest development version.
>
Agreed. This has also been fixed in the latest CVS version.

Thanks,
Srinath

[Vim-latex-devel] [Contact] vim-latex 2003 12 16 bug

[Contact f. <vim...@so...>]

When a try to insert a /cite reference on a secundary file where the primary file is 
named master.tex and I have the file master.tex.latexmain the program opens a file 
called master instead of the usual complation window.

I switched back to version 
1.5. This version doesn\'t have this problem.



Thanks for your attention

Jorge 
Pulido  

Re: [Vim-latex-devel] problem with Tex_IgnoredWarnings

[Alan S. <ala...@po...>]

* Srinath Avadhanula (sr...@fa...) wrote:
> On Thu, 19 Feb 2004, Alan Schmitt wrote:
>=20
> > Sorry, I get this doing a "let Tex_IgnoredWarnings". "echo" does return
> > it on several lines.
> >
> It works okay for me at least with the latest CVS version. I put the
> following in ~/.vim/after/ftplugin/tex.vim:
>=20
> let g:Tex_IgnoredWarnings =3D
>                         \ "inputting\n" .
>                         \ "Unused global option\n" .
>                         \ "Marginpar on page\n" .
>                         \ "No \\\\author given.\n" .
>                         \ "LaTeX Font Warning\n" .
>                         \ g:Tex_IgnoredWarnings
> let g:Tex_IgnoreLevel =3D g:Tex_IgnoreLevel + 5
>=20
> and I do successfully ignore the warning which you noted.
>=20
> This is somewhat strange. Is it still happening?

I should test again ... I have moved to other papers, and the warning=20
does not occur anymore. I'll upgrade to the current version and will let=20
you know if I see this again.

Thanks for the help (and the great tex mode ;-) )

Alan Schmitt

--=20
The hacker: someone who figured things out and made something cool happen.
=2EO.
=2E.O
OOO

Re: [Vim-latex-devel] [Contact] description environment macros

[Srinath A. <sr...@fa...>]

On Mon, 23 Feb 2004, Contact form wrote:

> When in a description environment, the first item inserted gets
> a \"<++>\" entry after it, but subsequent ones don\'t.  Changing line
> 888 in envmacros.vim to the following fixes this (and the misspelling
> of \'lablel\'):
>
> TexLet g:Tex_ItemStyle_description = \'\\item[<+label+>]
> <++>\'
>
Thanks! Changed.

Srinath

Re: [Vim-latex-devel] problem with Tex_IgnoredWarnings

[Srinath A. <sr...@fa...>]

On Thu, 19 Feb 2004, Alan Schmitt wrote:

> Sorry, I get this doing a "let Tex_IgnoredWarnings". "echo" does return
> it on several lines.
>
It works okay for me at least with the latest CVS version. I put the
following in ~/.vim/after/ftplugin/tex.vim:

let g:Tex_IgnoredWarnings =
                        \ "inputting\n" .
                        \ "Unused global option\n" .
                        \ "Marginpar on page\n" .
                        \ "No \\\\author given.\n" .
                        \ "LaTeX Font Warning\n" .
                        \ g:Tex_IgnoredWarnings
let g:Tex_IgnoreLevel = g:Tex_IgnoreLevel + 5

and I do successfully ignore the warning which you noted.

This is somewhat strange. Is it still happening?

Srinath

Re: [Vim-latex-devel] [Contact] Different Behavior of <S-F5> with Remote Terminal and Local Terminal

[Srinath A. <sr...@fa...>]

>
> I am having trouble to invoke <S-F5> in insert mode to insert
> \\begin{equation} \\end{equation} when using local terminal
> (gnome-terminal and kde terminal alike). But the same thing will
> succeed if through a remote terminal (ssh from Windows XP).
>
Could it simply be the fact that you are supposed to use <S-F5> to
_change_ environments, not insert new ones. You are supposed to use
<F5> to insert new environments. It might be happening that when you ssh
through a remote terminal, vim only sees <F5> instead of <S-F5> causing
things to mysteriously "work". Could you test with the latest CVS and
with <F5> and report back if it works or not?

Srinath

Re: [Vim-latex-devel] [Contact] block comments and its syntex highlight

[Srinath A. <sr...@fa...>]

On Sun, 25 Jan 2004, Contact form wrote:

>
> Currently there are two types of block comments in latex:
>
> 1. \\iffalse and \\fi
> pair
>
> 2. \\begin{comment} \\end{comment} pair
>
> Would you please consider providing syntex highlight for these two
> types of block comments?  Thanks a lot in advance!
>
As of now, there is absolutely no support to change syntax highlighting
via latex-suite, although this is something which could be done in the
future.

Also, I have not personally played around too much with vim's syntax
highlighting capabilities. Could you contact Charles Campbell who is
the maintainer of the latex highlighting file? You can always find the
maintainer of a syntax scheme by editing

$VIMRUNTIME/syntax/tex.vim

Srinath

Re: [Vim-latex-devel] [Contact] Question on inverse search

[Srinath A. <sr...@fa...>]

Hello Xin Yin,

> gvim -c \":RemoteOpen +4 d:\\temp\\myfile.tex\"
>
> in the command window, and the vim appeared without
> opening myfile.tex.

It turned out to be a bug in Vim which caused this problem. I have
worked around this problem. The latest vim-latex version in CVS should
have the fix.

Thanks,
Srinath

Re: [Vim-latex-devel] I'm back :)

[Srinath A. <sr...@fa...>]

On Fri, 20 Feb 2004, Mikolaj Machowski wrote:

>
> Beware. Something is broken with vim-latex-cvs mailing list.
>

It was a problem with the syncmail script in the CVSROOT module. It was
built for python 1.5.2 and it looks like sourceforge migrated to python
2.2... Had to change the script around a little. Should begin working
again...

I have still not managed to catch up from my backlog...

Srinath

[Vim-latex-devel] [Contact] bug in win32 handling of master dvi documents

[Contact f. <vim...@so...>]

There is a problem on win32 systems when trying to open the dvi document resulting from 
the compilation of a part of a master document. Specifically, the windows command 
line does not handle correctly file paths with spaces, so that running \\lv fails with 
a message saying a file was not found.



I managed to fix the problem. Changing line 
258 of compiler.vim to:

exec \'!start\' s:viewer \'\"\' . substitute(mainfname, 
\"\\\\\\\\ \", \" \", \"g\") . \'\"\' . \'.\' . s:target



works 
fine.



Congratulations for your good work,



Panos.  

[Vim-latex-devel] \cite completion bug report & patch

[Volker G. <V.G...@ls...>]

Hello,

as I'm using a latex masterfile with included files (also in
subdirectories), I found a small bug which causes <F9> not to work=20
correctly after \cite{   (because the file extension was removed).

A patch against the development version latexSuite20031216 is attached.

BTW: IMHO the correction in the previous mail of an unknown person=20
should be

TexLet g:Tex_ItemStyle_description =3D '\item[<+label+>] <++>'

to work correctly (line 880 in ftplugin/latex-suite/envmacros.vim of=20
latest development version.=20

HTH,
Volker


--=20
 Volker Gaibler                     v.g...@ls...
 Landessternwarte K=F6nigstuhl        phone  +49 6221 509-263
 69117 Heidelberg                   fax    +49 6221 509-202
 Germany                            http://www.lsw.uni-heidelberg.de
+---------------------------------------------------------------------+

[Vim-latex-devel] [Contact] description environment macros

[Contact f. <vim...@so...>]

Version: latexSuite20031022.tar.gz



When in a description environment, the 
first item inserted gets a \"<++>\" entry after it, but subsequent ones don\'t. 
Changing line 888 in envmacros.vim to the following fixes this (and the misspelling 
of \'lablel\'):



TexLet g:Tex_ItemStyle_description = \'\\item[<+label+>] 
<++>\'

  

[Vim-latex-devel] Re: Bug#233682: !commando ends in insert mode

[Artur R. C. <ar...@he...>]

Hello

plugin/imaps.vim:481 and next contains:

if !hasmapto('<Plug>IMAP_JumpForward', 'n')
    nmap <C-J> <Plug>IMAP_JumpForward
endif

What are above lines for? I discovered, that this piece of code is
responsible for bug reported to Debian: http://bugs.debian.org/233682:

On Thu, Feb 19, 2004 at 01:11:07PM +0100, Diether Knof wrote:
> If I press 'Return' while a shell commando is executed, I am in input mode afterwards.
> Example ':!sleep 5' followed by a <Return> (while sleeping).

It looks like <Return> key generates two keystrokes: ^M, which
is interpreted by vim as "Enter" at:
Hit ENTER or type command to continue
and ^J which is passed into processing and, in this case, which runs (via
nmap) IMAP_JumpForward.

Behavior which I cannot understand is: why <Return> pressed after "Hit
ENTER..." message works correctly, but pressed before it works bad.

Is it vim-latex or vim bug?

Cheers
	Artur
-- 
http://www.shibumi.org/eoti.htm

Re: [Vim-latex-devel] I'm back :)

[Mikolaj M. <mi...@wp...>]

Dnia pią 20. lutego 2004 03:44, Srinath Avadhanula napisał:
> Hello everyone!
>
> I was away on one long trip to India recently... (it was a lot of fun.)
> It was a busy week just before leaving hence I did not get time to
> properly announce the vacation... Anyway, I am back and will slowly work
> through the accumulated bug-reports etc in the coming weeks and make the
> next release. So please be patient...  (as you all have been
> apparently).

Beware. Something is broken with vim-latex-cvs mailing list.

m.

-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/
Learn Touch Typing with Vim? Oui. Ja. Yes. Tak:
  http://vim.sourceforge.net/script.php?script_id=461
vim.pl - http://skawina.eu.org/mikolaj/

[Vim-latex-devel] Adding Custom Macros for packages

[Aditya M. <adi...@al...>]

Hi,
 I like the envmacro feature of vim-latex a lot and would like to use
it for other package that I frequently use. I started with defining
envmacros in the envmarco.vim file but then Mikolaj Machowski
suggested that these mappings should go in the package directory.
The scheme that I have come up with is to define the mappings within
the g:Tex_package_packagename string in the package/packagename file.
I started with the amsmath package as it is the most widely used.

So, what I wanted to do was

EAL expands to
 \begin{align}
	<++>
 \end{align}<++>

and similarly EGA expands to gahter environment.

So, I changed packages/amsmath as follows
-23 \.'env:align'
+23 \.'env:aling#EAL'

-25 \.'env:gather'
+25 \.'env:gather#EGA'

Next I modified the function Tex_ProcessPackageCommand in packages.vim
has follows

function! Tex_ProcessPackageCommand(command)
 if a:command =~ ':'
   let commandType = matchstr(a:command, '^\w\+\ze:')
   let commandName = matchstr(a:command, '^\w\+:\zs[^:#]\+\ze:\?')
   let extra = strpart(a:command, strlen(commandType.':'.commandName))
   let extrapart   = matchstr(extra,'^:\zs\w\+\ze#')
   let mapping     = matchstr(extra,'#\zs.\+\ze')
 else
   let commandType = ''
   let commandName = a:command
   let extrapart   = ''
   let mapping     = ''
 endif

 let command = s:CommandSpec_{commandType}
 let command = substitute(command, '<+replace+>', commandName, 'g')
 let command = substitute(command, '<+extra+>', extrapart, 'g')
 if mapping != ''

   if g:Tex_EnvironmentMaps
	call IMAP (mapping,'\begin{'.commandName."}\<CR>".extrapart."<++>\<CR>\\end{".commandName."}<++>", 'tex')
   endif

 endif
 return IMAP_PutTextWithMovement(command)
endfunction

This does not work properly. If I open a tex file having
\usepackage{amsmath} and type EAL nothing happens. But if I use the
menu to go to TeX-Suite -> Packages -> amsmath command -> Environment
and choose 'align#EAL' (I have to sort out the menu entry) it will
output the align environment. Now EAL will expand as desired.

What this means is that Tex_ProcessPackageCommand() is being called
only when I choose the menu item and not otherwise. So this method is
doomed.

Can anyone suggest what would be a better method to assign environment
macros to packages

Sincerely
Aditya


-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

[Vim-latex-devel] I'm back :)

[Srinath A. <sr...@fa...>]

Hello everyone!

I was away on one long trip to India recently... (it was a lot of fun.)
It was a busy week just before leaving hence I did not get time to
properly announce the vacation... Anyway, I am back and will slowly work
through the accumulated bug-reports etc in the coming weeks and make the
next release. So please be patient...  (as you all have been
apparently).

Thanks,
Srinath

Re: [Vim-latex-devel] problem with Tex_IgnoredWarnings

[Alan S. <ala...@po...>]

* Mikolaj Machowski (mi...@wp...) wrote:
> > Tex_IgnoredWarnings    inputting^@Unused global option^@Marginpar on
> > page^@No \\author given.^@LaTeX Font
> > Warning^@Underfull^@Overfull^@specifier changed to^@You have
> > requested^@Missing number, treated as zero.^@There were undefined
> > references^@Citation %.%# undefined
>=20
> How do you get this output - echo Tex_IgnoredWarnings?
>=20
> It should be cleanly shown in separate lines (at least I am getting this
> on Linux).

Sorry, I get this doing a "let Tex_IgnoredWarnings". "echo" does return=20
it on several lines.

> > (sorry for the word wrap)
> >
> > I compile using a Makefile.
> >
> > So my questions are:
> > - What is wrong with my pattern ?
>=20
> Did you try check bugs with Tex_Debug and Tex_PrintDebug?

Nope, I'll look up the help for those.

>=20
> > - How can I suppress all "inputting ... instead of obsolete ..."
> >   messages (I tried using regular expressions, but they did not work. As
> >   "inputting" by itself does not work, there might be something else
> >   there as well).
>=20
> Code responsible for parsing IgnoredWarnings is in compiler/tex.vim. Try
> to add your expressions there. Ugly but simplest way to check what
> doesn't work.

OK, will do. Thanks for the help.

Alan Schmitt

--=20
The hacker: someone who figured things out and made something cool happen.
=2EO.
=2E.O
OOO

Re: [Vim-latex-devel] problem with Tex_IgnoredWarnings

[Mikolaj M. <mi...@wp...>]

Dnia pon 16. lutego 2004 15:09, Alan Schmitt napisał:
> Hi,
>
> As I get some warnings fairly often, I'm trying to shut them down using
> the variable Tex_IgnoredWarnings. However for some reason it does not
> seem to work (using the current cvs version).
>
> I want to remove the following warning:
>
> /usr/share/texmf/tex/latex/base/fleqn.sty|| LaTeX Warning: inputting
> `fleqn.clo' instead of obsolete `fleqn.sty'.
>
> I have the following after/ftplugin/tex.vim file:
>
> if !exists('g:did_my_tex_stuff')
>   let g:did_my_tex_stuff = 1
>   let g:Tex_IgnoredWarnings = "inputting\n" . "Unused global option\n" .
> "Marginpar on page\n" . "No \\\\author given.\n" . "LaTeX Font Warning\n"
> . g:Tex_IgnoredWarnings let g:Tex_IgnoreLevel = g:Tex_IgnoreLevel + 5
> endif
>
> which seems to be taken into account as asking what Tex_IgnoredWarnings
> is returns:
>
> Tex_IgnoredWarnings    inputting^@Unused global option^@Marginpar on
> page^@No \\author given.^@LaTeX Font
> Warning^@Underfull^@Overfull^@specifier changed to^@You have
> requested^@Missing number, treated as zero.^@There were undefined
> references^@Citation %.%# undefined

How do you get this output - echo Tex_IgnoredWarnings?

It should be cleanly shown in separate lines (at least I am getting this
on Linux).

> (sorry for the word wrap)
>
> I compile using a Makefile.
>
> So my questions are:
> - What is wrong with my pattern ?

Did you try check bugs with Tex_Debug and Tex_PrintDebug?

> - How can I suppress all "inputting ... instead of obsolete ..."
>   messages (I tried using regular expressions, but they did not work. As
>   "inputting" by itself does not work, there might be something else
>   there as well).

Code responsible for parsing IgnoredWarnings is in compiler/tex.vim. Try
to add your expressions there. Ugly but simplest way to check what
doesn't work.

m.

-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/
Learn Touch Typing with Vim? Oui. Ja. Yes. Tak:
  http://vim.sourceforge.net/script.php?script_id=461
vim.pl - http://skawina.eu.org/mikolaj/

[Vim-latex-devel] problem with Tex_IgnoredWarnings

[Alan S. <ala...@po...>]

Hi,

As I get some warnings fairly often, I'm trying to shut them down using=20
the variable Tex_IgnoredWarnings. However for some reason it does not=20
seem to work (using the current cvs version).

I want to remove the following warning:

/usr/share/texmf/tex/latex/base/fleqn.sty|| LaTeX Warning: inputting `fleqn=
=2Eclo' instead of obsolete `fleqn.sty'.

I have the following after/ftplugin/tex.vim file:

if !exists('g:did_my_tex_stuff')
  let g:did_my_tex_stuff =3D 1
  let g:Tex_IgnoredWarnings =3D "inputting\n" . "Unused global option\n" . =
"Marginpar on page\n" . "No \\\\author given.\n" . "LaTeX Font Warning\n" .=
 g:Tex_IgnoredWarnings
  let g:Tex_IgnoreLevel =3D g:Tex_IgnoreLevel + 5
endif

which seems to be taken into account as asking what Tex_IgnoredWarnings=20
is returns:

Tex_IgnoredWarnings    inputting^@Unused global option^@Marginpar on=20
page^@No \\author given.^@LaTeX Font=20
Warning^@Underfull^@Overfull^@specifier changed to^@You have=20
requested^@Missing number, treated as zero.^@There were undefined=20
references^@Citation %.%# undefined

(sorry for the word wrap)

I compile using a Makefile.

So my questions are:
- What is wrong with my pattern ?
- How can I suppress all "inputting ... instead of obsolete ..."=20
  messages (I tried using regular expressions, but they did not work. As=20
  "inputting" by itself does not work, there might be something else=20
  there as well).

Thanks for any hint.

Alan

--=20
The hacker: someone who figured things out and made something cool happen.
=2EO.
=2E.O
OOO

[Vim-latex-devel] [Contact] Different Behavior of <S-F5> with Remote Terminal and Local Terminal

[Contact f. <vim...@so...>]

I am having trouble to invoke <S-F5> in insert mode to insert \\begin{equation} 
\\end{equation} when using local terminal (gnome-terminal and kde terminal 
alike). But the same thing will succeed if through a remote terminal (ssh from Windows 
XP).



The error message is as following:

    Error detected while processing 
function Tex_ChangeEnvironments..<SNR>29_Change: 

    line   20:

    E486: Pattern 
not found: \\\\\\]\\|\\\\end{.\\{-}}

    line   22:

    E486: Pattern not found: 
\\\\\\[\\|\\\\begin{.\\{-}}



I tried to set all the local terminal environment 
variable to the same as the remote one\'s. But this  still happens. $TERM is set to 
xterm.



This is RedHat 9, with XFree86-4.3.0, Gnome 2.2, and KDE 3.2. Vim is 6.2 
patched to patch 231, but 6.2 with patch 098 still has this problem.

  

Re: [Vim-latex-devel] [Contact] I can\'t do input of hangul.

[Mikolaj M. <mi...@wp...>]

Dnia Monday 09 of February 2004 02:24:
> I can\'t do  input of hangul.
>
Sorry, I don't know how to input hangul at all and cannot help you.

m.