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

[Vim-latex-devel] vim latex on mandrake 8.0 (vim 6.0av beta)

[Jason S. <st...@ur...>]

Thanks for producing a tool that fits my needs!

The only problem I had was when attempting to use an insert
mode map (eg. ECE) I would get an error about an undefined 
function 'cursor'. I traced it back to line ~698 of 
imap.vim. After commenting out the line, insert mode maps 
seem to work fine.

Am I breaking vim latex or is there a more elegant fix?

Jason Stein
182 Gladmer Park
Regin, SK S4P 2W9
Canada
st...@te...

Re: [Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Benji F. <be...@me...>]

Peter Karp wrote:
> Hi Benji and Srinath,
> 
> I'll answer your two e-mails in one:

      Thanks.

>>But I am quite unclear about how exactly they process the xml source to
>>generate the various formats. It looks like they would use the docbook
>>xsl stylesheets available at
>>
>>http://docbook.sourceforge.net/projects/xsl/
> 
> I'm not sure about that. Michael can answer that.

      I hope he can find time to answer.

>>Since vim-help is plain text, it will be in general hard to create
>>stylesheets for it, because we will have to do all the rendering
>>ourselves. 
> 
> I hope that it won't be that hard, because the stylesheet for the plain
> ascii text output could be used as a starting point.

      That sounds promising.

>>Therefore, it is of importance to know how many elements of
>>the docbook DTD definition the tex-refs project uses. Each new element
>>used will be more work.
> 
> As far as I've understand the number of elements won't add too much work,
> because many can be handled the same way to create a simple ascii output.
> 
> I'm more worried if it's hard to create a stylesheet which creates an
> output as half as nice as the very good (in terms of ease of reading)
> formatted Vim help files. :-)
[snip]

> If you don't mind it would be great to subscribe to the tex-refs mailing
> list, so it's easier to reach everyone "at once". [snip]

      I just subscribed.

> I guess Michael is right and it's easier to create an XSLT transformation
> instead of writing a Vim macro (awk or whatever script) to do all the
> formatting, but maybe I'm wrong -- especially considering that you both
> have experience to write vim macros, but not with XSLT.

      I am willing to learn a new tool if it seems like the right one 
for the job.

> What do you think about those two options? Which way do you think is the
> best way to go? Are there others who are interested in an XML to Vim help
> converter (besides tex-refs)? As XML is gaining more ground each day it
> might be useful in the future for others too?

      We are thinking of writing the documentation for LaTeX Suite in 
XML format, so that we can get LaTeX, HTML, and Vim-help output.  If it 
works out, we can post a link on http://vimdoc.sourceforge.net/ in case 
others find it useful.

					--Benji

[Vim-latex-devel] Re: tex-refs project and xml to vim-help conversion

[Peter K. <pma...@ka...>]

Hi Benji and Srinath,

I'll answer your two e-mails in one:

> I downloaded 0.2.1 of the tex-refs xml source. It looks like you are
> using the DocBook DTD.

Yes.

> But I am quite unclear about how exactly they process the xml source to
> generate the various formats. It looks like they would use the docbook
> xsl stylesheets available at
> 
> http://docbook.sourceforge.net/projects/xsl/

I'm not sure about that. Michael can answer that.

> Since vim-help is plain text, it will be in general hard to create
> stylesheets for it, because we will have to do all the rendering
> ourselves. 

I hope that it won't be that hard, because the stylesheet for the plain
ascii text output could be used as a starting point.

> Therefore, it is of importance to know how many elements of
> the docbook DTD definition the tex-refs project uses. Each new element
> used will be more work.

As far as I've understand the number of elements won't add too much work,
because many can be handled the same way to create a simple ascii output.

I'm more worried if it's hard to create a stylesheet which creates an
output as half as nice as the very good (in terms of ease of reading)
formatted Vim help files. :-)

> For a simple vim help file itself, we need not more than a couple of
> elements:
> 
> 1. table
> 2. option
> 3. tag
> 4. para
> 
> and maybe a few more.

I'm not sure which option and tag you refer to. You don't mean the help
tags which are generated, do you?

>       A while ago, you wrote to the vim-latex group, asking for a 
> volunteer to work on an XML-to-vim-help converter.

I've forwarded your e-mail to Michael (at the tex-refs mailing list). As
I've written he's pretty busy these days, but I hope he can find some time
to give us a few pointers.

If you don't mind it would be great to subscribe to the tex-refs mailing
list, so it's easier to reach everyone "at once". I personally had started
to improve upon the LaTeX reference which Mikolaij prepared to the Vim help
format. I myself have no XML experience. I've started to learn about
XML/XSL and so on, so that I can better contribute to the project.

Have you already taken a look into the readme files of the source file from
tex-refs? Some questions are answered there already. But I myself still
need to see/learn which tags are used in the XML source and to think about
how they should be translated into the Vim help format.

I guess Michael is right and it's easier to create an XSLT transformation
instead of writing a Vim macro (awk or whatever script) to do all the
formatting, but maybe I'm wrong -- especially considering that you both
have experience to write vim macros, but not with XSLT.

The next best bet would be to use the text output format and reformat that
to the Vim help format. That's not as nice as doing a direct translation,
but might be a much easier solution -- more a (I hope so) quick hack to
have the information at least inside vim so that the help tags file can be
generated.

What do you think about those two options? Which way do you think is the
best way to go? Are there others who are interested in an XML to Vim help
converter (besides tex-refs)? As XML is gaining more ground each day it
might be useful in the future for others too?

Thanks for your efforts to help us to get the tex-references accesible
direct inside Vim :-)

Regards
Peter

Re: [Vim-latex-devel] Re: Bug in vim-latex

[Benji F. <be...@me...>]

Srinath Avadhanula wrote:
> On Thu, 30 Jan 2003, Benji Fisher wrote:
> 
> 
>>      I see that messages from the list now have a Reply-To line.  Much
>>better!
>>
> 
> Actually, I did that manually last time but I've changed the admin
> preferences on the list now so all mails get a Reply-To line (I
> hope).... I hope most people remember to include the original poster in
> the reply when we get a mail from a person not subscribed to the list...

      It seems to be working.  I think I am pretty aware of when the 
poster is an "outsider."  Time will tell if I live up to this.

>>      I tried this, and it worked as expected.  Either that other user
>>has addded an IMAP (ending in "1" or "2") or something else is causing
>>the problem.  The reason I rushed to answer is that I, too, thought it
>>might be an IMAP problem ...
> 
> 
> Hmm... are you sure you tested with the latest version of latex-suite?
> The latest version "protected" a few letters against expansion at the
> beginning of `` and unfortunately, I "protected" the space as well...
> 
> But even if you were using an older version,
>     :iab 12 twelve
> still doesn't work when you press something like 12/ (and '/' is not in
> 'iskeyword' because `/ is mapped to \frac{}{}).

      Yes, that could be the problem.  Let's see what the OP says in 
response to my post on the vim users' list.

>>>I haven't thought about how to take care of this problem... If it were
>>>a map, we could have used Charles Campbell's SaveMaps() strategy, but
>>>I do not know of an equivalent set up with abbreviations... Ofcourse, we
>>>should in the meanwhile, put up a warning in bright red somewhere saying
>>>that people who use latex-suite better use IMAP() instead of iab... Does
>>>anyone know of something like hasabto()?
>>
>>      I think there are three parts to the solution:
>>
>>(1) As you say, document it.
>>(2) Advise users to replace :iab's with IMAP()'s if they are going to
>>use imaps.vim .  This is the advice I gave Preben.
> 
> 
> Yes. I'll put these in the install directions.
> 
> 
>>(3) Make the map that calls IMAP_LookupCharacter() buffer-local.  I
>>already tried this, but I did not realize that IMAP() was being called
>>only once.  The hard part will be calling IMAP() on every FileType tex
>>event (or another autocommand that Latex Suite sets up).
>>
> 
> I think thats a good idea for the long term... Let's think about it.

      OK.

					--Benji

Re: [Vim-latex-devel] Re: Bug in vim-latex

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

On Thu, 30 Jan 2003, Benji Fisher wrote:

>       I see that messages from the list now have a Reply-To line.  Much
> better!
>
Actually, I did that manually last time but I've changed the admin
preferences on the list now so all mails get a Reply-To line (I
hope).... I hope most people remember to include the original poster in
the reply when we get a mail from a person not subscribed to the list...

>       I tried this, and it worked as expected.  Either that other user
> has addded an IMAP (ending in "1" or "2") or something else is causing
> the problem.  The reason I rushed to answer is that I, too, thought it
> might be an IMAP problem ...

Hmm... are you sure you tested with the latest version of latex-suite?
The latest version "protected" a few letters against expansion at the
beginning of `` and unfortunately, I "protected" the space as well...

But even if you were using an older version,
    :iab 12 twelve
still doesn't work when you press something like 12/ (and '/' is not in
'iskeyword' because `/ is mapped to \frac{}{}).

> > I haven't thought about how to take care of this problem... If it were
> > a map, we could have used Charles Campbell's SaveMaps() strategy, but
> > I do not know of an equivalent set up with abbreviations... Ofcourse, we
> > should in the meanwhile, put up a warning in bright red somewhere saying
> > that people who use latex-suite better use IMAP() instead of iab... Does
> > anyone know of something like hasabto()?
>
>       I think there are three parts to the solution:
>
> (1) As you say, document it.
> (2) Advise users to replace :iab's with IMAP()'s if they are going to
> use imaps.vim .  This is the advice I gave Preben.

Yes. I'll put these in the install directions.

> (3) Make the map that calls IMAP_LookupCharacter() buffer-local.  I
> already tried this, but I did not realize that IMAP() was being called
> only once.  The hard part will be calling IMAP() on every FileType tex
> event (or another autocommand that Latex Suite sets up).
>
I think thats a good idea for the long term... Let's think about it.

Srinath

[Vim-latex-devel] The culprit for that bug

[Sumit B. <b....@ie...>]

Hi

Well, by trial and error I have found the culprit for that strange behavi=
or.
Well, my vimrc has this line which caused the strange behavior as mention=
ed in=20
my mail:
       behave mswin

I would like to be on the mailing list. How to join this mailing list? Th=
anks=20
for help in this regard.

Regards
Sumit

Re: [Vim-latex-devel] Re: Bug in vim-latex

[Benji F. <be...@me...>]

      I see that messages from the list now have a Reply-To line.  Much 
better!

Srinath Avadhanula wrote:
> Hello,
> 
> I could reproduce the problem. It looks like
>     :behave mswin
> sets 'selection' to exclusive which breaks imaps.vim. If I put
>     :set selection=inclusive
> at the end of the .vimrc, it works... Thats a short term solution. In
> the long term, we'll make imaps.vim work with this option. I still
> haven't looked at the selection problem, but I suspect thats due to
> 'incrsearch'...

      Good:  at least that one is diagnosed.

> Also, we've got a serious potential problem. imaps.vim breaks iabs.
> (Preben reported this, and I suspect a user who reported that
>     :iab 12 twelve
>  didn't work for him also has the same problem).

      I tried this, and it worked as expected.  Either that other user 
has addded an IMAP (ending in "1" or "2") or something else is causing 
the problem.  The reason I rushed to answer is that I, too, thought it 
might be an IMAP problem ...

> I haven't thought about how to take care of this problem... If it were
> a map, we could have used Charles Campbell's SaveMaps() strategy, but
> I do not know of an equivalent set up with abbreviations... Ofcourse, we
> should in the meanwhile, put up a warning in bright red somewhere saying
> that people who use latex-suite better use IMAP() instead of iab... Does
> anyone know of something like hasabto()?

      I think there are three parts to the solution:

(1) As you say, document it.
(2) Advise users to replace :iab's with IMAP()'s if they are going to 
use imaps.vim .  This is the advice I gave Preben.
(3) Make the map that calls IMAP_LookupCharacter() buffer-local.  I 
already tried this, but I did not realize that IMAP() was being called 
only once.  The hard part will be calling IMAP() on every FileType tex 
event (or another autocommand that Latex Suite sets up).

The point of (3) is that Latex Suite should not be too intrusive for 
non-tex files.  If the user chooses to use imaps.vim for other file 
types, (s)he will have to follow Point (2) for those as well; if not, 
the only changes needed will be for tex files.

					--Benji

Re: [Vim-latex-devel] Re: Bug in vim-latex

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

Hello,

I could reproduce the problem. It looks like
    :behave mswin
sets 'selection' to exclusive which breaks imaps.vim. If I put
    :set selection=inclusive
at the end of the .vimrc, it works... Thats a short term solution. In
the long term, we'll make imaps.vim work with this option. I still
haven't looked at the selection problem, but I suspect thats due to
'incrsearch'...

Also, we've got a serious potential problem. imaps.vim breaks iabs.
(Preben reported this, and I suspect a user who reported that
    :iab 12 twelve
 didn't work for him also has the same problem).

I haven't thought about how to take care of this problem... If it were
a map, we could have used Charles Campbell's SaveMaps() strategy, but
I do not know of an equivalent set up with abbreviations... Ofcourse, we
should in the meanwhile, put up a warning in bright red somewhere saying
that people who use latex-suite better use IMAP() instead of iab... Does
anyone know of something like hasabto()?

Srinath

Re: [Vim-latex-devel] Re: Bug in vim-latex

[Sumit B. <b....@ie...>]

Hi,

> :echo $LANG
en_US.iso885915

>:set encoding
encoding=3Diso-8859-15

> :echo Imap_PlaceHolderStart=20
answer is --                   <+
> :echo Imap_PlaceHolderEnd
answer is --                   +>

I am also attaching the ".vimrc" because as Srinath pointed me changing t=
he=20
first 3 lines to=20
          filetype plugin on
          filetype indnet on
          finish=20
makes it work but ">" is still highlighted.

Regards,
Sumit

On Thu Jan 30 2003 19:27, Benji Fisher wrote:
> Srinath Avadhanula wrote:
> > Hey Sumit!
> >
> > On Wed, 29 Jan 2003, Sumit Bhardwaj wrote:
> >>-I am using Redhat 8.0 with the default gvim version 6.1.
> >>-:set encoding? produces  <iso-8859-15>
> >
> > Hmm... There are other people in the group who have tested latex-suit=
e
> > on that platform... Actually I just tested to make sure and it looks
> > like it works for me...
>
>       I use RH 8.0, and I have 'encoding' set to utf-8 by default.  Wha=
t
> localization are you using?
>
> :echo $LANG
>
> Please reply to all, so that everyone on the list can see your answers.
>
>
>       It looks to me like a problem with the IMAP_Jumpfunc() function
> from plugin/imaps.vim .  What does
>
> :echo Imap_PlaceHolderStart Imap_PlaceHolderEnd
>
> tell you?
>
> HTH=09=09=09=09=09--Benji Fisher

Re: [Vim-latex-devel] Re: Bug in vim-latex

[Benji F. <be...@me...>]

Srinath Avadhanula wrote:
> Hey Sumit!
> 
> On Wed, 29 Jan 2003, Sumit Bhardwaj wrote:
> 
> 
>>-I am using Redhat 8.0 with the default gvim version 6.1.
>>-:set encoding? produces  <iso-8859-15>
> 
> 
> Hmm... There are other people in the group who have tested latex-suite
> on that platform... Actually I just tested to make sure and it looks
> like it works for me...

      I use RH 8.0, and I have 'encoding' set to utf-8 by default.  What 
localization are you using?

:echo $LANG

Please reply to all, so that everyone on the list can see your answers.

>>- No, I haven't done any customization to the latex-suite defaults.
>>
>>The placeholder is always behaving like this for all the commands.
>>>
>>>>When I do 'EIT' in vim using vim-latex what I get is
>>>>   \begin{itemize}
>>>>       \item >
>>>>    \end{itemize} <++>
>>>>and when I do a Ctrl-J it becomes
>>>>     \begin{itemize}
>>>>       \item >
>>>>    \end{itemize} >

      It looks to me like a problem with the IMAP_Jumpfunc() function 
from plugin/imaps.vim .  What does

:echo Imap_PlaceHolderStart Imap_PlaceHolderEnd

tell you?

HTH					--Benji Fisher

[Vim-latex-devel] Re: Bug in vim-latex

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

Hey Sumit!

On Wed, 29 Jan 2003, Sumit Bhardwaj wrote:

> -I am using Redhat 8.0 with the default gvim version 6.1.
> -:set encoding? produces  <iso-8859-15>

Hmm... There are other people in the group who have tested latex-suite
on that platform... Actually I just tested to make sure and it looks
like it works for me...

> - No, I haven't done any customization to the latex-suite defaults.
>
> The placeholder is always behaving like this for all the commands.
>
Okay... maybe you can do a little more debugging:

suppose you change the first three lines of your ~/.vimrc to

   filetype plugin on
   filetype indent on
   finish

(Note the finish just to skip the rest of the .vimrc)
then does latex-suite still behave badly? If the behavior changes, then
it means its some setting in the .vimrc and I'll need to take a look.

Also, just to make sure, when you say:

> > On Wed, 29 Jan 2003, Sumit Bhardwaj wrote:
> > > When I do 'EIT' in vim using vim-latex what I get is
> > >    \begin{itemize}
> > >        \item >
> > >     \end{itemize} <++>
> > > and when I do a Ctrl-J it becomes
> > >      \begin{itemize}
> > >        \item >
> > >     \end{itemize} >

then you mean that you get an extra greater than sign, right? If you
used > to just denote the cursor position, then thats ofcourse a
feature. Did any previous version of latex-suite work without this
problem?

> I have attached the IEEEtran.tex
> <~/.vim/ftplugin/latex-suite/templates/IEEEtran.tex>.

Thanks! I have uploaded it to the CVS tree... It will be included in the
next release.

Thanks!

Srinath

[Vim-latex-devel] Re: Bug in vim-latex

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

Hey Sumit,

On Wed, 29 Jan 2003, Sumit Bhardwaj wrote:

> When I do 'EIT' in vim using vim-latex what I get is
>    \begin{itemize}
>        \item >
>     \end{itemize} <++>
> and when I do a Ctrl-J it becomes
>      \begin{itemize}
>        \item >
>     \end{itemize} >
>

Unfortunately, I cannot seem to reproduce this bug. I am forwarding to
the group hoping someone has some ideas...

- What is your OS?
- What does
    :set encoding?
  give in vim?
- Have you done any customization to the latex-suite defaults?

> Also, I wanted to contribute the template file for IEEE transactions
> template.  (A trivial work).

Thanks! Just email it to the group and one of us will add it.

Thanks,

Srinath

-- 
Srinath Avadhanula
Jan 28 12:52pm
Slang is language that takes off its coat, spits on its hands, and goes
to work.

Re: [Vim-latex-devel] Another problem with: LatexSuite (21.01.03)

[Preben R. <ra...@pv...>]

Benji Fisher <be...@me...> wrote on 28/01/2003 (06:58) :
> 
>      I also failed to reproduce it.  I copied the e-mail into foo.tex 
> and tried entering $$ in Insert mode.  One thought:  what packages do 
> you have (i.e. \usepackage{} lines in the .tex file)?
> 

Odd thing. When I wanted to reproduce the error myself today it doesn't
happen. Now I get $$<++> as I should. Odd. Perhaps I loaded something
yesterday. OK I'll look into it later, have to finish now before the
deadline :-)

Thanks for help

I'll convert the iab's later today.
-- 
Preben Randhol ---------------- http://www.pvv.org/~randhol/ --
"Violence is the last refuge of the incompetent", Isaac Asimov

Re: [Vim-latex-devel] Another problem with: LatexSuite (21.01.03)

[Benji F. <be...@me...>]

Srinath Avadhanula wrote:
> 
> Hello Preben,
> 
> On Tue, 28 Jan 2003, Preben Randhol wrote:
> 
>>quoted below:
>>
>>substances were weighed in a small plastic container on a balance with
>>an accuracy of 0.0001 g. The substance were transfered to the flasks by
>>
>>after hitting $$ I got:
>>
>>substances were weighed in a small plastic container on a balance with
>>   an accuracy of $<++>$<++>0.0001 g. The substance were transfered to the flasks by
>>
>>with the cursor on the 'a' in an and now it was not in insert mode
>>anymore.
>>
> 
> I tried reproducing this, but I couldn't... We'll need more
> information...
> 
> Does this thing with $$ happen everywhere or only in this situation? Are
> there any more specific circumstances which lead to this problem...
> 
> If you do not mind, it will also help if we can work with your .vimrc.
> Often the plugin doesn't account for some setting which makes some
> commands perform differently...
> 
> Another thing: Whats the set-up you have? In particular, I tested it on
> a linux system with encoding=utf8.
> 
> Srinath

      I also failed to reproduce it.  I copied the e-mail into foo.tex 
and tried entering $$ in Insert mode.  One thought:  what packages do 
you have (i.e. \usepackage{} lines in the .tex file)?

				--Benji Fisher

Re: [Vim-latex-devel] Another problem with: LatexSuite (21.01.03)

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

Hello Preben,

On Tue, 28 Jan 2003, Preben Randhol wrote:
> quoted below:
>
> substances were weighed in a small plastic container on a balance with
> an accuracy of 0.0001 g. The substance were transfered to the flasks by
>
> after hitting $$ I got:
>
> substances were weighed in a small plastic container on a balance with
>    an accuracy of $<++>$<++>0.0001 g. The substance were transfered to the flasks by
>
> with the cursor on the 'a' in an and now it was not in insert mode
> anymore.
>
I tried reproducing this, but I couldn't... We'll need more
information...

Does this thing with $$ happen everywhere or only in this situation? Are
there any more specific circumstances which lead to this problem...

If you do not mind, it will also help if we can work with your .vimrc.
Often the plugin doesn't account for some setting which makes some
commands perform differently...

Another thing: Whats the set-up you have? In particular, I tested it on
a linux system with encoding=utf8.

Srinath

[Vim-latex-devel] Another problem with: LatexSuite (21.01.03)

[Preben R. <ra...@pv...>]

I wanted to put $\pm$ in front of the number in the second line of that
quoted below:

substances were weighed in a small plastic container on a balance with
an accuracy of 0.0001 g. The substance were transfered to the flasks by

after hitting $$ I got:

substances were weighed in a small plastic container on a balance with
   an accuracy of $<++>$<++>0.0001 g. The substance were transfered to the flasks by

with the cursor on the 'a' in an and now it was not in insert mode
anymore.

Any idea why this is happening?

-- 
Preben Randhol ---------------- http://www.pvv.org/~randhol/ --
"Violence is the last refuge of the incompetent", Isaac Asimov

Re: [Vim-latex-devel] Problem with iab and LatexSuite (21.01.03)

[Benji F. <be...@me...>]

Preben Randhol wrote:
> My abbreviations won't work when I use LatexSuite now. My file looks
> like this:
> 
> iab gradc         \gradC{}
> iab co32-         CO$_{3}^{2-}$
> iab so42-         SO$_{4}^{2-}$
> iab ca2+          Ca$^{2+}$
> iab ba2+          Ba$^{2+}$
> iab sr2+          Sr$^{2+}$
> iab mg2+          Mg$^{2+}$
> iab co2           CO$_{2}$
> iab h2o           H$_{2}$O
> iab caco3         CaCO$_{3}$
> iab nahco3        NaHCO$_{3}$
> iab na2co3        Na$_{2}$CO$_{3}$
> iab cacl2         CaCl$_{2}$
> iab mgcl2         MgCl$_{2}$
> iab LAB           \label{}
> iab REF           \ref{}
> iab FIG           Figure~\ref{fig:}
> iab '-            {}
> 
> If I remove imaps.vim the iab's work. However if I use an old imaps.vim
> it doesn't work again. So I don't know if it is imaps.vim or some other
> file that is bugging. If I source the iab file for a text file then it
> works.
> 
> Thanks in advance
> 
> PS: If I can do something to help debug please let me know.

      I think that imaps.vim will break most ordinary :imap's.  Try 
replacing your ordinary :iab's with things like

:call IMAP("caco3", "CaCO$_{3}$", "tex")

and so on.  You might even try using the cursor-positioning techniques 
with things like

:call IMAP("LAB", '\label{<++>}<++>', "tex")

HTH					--Benji Fisher

Re[2]: [Vim-latex-devel] tex-refs project and xml to vim-help conversion

[Peter K. <pe...@ka...>]

Hi Srinath and Benji,

thank your for your e-mails. I'm lucky that you like to try to contribute
to our project :-)

(I'm not any longer subscribed to the vim-developer list, so I can't read
posts there, but I'm sending a copy there too).

> I downloaded 0.2.1 of the tex-refs xml source. It looks like you are
> using the DocBook DTD.
> 
> See:
> 	http://www.docbook.org/tdg/en/html/docbook.html

That's right. Michael is maintaining the technical part of tex-refs and
produces the various outpuf formats. He's quite busy these days (with a
move) and I'm personally can't answer all your questions. I hope Michael
will find time to respond in detail soon. Today and tomorrow I don't have
time for a longer answer, but I'll try to answer as many questions as I can
as soon as possible.

May I suggest that all who are interested to take part  subscribe to the
tex-refs mailing list? Then it's automaticly everybody intersted can gets a
copy of the e-mail. The list is low freqency, so you won't get "bombarded"
with too many e-mails ;-)

You can subscribe by sending email to

    tex...@ml...

containing the word subscribe in the subject or body of the email.


All the best
Peter

[Vim-latex-devel] Problem with iab and LatexSuite (21.01.03)

[Preben R. <ra...@pv...>]

My abbreviations won't work when I use LatexSuite now. My file looks
like this:

iab gradc         \gradC{}
iab co32-         CO$_{3}^{2-}$
iab so42-         SO$_{4}^{2-}$
iab ca2+          Ca$^{2+}$
iab ba2+          Ba$^{2+}$
iab sr2+          Sr$^{2+}$
iab mg2+          Mg$^{2+}$
iab co2           CO$_{2}$
iab h2o           H$_{2}$O
iab caco3         CaCO$_{3}$
iab nahco3        NaHCO$_{3}$
iab na2co3        Na$_{2}$CO$_{3}$
iab cacl2         CaCl$_{2}$
iab mgcl2         MgCl$_{2}$
iab LAB           \label{}
iab REF           \ref{}
iab FIG           Figure~\ref{fig:}
iab '-            {}

If I remove imaps.vim the iab's work. However if I use an old imaps.vim
it doesn't work again. So I don't know if it is imaps.vim or some other
file that is bugging. If I source the iab file for a text file then it
works.

Thanks in advance

PS: If I can do something to help debug please let me know.
-- 
Preben Randhol ---------------- http://www.pvv.org/~randhol/ --
"Violence is the last refuge of the incompetent", Isaac Asimov

Re: [Vim-latex-devel] tex-refs project and xml to vim-help conversion

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

Hello,

Sorry for not writing earlier about this...

I downloaded 0.2.1 of the tex-refs xml source. It looks like you are
using the DocBook DTD.

See:
	http://www.docbook.org/tdg/en/html/docbook.html

But I am quite unclear about how exactly they process the xml source to
generate the various formats. It looks like they would use the docbook
xsl stylesheets available at

http://docbook.sourceforge.net/projects/xsl/

But thats about all I know... I do not know the details of which tools
they have used to apply the stylesheets etc. That would be helpful
information.... Actually a quick google search just revealed that
docbook recommends saxon which has a windows installer...

Another thing:

Since vim-help is plain text, it will be in general hard to create
stylesheets for it, because we will have to do all the rendering
ourselves. Therefore, it is of importance to know how many elements of
the docbook DTD definition the tex-refs project uses. Each new element
used will be more work.

For a simple vim help file itself, we need not more than a couple of
elements:

1. table
2. option
3. tag
4. para

and maybe a few more. If you take a look at the tex-refs.xml source, you
will see a much richer xml. Writing a custom xsl stylesheet to convert
that to plain text might be a huge undertaking.

Srinath

On Sun, 26 Jan 2003, Benji Fisher wrote:

> Peter:
>
>       A while ago, you wrote to the vim-latex group, asking for a
> volunteer to work on an XML-to-vim-help converter.  I think we are
> willing to give this a try.  Unfortunately, none of us has much
> experience in XML so far, so we would appreciate some pointers to help
> us get started:  XML, DocBook, XSLT.  Any advice will be appreciated.
>
> 					--Benji Fisher
>

[Vim-latex-devel] Re: your mail

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

Dear Dr. Osman,

On Sun, 26 Jan 2003, Babiker Osman wrote:

> Dear  sir
>
> I have installed laTex suite within vim 6.1.3 at home and office .. at
> home every thing is OK ..  however, at office I could'nt view the
> output I did compiling from the menu first.. then i Press view nothing
> come out ..
>
> Any possible explanations please ...
>
Do you have latex installed on your system? You should be able to do

    :!latex %

from within vim. If the command above gives errors, try to find out if
your PATH environment variable contains the directory in which you have
your latex install.

Another thing:

Try doing

    :call RunLaTeX()

from within vim and see if that gives some error message. If it does,
please get back to me.

Thanks,

Srinath

PS: Please write such mails to vim-latex-devel because you might get an
answer faster.


-- 
Srinath Avadhanula

[Vim-latex-devel] tex-refs project and xml to vim-help conversion

[Benji F. <be...@me...>]

Peter:

      A while ago, you wrote to the vim-latex group, asking for a 
volunteer to work on an XML-to-vim-help converter.  I think we are 
willing to give this a try.  Unfortunately, none of us has much 
experience in XML so far, so we would appreciate some pointers to help 
us get started:  XML, DocBook, XSLT.  Any advice will be appreciated.

					--Benji Fisher

Re: [Vim-latex-devel] label viewing

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

On Thu, Jan 16, 2003 at 03:52:16PM -0800, Srinath Avadhanula wrote:
> I just cooked up something which shows what I mean... Note that this is
> still a very basic version which doesn't have the syncing capability of
> compiler.vim... Eventually, we would like to make the quickfix window
> (in this case, the '--Label Browser---' window) sync with the
> appropriate tex window in preview mode...
> I am attaching a file called labelbrowser.vim. Place that in your
> ftplugin/tex/ directory and then when you either type \ref{ or press
> <F9> in normal mode, a window with the \label matches is shown...
> (You must have some tex files containing \label's in the directory of
> the file being edited).

Hmm. I don't like idea of results caching - what about new \label items?

here is my version. this is rather prototype and needs completion and
polishing but before I do more I'd like to hear what do you think about
it. Your version was causing problems with redrawing of screen.

> On Thu, 16 Jan 2003, Mikolaj Machowski wrote:
> > Great :) The idea to use quickfix is wonderful but I have to read
> > something about it. Also I don't like to use IMAP here. quickfix and
> > preview are some kind "agressive". Making it appears automagically...
> I am including this agressive behavior :) just now just to show its
> possible. Eventually, we might make this an option which is disabled by
> default...

I commented this. IMAP here causes problems.
Try with <F9> in Normal mode

> In the meanwhile, you are welcome to add to the help suggest new modes
> of behavior etc...

What about turning off preview window? This can lead to some problems.
Previewing files opens them and this is not always desired behaviour.

Mikolaj

Re: [Vim-latex-devel] Re: Whats the best way to write vim documentation?

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

On Wed, 22 Jan 2003, Benji Fisher wrote:

>       That looks pretty good for a first attempt.  How about latex and
> html output?  Unless we want to write custom converters for those, too,
> we should figure out what kind of xml tags are already being used, and
> work with those.

Yes... We should definitely use tags which are standard (maybe find out
what the tex refs project uses)... Also, as I said, this was just a
quick hack around the xml.dom.minidom example. I really didn't spend
time learning the right tools and such. On further reading, xslt seems a
bit more tractable than before, but unfortunately, I couldn't get the xt
tools which Luc recommended to work on my box.  (Thats mostly a problem
with my java newbie status).

As far as converting to html goes, I think we might be able to find
xml2html converters on the web... I would think they are pretty
ubiquitous. I could find a few with a google search... I dont know about
xml2latex...

>
> Have you looked at the latex documentation project lately?
>
No. Another thing which should be done. Maybe we should contact Peter
Karp...

>       I am afraid I cannot help much right now.  Remember, the time
> frame I gave when I offered to look into this was "a few weeks."
>
Sorry. I didn't mean to hurry you :) Please take your time...

But I just wanted to get an opinion of whether this approach is worth
pursuing for the long run?

Srinath

Re: [Vim-latex-devel] Re: Whats the best way to write vim documentation?

[Benji F. <be...@me...>]

Srinath Avadhanula wrote:
> 
> PS: It converts
> 
> -----------------------------------%<-----------------------------------
> <option>
> <name>Tex_Leader</name>
> <desc>
> The mappings in latex-suite are by default prefixed with the back-tick
> character. For example, `/ inserts \frac{&lt;++&gt;}{&lt;++&gt;}&lt;++&gt; etc.
> You can change the
> prefix with the following setting.
> ',', '/', '`' are preferred values. '' or '\' will lead to a _lot_ of
> trouble.
> 
> g:Tex_Leader is also used for visual mode mappings for fonts.
> </desc>
> </option>
> -----------------------------------%<-----------------------------------
> 
> to
> 
> ----------------------------------%<----------------------------------
>                                                           *Tex_Leader*
> 
> Tex_Leader
> 
>                     The mappings in latex-suite are by default
>                     prefixed with the back-tick character. For
>                     example, `/ inserts \frac{<++>}{<++>}<++> etc. You
>                     can change the prefix with the following setting.
>                     ',', '/', '`' are preferred values. '' or '\' will
>                     lead to a _lot_ of trouble.
> 
>                     g:Tex_Leader is also used for visual mode mappings
>                     for fonts.
> ----------------------------------%<----------------------------------

      That looks pretty good for a first attempt.  How about latex and 
html output?  Unless we want to write custom converters for those, too, 
we should figure out what kind of xml tags are already being used, and 
work with those.  Have you looked at the latex documentation project lately?

      I am afraid I cannot help much right now.  Remember, the time 
frame I gave when I offered to look into this was "a few weeks."

					--Benji