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

Re: [Vim-latex-devel] List of mappings and =?iso-8859-1?Q?=E2?=

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

On Tue, 2 Sep 2003, Jean-Rene David wrote:

> I'm writing a text in French and a mapping is
> interfering with the character =E2 (a with a
> circonflex accent).

I have a feeling that this has to do with the Alt key mappings. If so
please refer to the (newly added) FAQ:

http://vim-latex.sourceforge.net/index.php?subject=3Dfaq#faq-5

HTH
Srinath

Re: [Vim-latex-devel] preference for default target

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

* Srinath Avadhanula (sr...@fa...) wrote:
> Hi Alan,
> 
> The patch looks good. Unfortunately, my patch program seems to be having
> trouble applying it. Oh well. Its simple enough to do manually. It looks
> like a good idea. I'll apply it soon. Thanks. In the longer term, maybe
> we need to have a setting where the user can use a completely different
> function for compiling a single file instead of Tex_CompileLatex().

That would be great.

> 
> On Tue, 2 Sep 2003, Alan Schmitt wrote:
> > Error detected while processing /home/schmitta/.vim/ftplugin/latex-suite/multicompile.vim:
> > line  200:
> > Traceback (most recent call last):
> >   File "<string>", line 1, in ?
> > ImportError: No module named string
> >
> > I think my python installation is broken with vim (it works well by
> > itself, I have noticed several problems with vim recently).
> >
> Unfortunate! But you can use
> 
> :let g:Tex_UsePython = 0
> 
> to make latex-suite use native vim script for reading the contents of
> a file. Its used for the new multiple compilation functionality.

My vim installation was broken (more precisely, I upgraded python (by 
rpm) and its installation dir changed). Rebuilding vim solved the issue.

Alan

-- 
The hacker: someone who figured things out and made something cool happen.

[Vim-latex-devel] List of mappings and =?iso-8859-1?Q?=E2?=

[Jean-Rene D. <jr...@ar...>]

Not sure this is the place for user questions.
Just tell me if it's better to use vim-users.

I don't use the gui, thus no menus. How can I
get a complete list of vim-latex insert mode
mappings?

I'm writing a text in French and a mapping is
interfering with the character â (a with a
circonflex accent).

thanks.

Re: [Vim-latex-devel] preference for default target

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

Hi Alan,

The patch looks good. Unfortunately, my patch program seems to be having
trouble applying it. Oh well. Its simple enough to do manually. It looks
like a good idea. I'll apply it soon. Thanks. In the longer term, maybe
we need to have a setting where the user can use a completely different
function for compiling a single file instead of Tex_CompileLatex().

On Tue, 2 Sep 2003, Alan Schmitt wrote:
> Error detected while processing /home/schmitta/.vim/ftplugin/latex-suite/multicompile.vim:
> line  200:
> Traceback (most recent call last):
>   File "<string>", line 1, in ?
> ImportError: No module named string
>
> I think my python installation is broken with vim (it works well by
> itself, I have noticed several problems with vim recently).
>
Unfortunate! But you can use

:let g:Tex_UsePython = 0

to make latex-suite use native vim script for reading the contents of
a file. Its used for the new multiple compilation functionality.

Srinath

Re: [Vim-latex-devel] preference for default target

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

* Srinath Avadhanula (sr...@fa...) wrote:
> Hello,
> 
> On Tue, 2 Sep 2003, Alan Schmitt wrote:
> > I am very often writing latex documents in collaboration with other
> > people, who use a Makefile with a target "all" to compile the paper.
> > I would like to change a preference so that as soon as a Makefile is
> > present, the default target is "all" (and not ps or dvi). Where can
> 
> You need to use the g:Tex_MainFileExpression described in the user
> manual:
> 
> http://vim-latex.sourceforge.net/documentation/latex-suite/latex-master-file.html
> 
> In particular, put the following snippet of code in
> ~/.vim/after/ftplugin/tex/mainfile.vim
> 
> ---------------------------%<---------------------------
> let g:Tex_MainFileExpression = 'MainFile(modifier)'
> function! MainFile(fmod)
>     " whenever a makefile is present in the file being edited, then set
>     " target to all. This will make pressing \ll result in running
>     " !make all
>     if glob('makefile') != ''
>         TCTarget all
>     endif
>     if glob('*.latexmain') != ''
>         return fnamemodify(glob('*.latexmain'), a:fmod)
>     else
>         return ''
>     endif
> endfunction
> ---------------------------%<---------------------------
> 
> NOTE: Any location which gets sourced after tex_latexSuite.vim on the
> filetype event will do.
> 
> The Tex_MainFileExpression is exec'd whenever latex-suite needs to find
> out which file needs to be compiled. If you put some code to set the
> target in it as above, then it will also change the target.

Thanks for your answer. Looking at the code and the web page, it seems 
that there is no way (short of modifying RunLaTeX) to have a similar 
solution to always ignore the Makefile. Would you accept a patch that 
would make this configurable ? (I'm thinking of something simple like

Index: ftplugin/latex-suite/compiler.vim
===================================================================
RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite/compiler.vim,v
retrieving revision 1.43
diff -u -p -r1.43 compiler.vim
--- ftplugin/latex-suite/compiler.vim   29 Aug 2003 02:29:35 -0000      1.43
+++ ftplugin/latex-suite/compiler.vim   2 Sep 2003 23:13:26 -0000
@@ -111,10 +111,11 @@ function! Tex_CompileLatex()
                let mainfname = escape(expand('%:t'), ' ')
        endif
 
-       " if a makefile exists, then use that irrespective of whether *.latexmain
+       " if a makefile exists, and g:Tex_MayUseMakefile is set (which is the 
+       " case by default) then use that irrespective of whether *.latexmain
        " exists or not. mainfname is still extracted from *.latexmain (if
        " possible) log file name depends on the main file which will be compiled.
-       if glob('makefile') != '' || glob('Makefile') != ''
+       if (glob('makefile') != '' || glob('Makefile') != '') && g:Tex_MayUseMakefile
                let _makeprg = &l:makeprg
                let &l:makeprg = 'make $*'
                if exists('s:target')
Index: ftplugin/latex-suite/texrc
===================================================================
RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite/texrc,v
retrieving revision 1.34
diff -u -p -r1.34 texrc
--- ftplugin/latex-suite/texrc  29 Aug 2003 02:55:48 -0000      1.34
+++ ftplugin/latex-suite/texrc  2 Sep 2003 23:13:26 -0000
@@ -115,6 +115,8 @@ TexLet g:Tex_CompileRule_html = 'latex2h
 
 TexLet g:Tex_CompileRule_bib = 'bibtex $*'
 
+TexLet g:Tex_MayUseMakefile = 1
+
 " }}}
 " ------------------------------------------------------------------------------ 
 " Viewer rules {{{

)

By the way, I now have an error when loading a tex file:

Error detected while processing /home/schmitta/.vim/ftplugin/latex-suite/multicompile.vim:
line  200:
Traceback (most recent call last):
  File "<string>", line 1, in ?
ImportError: No module named string

I think my python installation is broken with vim (it works well by 
itself, I have noticed several problems with vim recently).

Alan Schmitt

-- 
The hacker: someone who figured things out and made something cool happen.

Re: [Vim-latex-devel] preference for default target

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

Hello,

On Tue, 2 Sep 2003, Alan Schmitt wrote:
> I am very often writing latex documents in collaboration with other
> people, who use a Makefile with a target "all" to compile the paper.
> I would like to change a preference so that as soon as a Makefile is
> present, the default target is "all" (and not ps or dvi). Where can

You need to use the g:Tex_MainFileExpression described in the user
manual:

http://vim-latex.sourceforge.net/documentation/latex-suite/latex-master-file.html

In particular, put the following snippet of code in
~/.vim/after/ftplugin/tex/mainfile.vim

---------------------------%<---------------------------
let g:Tex_MainFileExpression = 'MainFile(modifier)'
function! MainFile(fmod)
    " whenever a makefile is present in the file being edited, then set
    " target to all. This will make pressing \ll result in running
    " !make all
    if glob('makefile') != ''
        TCTarget all
    endif
    if glob('*.latexmain') != ''
        return fnamemodify(glob('*.latexmain'), a:fmod)
    else
        return ''
    endif
endfunction
---------------------------%<---------------------------

NOTE: Any location which gets sourced after tex_latexSuite.vim on the
filetype event will do.

The Tex_MainFileExpression is exec'd whenever latex-suite needs to find
out which file needs to be compiled. If you put some code to set the
target in it as above, then it will also change the target.

HTH
Srinath

[Vim-latex-devel] preference for default target

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

Hi,

I am very often writing latex documents in collaboration with other 
people, who use a Makefile with a target "all" to compile the paper. 
I would like to change a preference so that as soon as a Makefile is 
present, the default target is "all" (and not ps or dvi). Where can 
I change such a preference (doing TTarget all is not very useful as it 
only works for one file, and I often deal with multiple files for one 
given paper).

Thanks,

Alan Schmitt

-- 
The hacker: someone who figured things out and made something cool happen.

[Vim-latex-devel] Fwd: Re: Bug#206050: vim-latexsuite File explorer won't work

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

----------  Przekazana wiadomość  ----------

Subject: Re: Bug#206050: vim-latexsuite File explorer won't work
Date: Thursday 21 of August 2003 13:42
From: Mikolaj Machowski <mi...@wp...>
To: Srinath Avadhanula <sr...@fa...>

On Mon, Aug 18, 2003 at 03:21:43PM -0700, Srinath Avadhanula wrote:
> I just ran an experiment. I removed the plugin/explorer.vim file which
> comes with latex-suite and tried the filename completion using <F9> and
> it works! So my guess is that whatever we need can indeed be done using
> wrapper functions which change various global settings, call :Explore
> and then remap certain keys in that buffer. Is this a feasible approach?
> Do you still wish to maintain a modified version of explorer.vim? If so,
> we will need to rename it to LatexSuiteExplorer.vim or something similar.

plugin/explorer.vim is/was necessary only for project features. It does
not affect texviewer commands/functions.

I still think we need something to handle projects. latex-suite has
problems with files nested in not orthodox ways, additionally it removes
from display of working directory auxiliary files. This cannot be
achieved with regular explorer.vim keeping backward compability to 6.0
Vim distribution (all functions needed for such functionality are local
to script - explorer.vim).

explorer.vim distributed with 6.2 have weak possibilities to interface
with other scripts. If we decide to break compatibility with 6.0 after
6.3 (I am for it[1]) we can try to do something with regular explorer.vim.

m.

[1] Use of new features:
- :popup - use popup menu to help, or inserting specific items
  this is not entirely new feature but this is currently available in
  all basic GUIs
- MultipleHead syntax. Patch prepared by Vince Negri probably will be
  included in 6.3. It will allow for producing quasi-wysiwyg code with
  UTF fonts.
- conceal patch. Also by Vince Negri. It allows for hiding syntax items.
  Althoutgh I don't especially like implementation it will allow for
  example for hiding items like \footnote, \index etc. to improve
  readability of basic text. (needs many redefinitions in syntax file)

OTOH all this don't need breaking compat. But providing separate
explorer.vim allows users of 6.0 to have some features which in other
case they wouldn't have.

m.

-------------------------------------------------------

Re: [Vim-latex-devel] New compiler features!

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

On Fri, 29 Aug 2003, Luc Hermitte wrote:

> I read on this page:
> > let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*'
> > let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
> > let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'
>
> I'd rather use definitions like:
>   let g:Tex_CompileRule_tex_dvi = 'latex --interaction=nonstopmode $*'
>   let g:Tex_CompileRule_dvi_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
>   let g:Tex_CompileRule_ps_pdf = 'ps2pdf $*.ps'
>
> Why ? Because we may prefer to use systematically pdflatex, but
> sometimes, for some documents, we may be interrested in ps2pdf because
> some particular packages, like pst-uml, are not compatible with
> pdflatex.
>
I actually gave those examples of g:Tex_CompileRule_format somewhat
redundantly. I assume that most people will be using the same rule on
most files. If someone does want to change the way compilation is done
on a particular file/project, then he can always use the .latexmain way
to redefine things within a certain directory. For example, the
.latexmain file could contain

let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'

in one directory and

let g:Tex_FormatDependency_pdf = 'pdf'
let g:Tex_CompileRule_pdf = 'pdflatex --interaction=nonstopmode $*'

in another. Better still, you could make a file called pst-uml in the
latex-suite/packages directory which contains something like:

let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'

This way a file which uses the pst-uml package automatically uses the
longer route while the others use the faster route.

Anyway, I did consider your way of doing it. But after some
consideration also of factors like backwards compatibility, I decided
that since I could do everything which I could forsee with the current
method, why change things?

> So, we may want to bind <c-l>P to tex-[pdflatex]->pdf and <c-l>pdf to
> tex->ps->pdf. This way, we have the choice to use one approach or the
> other at the last moment, with no need to redefine 4 global variables.
>
I prefer using \ll for compiling into everything and just changing
settings on a per-directory basis. I have always been a fan of
polymorphic keys...

> > The latest beta containing the 2 features is available at:
> > http://vim-latex.sourceforge.net/download/latexSuite-multicompile.tar.gz
>
> I had never spent much time on what &efm should be for makeindex or
> bibtex. So, you may need to eventually have a look at this issue.
>
Yes... Should remember to put this on the TODO list.

-- 
Srinath

Re: [Vim-latex-devel] New compiler features!

[Luc H. <her...@fr...>]

Hello,

* On Thu, Aug 28, 2003 at 04:38:03PM -0700, Srinath Avadhanula <sr...@fa...> wrote:
> 2. Automatically handling format dependencies: For example, if you
>    generate pdf documents by first compiling to dvi, then to ps, then
>    to pdf, then latex-suite handles it automatically, if you specify a
>    setting g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'
> http://vim-latex.sourceforge.net/documentation/latex-suite/compiler-dependency.html


I read on this page:
> let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*'
> let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
> let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'

I'd rather use definitions like:
  let g:Tex_CompileRule_tex_dvi = 'latex --interaction=nonstopmode $*'
  let g:Tex_CompileRule_dvi_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
  let g:Tex_CompileRule_ps_pdf = 'ps2pdf $*.ps'

Why ? Because we may prefer to use systematically pdflatex, but
sometimes, for some documents, we may be interrested in ps2pdf because
some particular packages, like pst-uml, are not compatible with
pdflatex.

So, we may want to bind <c-l>P to tex-[pdflatex]->pdf and <c-l>pdf to
tex->ps->pdf. This way, we have the choice to use one approach or the
other at the last moment, with no need to redefine 4 global variables.

> The latest beta containing the 2 features is available at:
> http://vim-latex.sourceforge.net/download/latexSuite-multicompile.tar.gz

I had never spent much time on what &efm should be for makeindex or
bibtex. So, you may need to eventually have a look at this issue.

-- 
Luc Hermitte
http://hermitte.free.fr/vim/

Re: [Vim-latex-devel] New compiler features!

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

On Thu, 28 Aug 2003, Srinath Avadhanula wrote:

> Two new features have been added to latex-suite:
>
I incorporated both these features into the main trunk, because
I beleive that both these features are pretty "safe", i.e will not break
the original functionality.

The latest developement release on the latex-suite download page
contains these additions.

Srinath

[Vim-latex-devel] New compiler features!

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

Hello,

Two new features have been added to latex-suite:

1. Generating certain output formats correctly by automatically
   compiling multiple times. This is a feature which has been mostly
   picked up from tex-tools.vim by Luc Hermitte and massaged
   stylistically and otherwise to fit nicely in with the rest of
   latex-suite. Also, if python is available, then it will use python
   instead of vimscript for certain functions which enable it to be
   faster and also avoid opening unused buffers.

http://vim-latex.sourceforge.net/documentation/latex-suite/compiling-multiple.html

2. Automatically handling format dependencies: For example, if you
   generate pdf documents by first compiling to dvi, then to ps, then to
   pdf, then latex-suite handles it automatically, if you specify
   a setting
   g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'

http://vim-latex.sourceforge.net/documentation/latex-suite/compiler-dependency.html

The latest beta containing the 2 features is available at:

vim-latex.sourceforge.net/download/latexSuite-multicompile.tar.gz

This is a release from the latex-multi-compile branch in the latex-suite
CVS tree. Those interested can directly get it from there. Any feedback
is appreciated. I am aiming at merging these changes into the main trunk
wihin the next week.

Thanks,
Srinath

[Vim-latex-devel] filebrowser.vim

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

Hello,

Recently, we have been using a modified version of explorer.vim to work
along with texviewer.vim to accomplish file name completion in
latex-suite via the <F9> key. I have never been keen on maintaining
a seperate copy of explorer.vim. First of all, it conflicts with the
standard vim distribution. There are other problems too, but I will not
spend time on that here.

Therefore, I wrote up a very lightweight replacement of explorer.vim
called filebrowser.vim. It strips most of the features of explorer.vim
away and provides a very basic "API" for the rest of latex-suite.
Basically, it functions more like a library component rather than
a dedicated plugin. I have had to change texviewer.vim to use this also.
Anyway, a new branch with this has been created as filebrowser-branch.

Use

cvs -d:pserver:ano...@cv...:/cvsroot/vim-latex co -r \
filebrowser-branch vimfiles

to get the branch from cvs. Please report any issues. Also, is there
anything else which is lacking in this branch which was available in the
previous way of using explorer.vim?

If I do not receive any bug-reports, I would really like to remove
explorer.vim from latex-suite's cvs tree and use filebrowser.vim
instead.

Thanks,
Srinath

Re: [Vim-latex-devel] Problems with viewing using the latex-suite and gvim

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

Dnia Tuesday 26 of August 2003 17:38, Norbert Strobel napisał:
> Dear Sirs:
>
> My name is Norbert Strobel, and I have problems when viewing
> pdf and ps files out of gvim using the latex-suite. That's why
> I checked out the associated FAQ's at =
> http://vim-latex.sourceforge.net/index.php?subject=3Dfaq
>
> Unfortunately, I could not find an answer to my problem, because the =
> answer to
> "Compiling/Viewing does not seem to work for me. My gvim hangs/does =
> nothing."
> only seems to address compiling. However, my problem is viewing, since =
> compiling
> works well. I can compile into *.dvi, *.ps, and *.pdf. However, I can =
> only view=20
> *.dvi Files at the moment. Here are my viewing rules:
>
> TexLet g:Tex_ViewRule_ps  =3D 'gsview32'
> TexLet g:Tex_ViewRule_pdf =3D 'AcroRd32'=20
> TexLet g:Tex_ViewRule_dvi =3D 'yap -1'
>
Could you try to write _full_ path? I remember Windows version of gvim has/
had problems with that.

m.

Re: [Vim-latex-devel] Problems with viewing using the latex-suite and gvim

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

Hi Norbert,

> My name is Norbert Strobel, and I have problems when viewing
> pdf and ps files out of gvim using the latex-suite. That's why
> I checked out the associated FAQ's at =
> http://vim-latex.sourceforge.net/index.php?subject=3Dfaq
>
I will make a FAQ entry for the viewing thing too. Thanks for all the
information! I will need another piece of information to make headway
though..

First of all, please update to the latest version just so we are both on
the same page. There was a bug-fix with spaces not being escaped on
shared drives. If the bug does not go away, let me know what happens
when you do

:TTarget pdf
:call ViewLaTeX()

from the vim command line. This should spawn a shell which generates the
command. You should be able to see what problem the command prompt has
with the command then.

Srinath

[Vim-latex-devel] Problems with viewing using the latex-suite and gvim

[Norbert S. <Nor...@st...>]

Dear Sirs:

My name is Norbert Strobel, and I have problems when viewing
pdf and ps files out of gvim using the latex-suite. That's why
I checked out the associated FAQ's at =3D
http://vim-latex.sourceforge.net/index.php?subject=3D3Dfaq

Unfortunately, I could not find an answer to my problem, because the =3D
answer to
"Compiling/Viewing does not seem to work for me. My gvim hangs/does =3D
nothing."
only seems to address compiling. However, my problem is viewing, since =
=3D
compiling
works well. I can compile into *.dvi, *.ps, and *.pdf. However, I can =
=3D
only view=3D20
*.dvi Files at the moment. Here are my viewing rules:

TexLet g:Tex_ViewRule_ps  =3D3D 'gsview32'
TexLet g:Tex_ViewRule_pdf =3D3D 'AcroRd32'=3D20
TexLet g:Tex_ViewRule_dvi =3D3D 'yap -1'

I did include gsview32 and AcroRd32 into my Path, i.e., I can call
these programs from the cmd shell on the command line and get
an output. Unfortunately, when I set TTarget to pdf and compile
to pdf, 'lv' will not display anything. The same happens when
I set TTarget to ps. The strange thing is that when I set TTarget=3D20
to dvi, compiling and viewing (using yap) both work. How
come that I have problems with gsview32 and AcroRd32?

Thank you very much for any help. Below you find some
more information about what's going on when I latex a file.

Kind Regards,

  Norbert =3D20

P.S.
:call RunLaTeX() produces the following output on my Win2000 PC:
:!latex --src-specials \nonstopmode \input{manuscript}  > =3D
C:/DOCUME~1/norbert/LOCALS~1/Temp/VIe4A.tmp

P.S.S.
I am using MikTex 2.2.2.

P.S.S.S.
It may be very helpful, if your FAQ item could present a similiar=3D20
sequence of checks for viewing as already provided for compiling

[Vim-latex-devel] Re: Bug#206050: vim-latexsuite File explorer won't work

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

On Tue, 19 Aug 2003, Artur R. Czechowski wrote:

> > 1. Make a release of latex-suite which restores plugin/explorer.vim to
> >    exactly the one which ships with vim without any of our
> >    modifications.
> For me there is no reason to do it. Uninstalling a vim-latexsuite
> automagically restores an original vim's files (there are two for now:
> plugin/explorer.vim and compiler/tex.vim).
>
Okay... this simplifies things. Just make a release which does not
contain a file called plugin/explorer.vim then. I haven't heard from
Mikolaj since I wrote him a few days back. Looks like hes on a break or
otherwise busy.

I was thinking of making a very concentrated extract from explorer.vim
which basically works specifically for just choosing files. Something
like :ChooseFile which will be a _lot_ simpler than explorer.vim and
therefore can be a lot smaller.

> > 2. After that, subsequent releases of latex-suite will not contain
> >    a file called plugin/explorer.vim. If we do require some
> >    functionality which compels us to use a modified explorer.vim, then
> >    we will call it something different say plugin/tex_explorer.vim and
> >    do the modifications there. However, I maintain that it will be much
> >    nicer if we can do without a duplicate.
> What was the reasons to create a splitted version of this file? I have
> looked into diff beetwen original file and yours one, there are quite some
> differences...

I beleive that there was something to be done with project files or
something. However, that part of the project is not "active" right now.
At some point, Mikolaj planned on letting users also define a
g:Tex_ProjectFiles variable or the like which explicitly lists the files
used in the current project. As of now, this does not seem to be
necessary because g:Tex_BIBINPUTS and g:Tex_TEXINPUTS seem to be able to
handle everything which latex itself can recognize.

Srinath

> PS. Hmm... I should update my Geek Code...

Oops. Didn't get this :)

[Vim-latex-devel] Bug#206050: Info received (was Bug#206050: vim-latexsuite File explorer won't work)

[<ow...@bu...>]

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the package maintainer(s)
and to other interested parties to accompany the original report.

Your message has been sent to the package maintainer(s):
 ar...@he... (Artur R. Czechowski)

If you wish to continue to submit further information on your problem,
please send it to 20...@bu..., as before.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the Bug-tracking system.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

[Vim-latex-devel] Re: Bug#206050: vim-latexsuite File explorer won't work

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

Hello

Bugfix is prepared and waiting for upload. I suggest to move future
discussion to v-...@sf... (Cc and Reply-to set).

On Mon, Aug 18, 2003 at 03:21:43PM -0700, Srinath Avadhanula wrote:
> On Mon, 18 Aug 2003, Artur R. Czechowski wrote:
> > Yes, I am enlighted :) What are your plans about :edit <dir> in future
> > versions of exlporer.vim? May I assume that you restore this functionality
> > in vim-latex's version of explorer.vim?
> I am hoping that in the long term, the default explorer.vim will be left
> completeley untouched and we will be able to write some wrapper
> functions around it to access its functionality when needed. In the
> short term, something like this might be needed:

> 1. Make a release of latex-suite which restores plugin/explorer.vim to
>    exactly the one which ships with vim without any of our
>    modifications.
For me there is no reason to do it. Uninstalling a vim-latexsuite
automagically restores an original vim's files (there are two for now:
plugin/explorer.vim and compiler/tex.vim).

> 2. After that, subsequent releases of latex-suite will not contain
>    a file called plugin/explorer.vim. If we do require some
>    functionality which compels us to use a modified explorer.vim, then
>    we will call it something different say plugin/tex_explorer.vim and
>    do the modifications there. However, I maintain that it will be much
>    nicer if we can do without a duplicate.
What was the reasons to create a splitted version of this file? I have
looked into diff beetwen original file and yours one, there are quite some
differences...

Cheers
	Artur

PS. Hmm... I should update my Geek Code...
-- 
Artur R. Czechowski <ar...@he...>
GCS dpu--(++) s-:-- a- C++ UL++++$ P++ L++ E--- W++$ N+(-) K- w---
!O M- V? Y? PGP++ t? !5 X- R !tv b+++ DI+++ D G e* h++ y+

[Vim-latex-devel] Gvim+latexSuite for TeXLive8

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

Hello,

http://skawina.eu.org/mikolaj/gvim62-lS-tl8.exe

This is special distribution of Vim (6.2.21) for TeXLive8.
In installer is latexSuite 20030726.

m.

Re: [Vim-latex-devel] How to customize latex-suite when installed system-wide

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

I have actually made another dated release with this patch and a couple
of other bugs I caught while fixing this.

On Sat, 26 Jul 2003, Artur R. Czechowski wrote:

> I think, yes. For now default 'rtp' compiled in vim is:
> runtimepath=~/.vim,/etc/vim,/usr/share/vim/vimfiles,/usr/share/vim/vim61,/usr/share/vim/vimfiles/after,~/.vim/after
>
> I Cc'ed this mail to Jakub Turski (which whom I work on draft of Debian Vim
> Scripts Policy[1]).
>
Good. Its very helpful to have ~/.vim or ~/vimfiles as the first
directory. I haven't really given too much though about
/usr/share/vim/vim61/addons. What problem were you trying to solve with
the introduction of this directory in the 'rtp'? I would advice you to
take into consideration how vim behaves on other platforms. If you
create a system which is specific to deb, then package writers will have
to write additional code to handle it. So even if you add the addons/
directory, please make sure it works transparently, i.e, the script
writer doesn't have to bother that his script/package is installed in
it...

> > If both 1 and 2 hold, the fix is pretty simple, the following patch
> > should work.
> Thank you for this! I'll add this patch to current Debian vim-latesuite
> release.
>
Just get the latest cvs. I patched it there.

Regards,
Srinath

Re: [Vim-latex-devel] How to customize latex-suite when installed system-wide

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

Hello

On Sat, Jul 26, 2003 at 11:42:04AM -0700, Srinath Avadhanula wrote:
> For future reference, should I assume that bugs from @bugs.debian.org will
> always have a system wide latex-suite installation?
Yes, that's right.

> Its a bug. main.vim currently checks for a texrc file in ../tex/texrc,
> which in the case of the system wide installation is in
> /usr/share/vim/vim61/ftplugin/tex/texrc (I would think), which I am
> assuming is not writable by a normal user... Actually, your suggestion
> of ~/.vim/ftplugin/tex/texrc.vim works because vim automatically sources
> this file on opening a .tex file and I am assuming that ~/.vim is
> before /usr/share/vim/vim61 in your 'runtimepath' setting. This
> workaround will therefore not work on local installations.
> 
> A couple of questions before I begin to fix it:
> 
> 1. Can I assume that the 'rtp' will always contain ~/.vim before
>    /usr/share/vim/vim61?
I think, yes. For now default 'rtp' compiled in vim is:
runtimepath=~/.vim,/etc/vim,/usr/share/vim/vimfiles,/usr/share/vim/vim61,/usr/share/vim/vimfiles/after,~/.vim/after

I Cc'ed this mail to Jakub Turski (which whom I work on draft of Debian Vim
Scripts Policy[1]).

> 2. Will latex-suite always be installed in ftplugin/ under some
>    directory in the 'rtp'? In a mail sent to vi...@vi... about the
>    installation policy, I got the feeling that you might be installing
>    under /usr/share/vim/vim61/addons or something.
In presence - yes, it will be installed in ftplugin. But in future
it is possible, that this draft of DVSP becomes standard. Then
plugins will be installed under /usr/share/vim/addons. But precendce
of ~/.vim before /usr/share/vim/addons will be saved.

OTOH, Jakub and me rethink a side-effects of installing plugins in separate
directory.

> If both 1 and 2 hold, the fix is pretty simple, the following patch
> should work.
Thank you for this! I'll add this patch to current Debian vim-latesuite
release.

> > For documentation issue please Cc: all correspondence regarding this
> > subject to http://bugs.debian.org/202955
> copy to an http:// address? :-) you mean the 20...@bu...
> right?
Right. I think I should sleep more :)

> Thanks for setting up this very neat bug tracking system.
This BTS is native to all Debian packages.

Cheers
	Artur

[1] http://yacoob.dnsalias.net/sakwa/vim-policy.txt
-- 
zapamiętaj, że ludzie i tak o Tobie nie myślą, a jeśli już myślą to
po to, żeby poczuć, iż są lepsi niż Ty
					/MrK/

Re: [Vim-latex-devel] How to customize latex-suite when installed system-wide

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

Hello,

I received the mails mentioning this from @bugs.debian.org, but didn't
realize that the problem was due to a system wide installation. For
future reference, should I assume that bugs from @bugs.debian.org will
always have a system wide latex-suite installation?

On Sat, 26 Jul 2003, Artur R. Czechowski wrote:

> The problem is that latex-suite is installed system-wide (in this case in
> /usr/share/vim/vim61). Comments in latex-suite's texrc claim, that
> in order to customize this package the user should copy it to
> ~/.vim/ftplugin/tex/texrc (in 20030605) or to ~/.vim (in 20030724).
>
This is a documentation bug. The relevant comment in texrc should read
as:

"              1. Copy this file into $VIMFILES/ftplugin/tex/texrc
"                 and edit the values in that file.
"                 $VIMFILES is ~/.vim for UNIX systems and ~/vimfiles for
"                 WINDOWS systems.  Copying it to some arbitrary location even
"                 within some other location in your 'runtimepath' will not
"                 work.

Therefore the local texrc should reside in
~/.vim/ftplugin/tex/texrc

> Regardles of the package's version and file's place it does not work.
> I have done some tests and there is only one case when it works: when
> the content of texrc is in file ~/.vim/ftplugin/tex/texrc.vim.
>
> I wonder if it is a lack in documentation or a bug in the package?
>
Its a bug. main.vim currently checks for a texrc file in ../tex/texrc,
which in the case of the system wide installation is in
/usr/share/vim/vim61/ftplugin/tex/texrc (I would think), which I am
assuming is not writable by a normal user... Actually, your suggestion
of ~/.vim/ftplugin/tex/texrc.vim works because vim automatically sources
this file on opening a .tex file and I am assuming that ~/.vim is
before /usr/share/vim/vim61 in your 'runtimepath' setting. This
workaround will therefore not work on local installations.

A couple of questions before I begin to fix it:

1. Can I assume that the 'rtp' will always contain ~/.vim before
   /usr/share/vim/vim61?

2. Will latex-suite always be installed in ftplugin/ under some
   directory in the 'rtp'? In a mail sent to vi...@vi... about the
   installation policy, I got the feeling that you might be installing
   under /usr/share/vim/vim61/addons or something.

If both 1 and 2 hold, the fix is pretty simple, the following patch
should work.

$ cvs diff -c main.vim
Index: main.vim
===================================================================
RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/latex-suite/main.vim,v
retrieving revision 1.44
diff -c -r1.44 main.vim
*** main.vim    25 Jul 2003 01:22:27 -0000      1.44
--- main.vim    26 Jul 2003 18:35:50 -0000
***************
*** 28,37 ****
  " these lines need to be outside the function.
  let s:path = expand('<sfile>:p:h')
  " set up personal defaults.
! let s:up_path = expand('<sfile>:p:h:h')
! if filereadable(s:up_path.'/tex/texrc')
!       exe "so ".s:up_path.'/tex/texrc'
! endif
  " set up global defaults.
  exe "so ".s:path.'/texrc'

--- 28,34 ----
  " these lines need to be outside the function.
  let s:path = expand('<sfile>:p:h')
  " set up personal defaults.
! runtime ftplugin/tex/texrc
  " set up global defaults.
  exe "so ".s:path.'/texrc'


> For documentation issue please Cc: all correspondence regarding this
> subject to http://bugs.debian.org/202955

copy to an http:// address? :-) you mean the 20...@bu...
right?

> Regards
> 	Artur

Thanks for setting up this very neat bug tracking system.

[Vim-latex-devel] How to customize latex-suite when installed system-wide

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

Hello

Please take a look at:
http://bugs.debian.org/202955

The problem is that latex-suite is installed system-wide (in this case in
/usr/share/vim/vim61). Comments in latex-suite's texrc claim, that
in order to customize this package the user should copy it to
~/.vim/ftplugin/tex/texrc (in 20030605) or to ~/.vim (in 20030724).

Regardles of the package's version and file's place it does not work.
I have done some tests and there is only one case when it works: when
the content of texrc is in file ~/.vim/ftplugin/tex/texrc.vim.

I wonder if it is a lack in documentation or a bug in the package?

For documentation issue please Cc: all correspondence regarding this
subject to http://bugs.debian.org/202955

Regards
	Artur
-- 
Jeden Celeron kompa nie czyni
	/z pamiętnika administratora/

RE: [Vim-latex-devel] bug in compiler/tex.vim

[PAN S. <Shi...@ne...>]

Thanks.

>===== Original Message From Srinath Avadhanula <sr...@fa...> =====
>On Wed, 23 Jul 2003, PAN Shizhu wrote:
>
>> You defined a character which looks like a reversed `!' as the delimeter of
>> global var g:Tex_IgnoredWarnings, but this character will definetely cause
>> problem on many systems (mainly non-latin systems such as Chinese, Japanese
>> and Korean).
>
>Okay the problem with the inverted '!' character causing i8n problems is
>fixed in the latest dated release. Get it from the latex-suite download
>page.
>
>Srinath