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

Re: [Vim-latex-devel] double xdvi opens and compiler error

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

      It certainly looks as though the $* is missing.  Try "\lv" 
(without the quotes, from Normal mode) or use the menu or (for more 
verbose messages)

:call RunLaTeX()

and see if that works.  We should probably set things up so that :make 
will work as expected.

					--Benji

Srinath Avadhanula wrote:
> Hello Fabio,
> 
> This is kinda strange... But we'll work it out soon. Just to eliminate
> the obvious,
> 
> When you open up a tex file, what does
> 	:set makeprg?
> display?
> It should be:
>  	latex \\nonstopmode \\input\{$*\}
> Hopefully, the $* is not missing.
> 
> If you can tell us that, we'll proceed from there. Also, there was a
> syntax error in the ViewLaTeX() command causing those errors and causing
> 2 xdvi's to shoot up.
> 
> Please download the latest from
> 
> 
> Thanks,
> Srinath
> 
> 
> On 12 Nov 2002, Fabio Spelta wrote:
> 
> 
>>Hi.
>>I've just checkout CVS module vimfiles and installed it.
>>Dunno why, but :make still does not works:
>>:!latex  \\nonstopmode \\input\{\} 2>&1| tee /tmp/v105219/4
>>This is TeX, Version 3.14159 (Web2C 7.3.1)
[snip]

Re: [Vim-latex-devel] Re: matching brackets

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

Dear Luc,

On Tue, Nov 12, 2002 at 06:29:08PM +0100, Luc Hermitte wrote:
> * On Tue, Nov 12, 2002 at 08:26:48AM -0500, Carl Mueller <cm...@ma...> wrote:
> > One of my biggest problems used to be mismatched brackets.
> > Now I have macros which automatically type the matching
> > bracket.  For instance, "(" results in "()" with the cursor
> > in between.  Since I sometimes want only one bracket, I made
> > it so that "((" results in "(".  
> > That is faster than typing "(" and then deleting the extra bracket.
> > Not everyone may agree with this idea, so it could be an option.
> 
> Hum ... nice idea. If you don't mind, may be I will use in my
> common_brackets.vim. As the only times I need a single parenthesis are
> within comments or string contexts, I use <C-V> for the remaining rare
> times.
> 
Please feel free to copy anything I've come up with;  
this applies to anyone else who might read these posts.  

Best wishes,
Carl

[Vim-latex-devel] Re: matching brackets

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

* On Tue, Nov 12, 2002 at 08:26:48AM -0500, Carl Mueller <cm...@ma...> wrote:
> One of my biggest problems used to be mismatched brackets.
> Now I have macros which automatically type the matching
> bracket.  For instance, "(" results in "()" with the cursor
> in between.  Since I sometimes want only one bracket, I made
> it so that "((" results in "(".  
> That is faster than typing "(" and then deleting the extra bracket.
> Not everyone may agree with this idea, so it could be an option.

Hum ... nice idea. If you don't mind, may be I will use in my
common_brackets.vim. As the only times I need a single parenthesis are
within comments or string contexts, I use <C-V> for the remaining rare
times.


Personnaly, I'd rather see this as a plugin. Then from any file in
ftplugin/tex, the corresponding pairs are activated.
and the same from ftplugin/vim, ftplugin/c, etc. These bracketing macros
are not interresting in LaTeX documents only.

> I'm listing the code below.  It applies to:
> () [] {} \{\} $$

It reminds me I need to extend my version of CompleteSlash to support
'\%(\)' -- for vim

> || \|\| 
> &&   (when within eqnarray or eqnarray* environments)

cheers,

-- 
Luc Hermitte

[Vim-latex-devel] Re: running latex

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

Hi,

* On Tue, Nov 12, 2002 at 06:31:54AM -0800, Srinath Avadhanula <sr...@ee...> wrote:
> Luc suggested quite a comprehensive algorithm for rerunning latex. If we
> want to go along the route, I think the following is best (Luc's idea).
> [...]
> I did take a look at tex-tools.vim and it already seems to be
> implemented :) 

:-)
BTW, this script should be easy to integrate as it does not require any
other script. Except searchInRuntime that will not be required anymore --
I used it to search for vim-tex.sh. I'll finish my current enhancements
on mu-template, and then I will patch tex-tools to make it integrable
into latex-suite

> So it shouldn't be too big of a deal to get it into latex-suite. Also,
> ref the steps above, what happens if there is no .aux file in step 2
> above like carl says will happen the first time round...

I haven't been very deep in details, but I never check the content of
files that don't exist (aux, bib, bbl, log, etc).

Also, I haven't said that if an error is detected during the run, a
message box ask the user weither he wishes to continue the compilation
(ie to continue in the loop) or weither he'd rather stop it and see the
errors-window.

-- 
Luc Hermitte

[Vim-latex-devel] entering your own environments

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

Am I missing something?  I don't see how to enter a
user-defined environment.  For instance, users always have
commands like

\newtheorem{lemma}{Lemma}

so there should be a way of entering a generic or
user-defined environment.  Here was how I did it, in
auctex.vim.

Best wishes,
Carl

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

" The next idea came from a contributed NEdit macro.
" typing the name of the environment followed by <F5> results in 
" \begin{environment} \end{environment}
" But, typing <F5> at the beginning of the line results in a prompt
" for the name of the environment.
inoremap <buffer> <F5> <Esc>:call <SID>DoEnvironment()<CR>

function! s:DoEnvironment()
    let l = getline(line("."))
    let env = strpart(l, 0, col("."))
    if env =~ '^\s*$'
	call <SID>PutEnvironment(l, input("Environment? "))
    else
	normal 0D
	call <SID>SetEnvironment(env)
    endif
    startinsert
endfunction

function! s:PutEnvironment(indent, env)
  put! =a:indent . '\begin{' . a:env . '}'
  +put =a:indent . '\end{' . a:env . '}'
  normal k$
  if a:env=="array"
    call <SID>ArgumentsForArray(input("{rlc}? "))
  elseif a:env =~# '^\(theorem\|lemma\|equation\|eqnarray\|align\|multline\)$'
    exe "normal O\\label\<C-V>{" . input("Label? ") . "}\<Esc>j"
  endif
endfunction

Re: [Vim-latex-devel] running latex

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

Hello,

Luc and Benji discussed this just a while ago:

Luc suggested quite a comprehensive algorithm for rerunning latex. If we
want to go along the route, I think the following is best (Luc's idea).

> 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.

I did take a look at tex-tools.vim and it already seems to be
implemented :) So it shouldn't be too big of a deal to get it into
latex-suite. Also, ref the steps above, what happens if there is no .aux
file in step 2 above like carl says will happen the first time round...

I'll put this on my TODO list.

> I would also suggest that folding of math expressions be an
> option, not the default behavior.  When writing latex, you
> always want to see the math expressions.

Okay. To be frank, I haven't had a chance to actually do latex in quite
some time...

Thanks,
Srinath

-- 
Srinath Avadhanula
Nov 12 6:27am
Look out!  Behind you!

[Vim-latex-devel] running latex

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

I propose that "\ll" should run latex twice.  On the first
run, you usually get all kinds of spurious error messages
such as "reference ... not defined".  This happens because 
on the first run, the .aux file does not yet exist.  It's 
distracting to get these messages, and then have to close 
down the error window and run latex again.  

I would also suggest that folding of math expressions be an
option, not the default behavior.  When writing latex, you
always want to see the math expressions.

Best wishes,
Carl Mueller

Re: [Vim-latex-devel] double xdvi opens and compiler error

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

Hello Fabio,

This is kinda strange... But we'll work it out soon. Just to eliminate
the obvious,

When you open up a tex file, what does
	:set makeprg?
display?
It should be:
 	latex \\nonstopmode \\input\{$*\}
Hopefully, the $* is not missing.

If you can tell us that, we'll proceed from there. Also, there was a
syntax error in the ViewLaTeX() command causing those errors and causing
2 xdvi's to shoot up.

Please download the latest from


Thanks,
Srinath


On 12 Nov 2002, Fabio Spelta wrote:

> Hi.
> I've just checkout CVS module vimfiles and installed it.
> Dunno why, but :make still does not works:
> :!latex  \\nonstopmode \\input\{\} 2>&1| tee /tmp/v105219/4
> This is TeX, Version 3.14159 (Web2C 7.3.1)
> LaTeX2e <2001/06/01>
> Babel <v3.7h> and hyphenation patterns for american, french, german,
> ngerman, b
> asque, italian, portuges, russian, spanish, swedish, nohyphenation,
> loaded.
>
>
> ! LaTeX Error: File `.tex' not found.
>
> Type X to quit or <RETURN> to proceed,
> or enter new name. (Default extension: tex)
>
> Enter file name:
> ! Emergency stop.
> <read *>
>
> <*> \nonstopmode \input{}
>                          ^^M
> No pages of output.
> Transcript written on texput.log.
> (1 of 2) error: File `.tex' not found.
>
> --
>
> Second thing; when I \lv it opens two xdvi windows and not only one.
>
> Please cc me in your reply; i'm not subscribed to the list.
>
> Thank you
> --
>   Fabio Spelta
>
>    email: fab...@ti...
>    jabber: fe...@ja...
>    ecdl project: http://ecdllibre.sf.net
>
>
> -------------------------------------------------------
> 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] inserting \label{}

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

I notice that with the "eqnarray" environment, "\label{}"
is automatically inserted, which is good.  This needs to
happen for "equation", too.  If someone didn't want a 
label, they would use "\[...\]".

Best wishes,
Carl Mueller

[Vim-latex-devel] matching brackets

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

One of my biggest problems used to be mismatched brackets.
Now I have macros which automatically type the matching
bracket.  For instance, "(" results in "()" with the cursor
in between.  Since I sometimes want only one bracket, I made
it so that "((" results in "(".  That is faster than typing
"(" and then deleting the extra bracket.

Not everyone may agree with this idea, so it could be an option.
However, it has saved me an enormous amount of time.  Also,
the emacs package "ultratex" has automatic matching $$ and {},
so there is some precedent.  

I'm listing the code below.  It applies to:

()
[]
{}
\{\}
||
\|\|
$$
&&   (when within eqnarray or eqnarray* environments)

Carl Mueller

=========================================================================

" Bracket Completion Macros 

" Key Bindings             

" Typing the symbol a second time (for example, $$) will result in one
" of the symbole (for instance, $).  With {, typing \{ will result in \{\}.
inoremap <buffer> ( <C-R>=<SID>Double("(",")")<CR>
"inoremap <buffer> [ <C-R>=<SID>Double("[","]")<CR>
inoremap <buffer> [ <C-R>=<SID>CompleteSlash("[","]")<CR>
inoremap <buffer> $ <C-R>=<SID>Double("$","$")<CR>
inoremap <buffer> & <C-R>=<SID>DoubleAmpersands()<CR>
inoremap <buffer> { <C-R>=<SID>CompleteSlash("{","}")<CR>
inoremap <buffer> \| <C-R>=<SID>CompleteSlash("\|","\|")<CR>

" If you would rather insert $$ individually, the following macro by 
" Charles Campbell will make the cursor blink on the previous dollar sign,
" if it is in the same line.
" inoremap $ $<C-O>F$<C-O>:redraw!<CR><C-O>:sleep 500m<CR><C-O>f$<Right>

" Functions 

" For () and $$
function! s:Double(left,right)
    if strpart(getline(line(".")),col(".")-2,2) == a:left . a:right
	return "\<Del>"
    else
	return a:left . a:right . "\<Left>"
    endif
endfunction

" Complete [, \[, {, \{, |, \|
function! s:CompleteSlash(left,right)
    let column = col(".")
    let first = getline(line("."))[column-2]
    let second = getline(line("."))[column-1]
    if first == "\\"
	if a:left == "["
	    return "\[\<CR>\<CR>\\]\<Up>"
	else
	    return a:left . "\\" . a:right . "\<Left>\<Left>"
	endif
    else
	if a:left =~ '\[\|{'
	\ && strpart(getline(line(".")),col(".")-2,2) == a:left . a:right
	    return "\<Del>"
        else
            return a:left . a:right . "\<Left>"
	endif
    endif
endfunction

" Double ampersands, if you are in an eqnarray or eqnarray* environment.
function! s:DoubleAmpersands()
    let stop = 0
    let currentline = line(".")
    while stop == 0
	let currentline = currentline - 1
	let thisline = getline(currentline)
	if thisline =~ '\\begin' || currentline == 0
	    let stop = 1
	endif
    endwhile
    if thisline =~ '\\begin{eqnarray\**}'
	return "&&\<Left>"
    elseif strpart(getline(line(".")),col(".")-2,2) == "&&"
	return "\<Del>"
    else
	return "&"
    endif
endfunction

[Vim-latex-devel] double xdvi opens and compiler error

[Fabio S. <fab...@ti...>]

Hi.
I've just checkout CVS module vimfiles and installed it.
Dunno why, but :make still does not works:
:!latex  \\nonstopmode \\input\{\} 2>&1| tee /tmp/v105219/4
This is TeX, Version 3.14159 (Web2C 7.3.1)
LaTeX2e <2001/06/01>
Babel <v3.7h> and hyphenation patterns for american, french, german,
ngerman, b
asque, italian, portuges, russian, spanish, swedish, nohyphenation,
loaded.


! LaTeX Error: File `.tex' not found.

Type X to quit or <RETURN> to proceed,
or enter new name. (Default extension: tex)

Enter file name:
! Emergency stop.
<read *>

<*> \nonstopmode \input{}
                         ^^M
No pages of output.
Transcript written on texput.log.
(1 of 2) error: File `.tex' not found.

-- 

Second thing; when I \lv it opens two xdvi windows and not only one.

Please cc me in your reply; i'm not subscribed to the list.

Thank you
-- 
  Fabio Spelta
  
   email: fab...@ti...
   jabber: fe...@ja...
   ecdl project: http://ecdllibre.sf.net

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

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

Mikolaj Machowski wrote:
> 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.

      In AMS-LaTeX,

$ 1 + \dots + 5 $	% like \cdots if followed by +

$ 1, \dots, 5 $		% like \dots if followed by ,

Personally, I have never trusted this, so I always use $\ldots$ or 
$\cdots$ as I see fit, but using $\dots$ is probably better (when using 
amsmath) than using either one of these automatically.

					--Benji

[Vim-latex-devel] (no subject)

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

Bcc: 
Subject: [Vim-latex-devel] Re: splitting lines
Reply-To: 
In-Reply-To: <Pin...@fl...>

Hello,

* On Sun, Nov 10, 2002 at 06:15:42PM -0800, Srinath Avadhanula <sr...@ee...> wrote:
> Please try it out and tell me what you think.

I have some general comments. Fortunately, 'ì' (\`i) and 'â' (\^a) are
not characters I need in French. But people using iso-8859-1 encoding
and these characters will trigger the <M-l> and <M-b> mappings on ì and
â.  
Mappings on meta characters must be handled with care, or we must let a
way to easily change the mappings without having to edit the
incriminated script files.

Otherwise, I'm thinking of a feature that could be very nice: on xxxx
[1], we insert \textbf{} or \mathbf{} according to the current mode.

Cheers.

[1] ']bf' beeing my favourite keybinding
-- 
Luc Hermitte

[Vim-latex-devel] [ vim-latex-Patches-636028 ] Allow arbitrary placement of menu tree

[<no...@so...>]

Patches item #636028, was opened at 2002-11-09 21:55
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=636028&group_id=52322

Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 5
Submitted By: Peter Wilson (pabw)
Assigned to: Nobody/Anonymous (nobody)
Summary: Allow arbitrary placement of menu tree

Initial Comment:
This package adds too many top-level menus for my tastes. This package adds the infrastructure necessary to move the menus around.

It adds another option named g:Tex_MainMenuPrefix and uses it to generate s:mainmenuname in texmenuconf.vim, fixes a bug in texmenuconf.vim where s:mainmenuname wasn't used when it should have been, and adds a bit of documentation to texrc suggesting how to move the menus by setting g:Tex_MainMenuPrefix and g:Tex_MenuPrefix.

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

>Comment By: Srinath Avadhanula (srinathava)
Date: 2002-11-11 08:58

Message:
Logged In: YES 
user_id=460214


Accepted the patch. Thanks!

Also, I dont see the use of having g:Tex_MainMenuPrefix and
g:Tex_MenuPrefix. I used only g:Tex_MenuPrefix. This way
if that variable ends with a '.', then latex-suite creates
just one
menu.

-- 
Srinath

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=636028&group_id=52322

Re: [Vim-latex-devel] splitting lines

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

Hello Carl,

I just had a quick stab at incorporating 2 of your files into
latex-suite. As of now, since I dont have any other bright ideas, I have
added them to the ftplugin/tex/ directory. Maybe this will change in the
future.

I have temporarily put up a zip file at:

	http://vim-latex.sf.net/auctex-latexSuite.zip

Installation should be similar to the standard package.  It should
contain 2 files in the ftplugin/tex directory. As of now, I have had
time to incorporate the function for formatting lines without breaking
$$s and the functions for inserting \left( \right) etc.

Please try it out and tell me what you think.

The other developers should note that this addition has been done to the
CVS repository but as previously mentioned to a new branch, called
"release-nov-10-02-auctex-brach"
(Note: its brach not branch :( )

Which means you will still be able to work on bug fixes etc on the main
trunk without my huge changes getting in your way.

Anyayz, give it a try and let me know what you think.

Srinath


On Sat, 9 Nov 2002, Carl Mueller wrote:

> Dear Srinath,
>
> Thanks for looking at my suggestions.  I'll work on the bug,
> and I'll join the list.

[Vim-latex-devel] Possible bug in ViewLaTeX

[Michael C. H. <ho...@cs...>]

I currently don't have a dvi viewer installed (Cygwin on NT).

When I invoke the non-existent DVI viewer from
vim (not gvim), the following error is reported

Error detected while processing function ViewLaTeX
line   42:
:endif without :if: ^Iend

This seems to be an error in interpreting the plugin
code.  It causes the Cygwin terminal to print all text 
with the error highlighting background colour.

The shell also tells me that xdvi is not found.  Twice.
That seems odd to me as well.  I have looked at the 
code for ViewLaTeX and it doesn't look obviously 
like there's an extra endif.  I suppose that the 
missing executible is causing the script interpreter
some trouble.  

I know my setup is incomplete (as far as not having
a dvi viewer is concerned).   I shall stop invoking
the viewer, of course.  I just wanted to know what
it might do.  Now I know.  :-)

Mike

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

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

* On Sun, Nov 10, 2002 at 04:05:04PM +0100, Peter Karp <pe...@ka...> wrote:
> > Not every body using VIM have these tools installed, nor VIM
> > compiled to accept such script.
> ??? You mean somebody will not be able to run a simple Vim script foo.vim?
> I doubt that. Or did you mean that not everybody has Perl or awk configured
> in some way to work with Vim? That's surely right.

I mean your second hypothesis: having vim installed does not mean one
has perl nor awk installed. Nor one has a vim version with support of
perl.

> > With XT, i didn't have to run any makefile to install it.
> ? What's XT? 

XT is a parser that render XML data into any format (html, php, TeX, ...
and even pure text file if we want to) according to a given XSLT file. 

> > > 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
> Thanks for the pointer. On a first look I didn't found how that would help
> me -- not with a too big effort.

I don't remember where exactly, but in the FAQ, there is a list of
products able to parse XSLT+XML documents to render the data in other
formats. XT is referenced, amongs several other free and not free
programs.

> My thought was that a Vim script might be the best solution, because every
> Vim user who would like to take the XML sources to add personal stuff will
> surely have Vim. 
> All other solutions seem not so easy to use for me. 

I understand what you mean.
But, converting an XML file thanks to a dedicated tool (ie an XML+XSLT
parser) will be easier than trying a parse a tagged file will tools like
awk. Awk is nice, but not the easiest tool for this task.

> Every other solution like Perl and even more XSLT would need more
> effort and is not likely to be installed "just" to translate the docs
> for themself. 
> O.K. one can argue that not many people would like to add personal
> stuff. That could be true. 

I think so: not every body will want to add stuff to the doc. And if
they want to do it, they will likely share with other people, and they
may be interrested in using appropriate tools.

> _I_ want to be able to add personal content :-)

You have awk installed. Not everybody has it -- unless having access to
a *NIX system.

Anyway. It is not very important as you can provide an awk script to
translate the docs into HTML/vim-help ; and other people can provide two
XSLT files aimed at producing the same thing.

Regards,

-- 
Luc Hermitte

Re: [Vim-latex-devel] packages.vim: bug?

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

On Sat, Nov 09, 2002 at 06:07:33PM -0800, Srinath Avadhanula wrote:
> Hello,
> I just noticed a small thing. updateAll doesn't seem to remove the
> package from the menu if we remove the \usepackage{package} line.
> Reproduce:
> 1. open up a new file. add in the amsmath package using the
>    menu.
> 2. Now remove the \usepackage{amsmath} line.
> 3. update all. for me, this doesn't remove the amsmath from
>    Tex-Packages menu.
> However, strangely enough, it does work some of the time.

And for me it never works. OK. I will fix it.

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: LaTeX help for Vim

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

Hermitte Luc schrieb am 09.11.2002:

> > 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.

Ah, o.k.

> Not every body using VIM have these tools installed, nor VIM compiled to
> accept such script.

??? You mean somebody will not be able to run a simple Vim script foo.vim?
I doubt that. Or did you mean that not everybody has Perl or awk configured
in some way to work with Vim? That's surely right.
 
> > , 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.

? What's XT? 

> > 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

Thanks for the pointer. On a first look I didn't found how that would help
me -- not with a too big effort.

> 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.

As I don't know what XT is I don't understand your e-mail in all details.

My thought was that a Vim script might be the best solution, because every
Vim user who would like to take the XML sources to add personal stuff will
surely have Vim. All other solutions seem not so easy to use for me. Only
awk, as it has a really tiny binary would be almost as good. Every other
solution like Perl and even more XSLT would need more effort and is not
likely to be installed "just" to translate the docs for themself. O.K. one
can argue that not many people would like to add personal stuff. That could
be true. I don't know. _I_ want to be able to add personal content :-)


Regards
Peter

[Vim-latex-devel] Re[2]: does VIM has bibtex support as Emacs?

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

Hey Alan,

I wonder why I missed telling you this (did I?), but when you announced
this function on the vim list a long time ago, I incorporated it into
LaTeX-suite ( http://vim-LaTeX.sf.net ) I changed a few things to
incorporate it into the general LaTeX-suite structure (although not
much). If you install LaTeX-suite, it will be in ftplugin/latex-suite/

Unfortunately, it remains a very well hidden feature of LaTeX-sute
because I never got around to doing any documentation for it. Are you
interested? It will be a shame if this nice function is not used just
because of lack of docs.

Thanks,
Srinath

PS: I have been doing lots of other things nowadays and therefore only
very rarely catch up with this list, so please excuse me if I haven't
responded to things which were obviously directed at me.

On Fri, 8 Nov 2002, Alan G Isaac wrote:

> > Liu Wen <ipt...@16...> wrote on 08/11/2002 (09:38) :
> >> I am looking for a bibtex management software under windows, for bibtex
> >> format is more schalable than Endnotes or Ref Manager. It seems vim does
> >> not support it yet.
>
> On Fri, 8 Nov 2002 10:32:12 +0100 Preben Randhol <ran...@pv...> wrote:
> > Check: http://www.math.rochester.edu:8080/u/cmlr/vim/syntax/
>

-- 
Srinath Avadhanula
Nov 10 3:53am
The end of the world will occur at 3:00 p.m., this Friday, with
symposium to follow.

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

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

Hey Peter!

The Tex-Refs (or is Tex-refs for friends :) project sounds very
fascinating. From what I understand, the most useful thing for you now
will be a vim macro which converts XML source to vim help...

As of now, I do not have any experience with XML or the like, but it
looks like a useful thing to learn... I was in fact thinking of
expanding the documentation section of LaTeX-suite and in that sense
your email did come in time.

A few doubts:

1. Although a vim help format file might be the most natural way of
   viewing LaTeX documentation for users, HTML in my opinion does not
   fall far behind. Firstly, absolutely everyone has some sort of HTML
   browser.  With HTML, we could do more formatting etc.
2. Also, at around the bottom of the first URL, you say that you might
   need some help converting the vim help file into html. Mikolaj has
   already done this for the LaTeX help file in LaTeX-suite.
   See it at:
    http://vim-latex.sourceforge.net/download/latexhelp.html
   It has html links and everything...
   I say this because www.karpfenteich.net says at the bottom:
>      (at the moment simple form without hyperlinks, read to the end to
>      see how you could help me there :-)

In any case, we can begin to collaborate even before a xml-vimhelp tool
is available. For one, I'll put a link to the tex-refs page from the
links page on LaTeX-suite.

At the present moment, I am looking at some vim scripting things with
LaTeX-suite. I will get back to you when I get that done.

Thanks,
Srinath

On Sat, 9 Nov 2002, Peter Karp wrote:

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

-- 
Srinath Avadhanula
Nov 10 1:58am
I am so optimistic about beef prices that I've just leased a pot roast
with an option to buy.

[Vim-latex-devel] Re: Incorporating new contributions into vim-latex

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

* On Sat, Nov 09, 2002 at 05:08:49PM -0800, Srinath Avadhanula <sr...@fa...> wrote:
> What about just adding them into the ftplugin/tex directory? 

If the script only concerns TeX, of course, this is a good way, may be
the better.  When it is broader than that, {rtp}/plugin or even
{rtp}/macros will be better.

Regarding dependencies aspects, if the script is not meant to be totally
independant, forcing dependencies to be respected is not a very big
issue -- as I guess it is not your main problem, I won't dwell any
longer on this subject now.

> This way vim will take care of sourcing them. This however means that
> these plugins will have to be completely independent of latex-suite. I
> still dont have a good way to get the commands into the menus? Also
> some documentation is required.

If on the long run everybody agrees to converge to one unique big and
wonderful suite (I think it will be the case & I hope it will eventually
happen), the issues will be:
- for the add-on scripts: how to fit in the suite without messing up
  things
- for the suite: how to export interface functions and commands (API) to
  the add-ons.

For instance, I will take an example from lh-tex & my other html stuff:
my suites are build around several commands: 
- MenuMake: that defines here a -nic-menu + 3 mappings for normal,
  insert and command mode to produce DVI documents
    :MenuMake nic 50.305 &LaTeX.Run\ LaTeX\ &once	<C-L><C-O>
      \ <buffer> :wa<CR>:TeXMakeDVI 1<CR>
- MapMenu: that defines a -inv-menu + 3 mappings for insert, normal and
  visual modes to insert TeX commands, here "\emph{}«»" [1](/ "emph{}"
  around current word/selection)
    :MapMenu 50.370.100.400 &LaTeX.&Fonts.S&hort\ Scope.&Emphasize	
      \ ]em	emph

I haven't totaly checked the LaTeX suite, but with similar tools, the
add-ons can easily fit in the suite. All the suite developers have to do
is: propose the commands and suggest places (in menus) to add other
stuff.

A even more advanced (read "smart") mecanism could take care of the
assignment of numbers in the menu -- could be tough to do, but
interresting.

Note BTW: this approach (MapMenu&MenuMake&...) ensures the mappings and
menus are coherent. On this point it seems that mathmacros.vim and
main.vim are not synchronized ; check the greek letters.

Back to the point of beeing independant of the latex-suite. 
Today the agenda seems to be to bring together totally different
features that can be defined in many different ways. The menu problem
may arise. 
Eventually, the latex-suite will a be standard [2]. In other words, the
latex-suite will be the big open IDE. Its role won't be to define menus
for script to-be-written, but to propose API functions/commands that
will be used by the script to-be-written in order to be part of the
suite.

Don't make an independant menus-for-(la)tex module. Instead, propose a
way to define mappings *and* menu in one action, and split the different
stuff according thematics: compilation/viewing, environments, maths,
fonts (if not part of environments), smart chars, ... IMO, it will be
easier to maintain and help on the scalability issue.


Last point, try to not be redundant with other existing plugins. For
instance you use a specialised version of mu-templates for LaTeX as an
ftplugin. Why not using mu-template as a global plugin ? Copying it adds
more work on your shoulders. And I don't see the point of having
mu-templates for LaTeX, mu-templates for xslt, mu-templates for C++,
etc. Don't make it a ftplugin. It is generic, like brackets and markers.

Something like: 
    function s:AddToMyMenu(template_file)
      let short=matchstr(a:template_file, 
	\ 'template[/\\]tex[/\\]template\.\zs.*')
      exe "amenu ".g:Tex_TemplatesMenuLocation.".&".short." "
	\ ':MuTemplate tex/'.short."\<cr>"
    endfunction
    :command -nargs=1 AddToMyMenu :call s:AddToMyMenu("<arg>")
    :SearchInRuntime! AddToMyMenu template/tex/template.*
    " or, with your configuration and more complex regexs:
    :SearchInRuntime! 
	\ AddToMyMenu template/template.tex-*
	\ AddToMyMenu template/tex/template.*
	\ AddToMyMenu ftplugin/latex-suite/templates/template.*
    :delcommand AddToMyMenu
... should do the trick [3] 


Hope this will be of any help.

[1] "\emph{}" only if b:usemarks is set to 0
[2] Which make me think about auctex whose problem is "one monolotical
file". It proposes many very good things, but it is (was?) not really
scalable (neither European/French friendly): changing one little part to
suit our preferences will be eventually problematic for the day a new
version is available.
[3] but: - with a customized version of mu-template that is not aware of
latex, vim, C++, xslt, etc, - and another plugin (searchInRuntime).
-- 
Luc Hermitte

[Vim-latex-devel] packages.vim: bug?

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

Hello,

I just noticed a small thing. updateAll doesn't seem to remove the
package from the menu if we remove the \usepackage{package} line.

Reproduce:

1. open up a new file. add in the amsmath package using the
   menu.
2. Now remove the \usepackage{amsmath} line.
3. update all. for me, this doesn't remove the amsmath from
   Tex-Packages menu.

However, strangely enough, it does work some of the time.

-- 
Srinath

[Vim-latex-devel] CVS branching

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

I anticipate a fairly turbulent developement cycle over the next few
days/weeks. This will become more of an effect when we get more people
into the developement circle. Which means that things might get into
a broken state if we are not careful.

So here's what I propose:

Lets keep the main trunk of the CVS tree as a 'stable' candidate at all
times.  Whenever we want to make some major changes, split off a branch
and do developement on that branch. When that branch gets into a stable
state, merge it into the main trunk. I heard somewhere this kind of
thing being described as the "branch early" way of working. We still
ofcourse make small changes we are reasonably confident of working
straight away in the main branch.

How to do this is described extensively in the CVS manual and book:

<a href="http://www.cvshome.org/docs/manual/cvs.html">CVS manual</a>
<a href="http://cvsbook.red-bean.com/cvsbook.html">CVS book</a>

Have a look. Its also a very cool new thing to learn if you haven't
tried it before (I havent tried it before).

Benji, you might want to try this the next time you do some of those
radical changes you talked about :) I am going to do it now when I add
in Carl's changes.

Thanks,
Srinath

[Vim-latex-devel] Incorporating new contributions into vim-latex

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

Hello!

We need to figure out a good way to introduce new files into the project. I
am working on  incoporating Carl's contributions into latex-suite. As of
now, I cannot think of some way which should be the "correct" way.. Please
think about this in your spare time and let me know if you get some good
ideas.

What about just adding them into the ftplugin/tex directory? This way vim
will take care of sourcing them. This however means that these plugins will
have to be completely independent of latex-suite. I still dont have a good
way to get the commands into the menus? Also some documentation is
required.

Thanks!

Srinath