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

Re: [Vim-latex-devel] CompilerFormat mystery: solved

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

Hey Benji,

I just had a thought. I think that g:Tex_CompilerFormat was once upon
a time the name for g:Tex_CompileRule_dvi!!! (this was before
latex-suite was able to handle different formats and the TCTarget
command). What about changing it back? This way the compiler/tex.vim
will look like:

VIM> " Latex-suite is installed. Use the rule it defines instead of
VIM> " redefining...
VIM> if exists('g:Tex_CompileRule_dvi')
VIM> 	let &l:makeprg = g:Tex_CompileRule_dvi
VIM> else
VIM> 	if has('win32')
VIM> 		let escChars = ''
VIM> 	else
VIM> 		let escChars = '{}\'
VIM> 	endif
VIM> 	" Furthermore, if 'win32' is detected, then we want to set the arguments up so
VIM> 	" that miktex can handle it.
VIM> 	if has('win32')
VIM> 		let options = '--src-specials'
VIM> 	else
VIM> 		let options = ''
VIM> 	endif
VIM> 	let &l:makeprg = current_compiler . ' ' . options .
VIM> 				\ escape(' \nonstopmode \input{$*}', escChars)
VIM> endif

This looks like there are fewer repititions, no?

Srinath


On Sat, 9 Nov 2002, Benji Fisher wrote:

>      I found the problem:  a slightly dusty entry in my _vimrc file,
>
> " Now it is April 2002 and I am using Srinath's latex macros etc.
> let g:Tex_CompilerFormat = ' --src-specials $*'
>
> 					--Benji
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

[Vim-latex-devel] (no subject)

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

[Vim-latex-devel] Re: texrc or tex.vimrc or ...

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

* On Sat, Nov 09, 2002 at 10:49:55AM -0500, Benji Fisher <fis...@bc...> wrote:
> > [1] I'd rather have texrc.vim or .texvimrc instead of just texrc
>      On the vim-dev list, I proposed the extension .vimrc .  I am not
> sure it is worth changing, though.

It is not important. Just a question of taste. As texrc contains VimL,
I'd rather see this fact in its name.

> P.S.  Hermite:  I assume you are subscribed to this list, but I want
> to make sure before I start removing you from the address list.

I am subscribed, Benji.
BTW, You can call me Luc -- hum.. I've some hooks to update, my first
name did not appear in first position on the vim-latex & vim mailiing
lists.

Regards,
-- 
Luc 

[Vim-latex-devel] Re: LaTeX help for Vim

[Hermitte L. <her...@fr...>]

Hello Peter,

* On Sat, Nov 09, 2002 at 09:29:17AM +0100, Peter Karp <pe...@ka...> wrote:
> Michael would prefer an XSLT solution.  
> My qualms are that an XSLT solution would not give as many people the
> chance to do the translations for themselfs

It is not so different from Perl or awk. Not every body using VIM have
these tools installed, nor VIM compiled to accept such script.

> , because the XSLT setup is much more complex (with makefiles and so
> on), 
With XT, i didn't have to run any makefile to install it.
The only makefile I have is to parse the XML and XSLT files when either
of them has changed.


> I'm (at least now) on a Win32 platform and as I understood Michael the
> XML/XSLT tools are not all available for the win platform. 

XT is available on windows (I'm currently under a WinMe + cygwin box),
and here exist other tools, check the xsl faq on:
    http://www.dpawson.co.uk/xsl/xslfaq.html

May be, it lack features, I don't know as I'm a complete newbye with
xslt, but so far it works fine: I've been able to generate xsl:fo files
that I used then to produce PDF files. As the Vim help-filetype format
is very simple, I guess that tools like XT will be fine.

-- 
Luc Hermitte

Re: [Vim-latex-devel] amslatex package

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

On Sat, Nov 09, 2002 at 12:25:08AM -0500, Benji Fisher wrote:
>      I think that amsguide.* is a reference for AMS-TeX; we want 
> AMS-LaTeX.  I have not figured out where (if anywhere) the latex docs 
> are put by Red Hat, but on my CTAN CD I found
> /mnt/cdrom/macros/latex/required/amslatex/math/amsldoc.tex
> which looks like the right documentation.  If you have "A Guide to 
> LaTeX" (Kopka and Daly) then you can also look in Appendix E.
>      And yes, I think the issue is environments, etc, not changes in 
> math mode (although there are a few of those, such as \text{}).

Thanks for link.

Mikolaj

Re: [Vim-latex-devel] More details about changing environments, dots, polymorphism.

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

On Fri, Nov 08, 2002 at 02:27:59PM -0500, Carl Mueller wrote:
> -----------------
> In emacs auctex, and also my package, typing "..." results
> in "\dots".  This is absolutely logical, and it would be a
> shame to leave it out.

SmartDots function do change ... for \cdots in math mode and for
\ldots outside it.

> 3.  On a blank line, in insert mode, <F5> asks the user for
> the name of the environment, and creates the environment.
> But one can also create the environment by typing its name,
> and then typing <F5>.

This functionality existed in praversions of lS. I deleted them because
it looked there is too much ways of creating envs.
I will reintroduce it.

Mikolaj

Re: [Vim-latex-devel] vim.sf.net

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

On Fri, Nov 08, 2002 at 12:41:51PM -0500, Benji Fisher wrote:
> >>Thanks for taking care of the CTAN end... The .zip file on the downloads
> >>page is a bit more stable than the present CVS repository. Can we use
> >>that for the CTAN thingie?
> >
> >Are you sure? Latest commits seems rather necessary for include.
>      There is no need to rush.  Let's upload the next time that we 
> agree we have a stable version.

We have time until April. I thinks then begins work over next TeXLive :)

>      I think the "Reply To" field would be a good idea.  One potential 
> problem:  how do we reply to a user who posts a bug or question to the list?

Hmm. I am using L in mutt.

Mikolaj
-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/
Learn Touch Typing with Vim:
 http://vim.sourceforge.net/script.php?script_id=461

Re: [Vim-latex-devel] Re: bracket macros?

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

On Fri, Nov 08, 2002 at 09:53:51AM -0800, Srinath Avadhanula wrote:
> We have to consolidate the latex-suite structure somewhat so that from
> next time on, adding such contributions becomes seamless (plugins for
> latex-suite?)
> In the meanwhile, I will add the bracketing things manually when I next
> get around to it (unless someone volunteers to do it).
> Also, about amslatex, I am not too familiar with that. Mikolaj, you want
> to take that up? A general doubt which I asked Mikolaj a long time ago:
> is there a tool which parses a .sty file and is able to extract all the
> options, commands etc? This might make supporting new packages easier.

Packages are written in very different ways. From plain plain to latex.
I am afraid the only way is to read documentation of package and do it
by hand :(

I will do amslatex as package. Most math chars are now included in Math
menu.

Mikolaj
-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/
Learn Touch Typing with Vim:
 http://vim.sourceforge.net/script.php?script_id=461

[Vim-latex-devel] texrc or tex.vimrc or ...

[Benji F. <fis...@bc...>]

Hermitte Luc wrote:
> 
> [1] I'd rather have texrc.vim or .texvimrc instead of just texrc

     On the vim-dev list, I proposed the extension .vimrc .  I am not
sure it is worth changing, though.

     After the stable release, I will have a look at overhauling the
compiler system.

					--Benji

P.S.  Hermite:  I assume you are subscribed to this list, but I want to
make sure before I start removing you from the address list.

[Vim-latex-devel] Re: compiler rules

[Hermitte L. <her...@fr...>]

* On Sat, Nov 09, 2002 at 12:33:41AM -0800, Srinath Avadhanula <sr...@ee...> wrote:
> > Or may be just check tex-tools.vim + compiler/tex.vim (my variation
> > of a former Srinath's file) + vim-tex.sh I already manage that and
> > much more.
> compiler/tex.vim has changed since then. It no longer requires
> vim-tex.sh because I found out a way to take care of badly nested '('
> in the LaTeX output. 

I've seen that later, but wasn't sure whether the outgoing messages from
LaTeX were still "reformatted". Now I  know, cool!

> This next thing of automatically handling dependencies is a nice
> thing... I will take a look at it. 
>
> But looking at another persons code and then figuring out what part of
> it overlaps with existing portions, extracting the necessary stuff etc
> takes a while. 

I do completly understand what you mean.

> The fastest way by far of getting things into LaTeX-suite will be to
> maybe attach exactly one file which I can directly read in into some
> part of LaTeX-suite.

To use my system, we need:
- change your compiler/tex.vim to expose TeXSetEFM (needed as in the
  compilation chain I use many programs: bibtex, makeindex, latex, ...).
  TCLevel is too highlevel there from what I understood.
- change the name of the options I need into my tex-tool.vim ; and
  eventually, split the file to define the options in texrc.vim. [1]
- rework the way I change the shell I'm using on windows boxes.
- 2 other files dedicated to a portable way of manipulating pathnames
  and dependancies.
- change tex-tools to support makefiles if any
- update the way *tex outgoing messages are managed in tex-tools.

> However, please dont take this to mean that I (or the other developers)
> will never look at the code. 
 dont worry :-))


[1] I'd rather have texrc.vim or .texvimrc instead of just texrc
-- 
Luc Hermitte

[Vim-latex-devel] CompilerFormat mystery: solved

[Benji F. <fis...@bc...>]

     I found the problem:  a slightly dusty entry in my _vimrc file,

" Now it is April 2002 and I am using Srinath's latex macros etc.
let g:Tex_CompilerFormat = ' --src-specials $*'

					--Benji

[Vim-latex-devel] Re: compiler rules

[Hermitte L. <her...@fr...>]

* On Sat, Nov 09, 2002 at 12:36:01AM -0500, Benji Fisher <be...@me...> wrote:
> >The dependancies for several compilation chains are managed, and the
> >compilation done.
> >    tex-->dvi-->ps ; 
> >       latex + dvips 
> >    tex-->pdf ; 
> >       pdflatex
> >    tex-->dvi-->ps-->pdf
> >       latex + dvips -Ppdf  + pspdf
> >Plus support of bibtex and makeindex if needed.
> >[The user can also choose pdftex, etex, epdflatex, ...]
>      Does that mean that you run latex; latex; bibtex; latex if 
> necessary?  (Or is is latex; bibtex; latex; latex ?)

I check the main loop for tex->dvi/pdf ...

1- if there exist a .idx file, makeindex is run, (a backup for the old
one beeing made)
2- On the first passage in 2-, if there is '\bibdata' in the .aux file,
   bibtex is run 
3- if is there exists a .bbl file, it is backuped
4- run e\=\(pdf\)\=\(la\)=tex
5- same as 2-
6- checks if the .log file ask for a rerun (not always correctly
   working) and check if the .idx has changed ; if either requires it,
   goto 1-

hum... may be I should delete 2- and change 6- to check the need of
re-running based of bibtex changes.

-- 
Luc Hermitte

Re: [Vim-latex-devel] splitting lines

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

Hello Carl,

Thanks for the contribution. I must say, this is the most convenient way
for us to incorporate someone's work. You have already done the work of
distilling out the portion which we need... Most excellent! Thanks!

I just tried it out and it looks pretty cool. However, a (small) bug
report. Try typing the following (pretty pointless drivel).

this is $ a new math environment which is really really really long ...

basically, keep typing in one line without typing in the second $. You
will notice that new lines keep getting inserted with every space after
a while.  Also, it would be nice if the &tw setting is checked before
setting it to zeo and hardcoding in b:tw=79.

Also, since we have contributions from so many people coming in, we need
to step back and figure out a good way to organize LaTeX-suite so that
incorporating contributions from people is seamless...

Here's a suggestion off the top of my head.

For such scripts which are kind of independent of the rest of
LaTeX-suite, we could just put them in the ftplugin/tex/ directory. We
could name such files with a leading "ls_" or something similar to
prevent conflicts... A few questions arise. How will such a "plugin"
know where to put itself in the menus?

So please be a little patient :) This function is definitely going into
LaTeX-suite. However, please give us some time to figure out the best
way to incorporate it. Also, mapping the space bar is pretty intense. We
definitely need to test this a lot before taking so much control away
from vim.

If you wish, you can keep in sync with our conversations and give
suggestions by signing up with the vim-latex-devel mailing list. See

https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

for instructions.

Thanks,
Srinath

On Fri, 8 Nov 2002, Carl Mueller wrote:

> Here is another feature which I would very much like to see.
> Automatic splitting of lines is a great feature for editing.
> On the other hand, it is a pain when an editor splits up a
> math expression $...$.  As part of auctex.vim, I wrote the
> following function(s) which keep $...$ expressions on the
> same line, while allowing the user to keep typing without
> hitting <CR>.
>
> Best wishes,
> Carl Mueller
>
> ----------------------
>
> " The following is necessary for TexFormatLine() and TexFill()
> set tw=0
> [snip]

-- 
Srinath Avadhanula
Nov 9 1:01am
"The chain which can be yanked is not the eternal chain."
		-- G. Fitch

Re: [Vim-latex-devel] Re: compiler rules

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

On Sat, 9 Nov 2002, Hermitte Luc wrote:

> > > think.)  I have tested this on Linux, W95, and OSX.  (On OSX, it
> > > is a problem that compiler/tex.vim ignores the target format,
> > > since most users want pdf instead of dvi.)
>
> Or may be just check tex-tools.vim + compiler/tex.vim (my variation of
> a former Srinath's file) + vim-tex.sh I already manage that and much
> more.
>
compiler/tex.vim has changed since then. It no longer requires
vim-tex.sh because I found out a way to take care of badly nested '(' in
the LaTeX output. It looks like vim can indeed handle two stack
operations based on a single line of compiler output... I have this
thing written down in some cvs log (maybe on my local cvs repository).

This next thing of automatically handling dependencies is a nice
thing... I will take a look at it. But looking at another persons code
and then figuring out what part of it overlaps with existing portions,
extracting the necessary stuff etc takes a while. The fastest way by far
of getting things into LaTeX-suite will be to maybe attach exactly one
file which I can directly read in into some part of LaTeX-suite.
However, please dont take this to mean that I (or the other developers)
will never look at the code. It just means that it will take a lot
longer because it will get put on someones todo list.

Thanks,

Srinath


-- 
Srinath Avadhanula
Nov 9 12:24am
"It's a summons."
"What's a summons?"
"It means summon's in trouble."
		-- Rocky and Bullwinkle

[Vim-latex-devel] LaTeX help for Vim

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

[regarding http://vim-latex.sourceforge.net/ ]

Hi,

quite some time ago I e-mailed with Mikolaj Machowski about LaTeX-help for
Vim. Mikolaj told me about your Vim-Latex Suite, but I lost contact, =
mainly
due limited time during the time I was writing my diploma thesis.

I don't know if any of you is aware of the additions I've made to =
Mikolaj's
LaTeXhelp. I added some stuff, I missed while writing latex documents. You
can grab that updated copy of LaTeX-help at my homepage:

    www.karpfenteich.net

I began that work as a personal "project", just to help me writing latex
stuff. As I noticed that this would be beneficial for other LaTeX/Vim =
users
I posted the uncompleted but already somewhat enlarged version on my
homepage. I have been looking for people willing to contribute, but nobody
seemed to have interest/time/fun/whatever. I got two or three e-mails, but
none of them stayed at the project or even began... :-(

Then I got in contact with Michael Wiedmann who earlier had suggested that
adding content in the Vim specific file format might not be the best idea,
as non-Vim users won't benefit (at least that another "special" conversion
process would be needed). Sure I agreed, but had no better idea for a
source format _and_ most important didn't had the time during the diplom
thesis to learn a new markup language, _just_ to add some missing latex
commands to the help file. Therefore I took the easiest way to improve =
upon
Mikolaj's file.

But after I announced the updated LaTeXhelp file Michael contacted me =
again
and already had begun to work on a translation from the orginal texinfo
files to an XML source!

BTW, such a LaTeX reference is highly needed. In a few days nearly
twothousand people visited my homepage and downloaded the LaTeXhelp =
(either
in Vim help format or as HTML). I just had an announcement on the german
and the international latex newsgroup, so I'm sure that the demand for =
such
a LaTeX reference is high!

Back to Michael. He kept improving the translation process to XML and
finally added my changes/improvements from the LaTeXhelp file for the Vim
help. From then on he maintained the XML sources and added more content. I
personally would have liked to contribute more content (for example for =
the
excellent Koma script or for AMS math stuff). That has been some months =
ago
now and Michal still is keeping on improving the XML source (technically
and adding content). BTW, currently the output formats he generates are
pdf, html, rtf, winhelp and others.

I finished my diploma thesis and thought I'd now have time, but must admit
that looking for a job and improving my knowledge in my field takes most =
of
my time. Still I _would_ have contributed more content to the LaTeXhelp
(which we named tex-refs to show that the aim is to provide a reference =
for
TeX and friends and that it's "more" then the original LaTeX help"), =
_when_
two conditions would have been met:

    1) I need to be able to understand the XML structure and add content
    easy. That was the major problem. I'm still looking for a good
    solution to help me editing the XML source. I must admit that I don't
    find it that easy to take care of the tags. Maybe a "tag list" which
    is allowed in the document would get me going, but I didn't took the
    time to make such a list or even write Vim macros to aid maintaining
    the XML source.
    
    2) Another reason that dramaticly made my wish to improve on that XML
    source file smaller is that up till now no conversion from XML to the
    Vim help file format exists and in the end that's what I want to have.

I only have basic experience with Vim macros and have not been able to =
come
up with a solution myself (at least not in the time span which I could =
have
"afforded" at that moment). Therefore I was looking for a volunteer to =
help
us to write a conversion routine from XML to the Vim help format. We would
be happy about _every_ solution. Perl, XSLT, Vim macros, awk or other
solutions would be a good way to go.

I personally think that a Vim macro might be the most natural way, because
every Vim user who wants the LaTeX help for Vim will surely have Vim ;-)
This approach would allow a user to add personal content to the XML file
and generate a LaTeX help file, where one also could add the descriptions
for personal defined latex macros and so on.

My second best solution would be using awk or Perl, because that's
available on every platform and (especially awk) is easy to install.

Michael would prefer an XSLT solution, because that's what _he_ uses for
the conversion of the other formats. Sure that's also logic. My qualms are
that an XSLT solution would not give as many people the chance to do the
translations for themselfs, because the XSLT setup is much more complex
(with makefiles and so on), then using a plain Vim, awk or perl macro. I'm
(at least now) on a Win32 platform and as I understood Michael the =
XML/XSLT
tools are not all available for the win platform. Also it still would need
bigger efforts to get a running XSLT setup then using one of the other
scripting languages.

So here's my suggestion:

Provide the already existent expanded LaTeXhelp file from my homepage with
the Vim LaTeX-Suite

and even better take a look at the current state of TeX-Refs at:

    http://www.miwie.org/tex-refs/

and see what you/we/all LaTeX/Vim users miss, when we don't have a
conversion between XML and the Vim help format.

When time permits I'll try to write a Vim macro to do the conversion, but
don't hold your breath as I have other projects which are more important
right now (I also don't use LaTeX that much these days...)

When one of you would like to contribute in form of writing a Vim macro =
(or
any other solution mentioned or even a Basic program or one in Assembler
;-) we surely would like to hear from you and the TeX-Refs project and the
LaTeX-Suite would fructify each other.

I'm looking forward to hear your ideas and opinions.

Regards
Peter

Re: [Vim-latex-devel] texmenuconf.vim v. 1.5

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

This is correct... I got a little sloppy. I'll take care of it now.

Srinath

On Fri, 8 Nov 2002, Benji Fisher wrote:

>       I looked at the diff in the latest digest (my last, following
> Srinath's suggestion) and it looks as though some debugging code got
> left in ... or is my vision too blurry at this hour?
>
> 					--Benji
>

-- 
Srinath Avadhanula
Nov 9 12:18am
Expense Accounts, n.:
	Corporate food stamps.

Re: [Vim-latex-devel] Re: compiler rules

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

Hermitte Luc wrote:
> * On Fri, Nov 08, 2002 at 04:18:28PM -0800, Srinath Avadhanula <sr...@fa...> wrote:
> 
>>>think.)  I have tested this on Linux, W95, and OSX.  (On OSX, it is a
>>>problem that compiler/tex.vim ignores the target format, since most
>>>users want pdf instead of dvi.)
>>
> 
> Or may be just check tex-tools.vim + compiler/tex.vim (my variation of
> a former Srinath's file) + vim-tex.sh
> I already manage that and much more.

      The real problem is how to do it in the current structure of latex 
suite, and how that structure should be improved.

> The dependancies for several compilation chains are managed, and the
> compilation done.
>     tex-->dvi-->ps ; 
>        latex + dvips 
>     tex-->pdf ; 
>        pdflatex
>     tex-->dvi-->ps-->pdf
>        latex + dvips -Ppdf  + pspdf
> Plus support of bibtex and makeindex if needed.
> [The user can also choose pdftex, etex, epdflatex, ...]

      Does that mean that you run latex; latex; bibtex; latex if 
necessary?  (Or is is latex; bibtex; latex; latex ?)

					--Benji

Re: [Vim-latex-devel] compiler rules

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

Srinath Avadhanula wrote:
> On Fri, 8 Nov 2002, Benji Fisher wrote:
> 
> 
>>      I have a headache!
>>
> 
> But its worth it :) The compiler rule thing seems to be working quite
> nicely now... Agreed that there is all sorts of wierd program flow as
> you point out in the next para, but at least as of now, its working
> well, even if a little unoptimally.. If you want go ahead and change
> things around so that only compiler/tex.vim defines 'makeprg'.

      I will, but not before the next stable release.

>>      One thing I cannot figure out:  on W95, g:Tex_CompilerFormat is
>>defined, and I cannot figure out where.  This variable is used in
>>compiler/tex.vim and overrides all other methods.
>>
> 
> Thats totally bizzare. I dont get this behavior on my win2k box. Also
> I did the following in the CVS repository:
[snip]
> Are you sure about this?

      One possibility I will have to check (next time I boot Windows 
...) is that I may have defined this at some point, and it may be saved 
in .viminfo .  At lease, we agree that that part of the code is supposed 
to be skipped (unless the user intervenes).

					--Benji

Re: [Vim-latex-devel] amslatex package

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

Mikolaj Machowski wrote:
> On Fri, Nov 08, 2002 at 10:18:23AM -0500, Carl Mueller wrote:
> 
>>This is a plea for vim-latex to support ams-latex.  It is
>>one of the main packages that mathematicians use, and is
>>indicated by 
>>\usepackage{amsmath,amsthm,amsfonts}
>>(along with other possible options such as "amsthm", "amsfonts")
>>vim-latex is certainly a step forward!  Thanks to everyone
>>involved.
> 
> 
> Hmm. Most(?) of special math signs provided by ams-latex are provided
> with Math menu (and probably they stay there). Problem is with
> environments and other things. I will do it in next few days. Is
> amsguide.pdf good as a reference (I don't know ams-latex)?

      I think that amsguide.* is a reference for AMS-TeX; we want 
AMS-LaTeX.  I have not figured out where (if anywhere) the latex docs 
are put by Red Hat, but on my CTAN CD I found
/mnt/cdrom/macros/latex/required/amslatex/math/amsldoc.tex
which looks like the right documentation.  If you have "A Guide to 
LaTeX" (Kopka and Daly) then you can also look in Appendix E.

      And yes, I think the issue is environments, etc, not changes in 
math mode (although there are a few of those, such as \text{}).

					--Benji

[Vim-latex-devel] texmenuconf.vim v. 1.5

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

      I looked at the diff in the latest digest (my last, following 
Srinath's suggestion) and it looks as though some debugging code got 
left in ... or is my vision too blurry at this hour?

					--Benji

*** 71,76 ****
   command! -nargs=0 Ttexrc :call Tex_texrc()
   function! Tex_texrc()
! 	if filereadable(s:up_path.'tex/texrc')
! 		exec 'split '.s:up_path.'tex/texrc'
   		lcd
   	else
--- 71,77 ----
   command! -nargs=0 Ttexrc :call Tex_texrc()
   function! Tex_texrc()
! 	echomsg 's:path = '.s:path.', s:up_path = '.s:up_path
! 	if filereadable(s:up_path.'/tex/texrc')
! 		exec 'split '.s:up_path.'/tex/texrc'
   		lcd
   	else

[Vim-latex-devel] splitting lines

[Carl M. <cm...@ma...>]

Here is another feature which I would very much like to see.
Automatic splitting of lines is a great feature for editing.
On the other hand, it is a pain when an editor splits up a 
math expression $...$.  As part of auctex.vim, I wrote the
following function(s) which keep $...$ expressions on the
same line, while allowing the user to keep typing without
hitting <CR>.

Best wishes,
Carl Mueller

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

" The following is necessary for TexFormatLine() and TexFill()
set tw=0
" substitute text width
let b:tw = 79

"  With this map, <Space> will split up a long line, keeping the dollar
"  signs together (see the next function, TexFormatLine).
inoremap <buffer> <Space> <Space><Esc>:call <SID>TexFill(b:tw)<CR>a
function! s:TexFill(width)
    if col(".") > a:width
	exe "normal a##\<Esc>"
	call <SID>TexFormatLine(a:width)
	exe "normal ?##\<CR>2s\<Esc>"
    endif
endfunction

function! s:TexFormatLine(width)
    normal $
    let length = col(".")
    let go = 1
    while length > a:width+2 && go
    let between = 0
    let string = strpart(getline(line(".")),0,a:width)
    " Count the dollar signs
    let evendollars = 1
    let counter = 0
    while counter <= a:width-1
	if string[counter] == '$' && string[counter-1] != '\'  " Skip \$.
	   let evendollars = 1 - evendollars
	endif
	let counter = counter + 1
    endwhile
    " Get ready to split the line.
    exe "normal " . (a:width + 1) . "|"
    if evendollars
    " Then you are not between dollars.
       exe "normal ?\\$\\| \<CR>W"
    else
    " Then you are between dollars.
	normal F$
	if col(".") == 1
	   let go = 0
	endif
    endif
    exe "normal i\<CR>\<Esc>$"
    let length = col(".")
    endwhile
endfunction

[Vim-latex-devel] Re: bracket macros?

[Hermitte L. <her...@fr...>]

* On Fri, Nov 08, 2002 at 09:53:51AM -0800, Srinath Avadhanula <sr...@fa...> wrote:
> We have to consolidate the latex-suite structure somewhat so that from
> next time on, adding such contributions becomes seamless (plugins for
> latex-suite?)

> In the meanwhile, I will add the bracketing things manually when I
> next get around to it (unless someone volunteers to do it).

My biaised opinion is to use common_brackets.vim also. 
    http://hermitte.free.fr/vim/settings.php3#common_brackets_vim

pro:
* the work is already there
* it is independant of any filetype
* heavily configurable
* I will continue to maintain and support it as a core part of all my
  ftplugins
* a little documentation already exists.

cons:
* it is complex and may need to rewrite/delete some parts from vim-latex
  (only if '{' inserts '}«»', '[' -> ']«»' and may be '(' -> ')«»')
* it requires other plugins having a minor incompatibility with imap.vim
  (the name of the options for the open and close markers)
  BTW, pro: the marker system I propose is more advanced (in term of
  available options, features and complexity) than the variation of
  Gergely's function you include.
* did I said it is a big and quite complex piece.

Last point for tonight (may things to say about templates this weekend),
I prefer having thematic scripts. When something can be done as a plugin
only, it should be so. It helps to define more scalable systems and it
helps the maintenance.


> PS: Hey Luc! Welcome to the group!
:-)) Thanks.

Have a nice week-end.
-- 
Luc Hermitte

[Vim-latex-devel] Re: compiler rules

[Hermitte L. <her...@fr...>]

* On Fri, Nov 08, 2002 at 04:18:28PM -0800, Srinath Avadhanula <sr...@fa...> wrote:
> > think.)  I have tested this on Linux, W95, and OSX.  (On OSX, it is a
> > problem that compiler/tex.vim ignores the target format, since most
> > users want pdf instead of dvi.)

Or may be just check tex-tools.vim + compiler/tex.vim (my variation of
a former Srinath's file) + vim-tex.sh
I already manage that and much more.

The dependancies for several compilation chains are managed, and the
compilation done.
    tex-->dvi-->ps ; 
       latex + dvips 
    tex-->pdf ; 
       pdflatex
    tex-->dvi-->ps-->pdf
       latex + dvips -Ppdf  + pspdf
Plus support of bibtex and makeindex if needed.
[The user can also choose pdftex, etex, epdflatex, ...]

This should save you the headache.
BTW, since our last conversation (Srinath), now I support your
{project}.latexmain *and* g:TexFile (from TKlatex).

-- 
Luc Hermitte

[Vim-latex-devel] Re: More details about changing environments, dots, polymorphism.

[Hermitte L. <her...@fr...>]

* On Fri, Nov 08, 2002 at 02:27:59PM -0500, Carl Mueller <cm...@ma...> wrote:
> I want to emphasize again that the ability to change
> environments is a standard part of the emacs auctex
> package.  

I agree on the pertinence of such feature.

I also a similar feature to change the name of the outer command:
http://hermitte.free.fr/vim/ressources/vimfiles/ftplugin/tex/tex-macros_vim.html
[last function and first commands]

The file also contains:
- some function everybody already knows
- a wrapper that help the user choose the environment he wishes to
  insert -- thanks to a dialog box.
- a function from the old TKlatex to insert sections
- and two commands to change the outer font: ie.
     \nameofthefont{text cursor_here text}
  eases the change of the font for the current context.

-- 
Luc Hermitte

Re: [Vim-latex-devel] compiler rules

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

On Fri, 8 Nov 2002, Benji Fisher wrote:

>       I have a headache!
>
But its worth it :) The compiler rule thing seems to be working quite
nicely now... Agreed that there is all sorts of wierd program flow as
you point out in the next para, but at least as of now, its working
well, even if a little unoptimally.. If you want go ahead and change
things around so that only compiler/tex.vim defines 'makeprg'.

> think.)  I have tested this on Linux, W95, and OSX.  (On OSX, it is a
> problem that compiler/tex.vim ignores the target format, since most
> users want pdf instead of dvi.)

Hmmm.... This will be on my todo list. I assume on yours as well.. It
will be easy enough to check g:Tex_DefaultTargetFormat there...

>       One thing I cannot figure out:  on W95, g:Tex_CompilerFormat is
> defined, and I cannot figure out where.  This variable is used in
> compiler/tex.vim and overrides all other methods.
>
Thats totally bizzare. I dont get this behavior on my win2k box. Also
I did the following in the CVS repository:

.vim > fgrep Tex_CompilerFormat `find . -print` 2>/dev/null

and the only files this finds is compiler/tex.vim, where it occurs as:

VIM> " If the user wants a particular way in which the latex compiler needs to be
VIM> " called, then he should use the g:Tex_CompilerFormat variable. This variable
VIM> " needs to be complete, i.e it should contain $* and stuff.
VIM> if exists('g:Tex_CompilerFormat')
VIM> 	let &l:makeprg = current_compiler.' '.g:Tex_CompilerFormat

Are you sure about this?

-- 
Srinath