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

Re: [Vim-latex-devel] running latex

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

Carl Mueller wrote:
> 
> I have some suggestions about running latex and viewing the errors.
> 
> Once again, emacs did it right, in my opinion (in the auctex package).
> After running latex, the .log file appears in its own window.
> Typing C-c` will take you to the next tex error.  The cursor is
> placed on the exact position of the error.  This is indicated in
> the .log file by a split line, with the split at the postion of the
> error.  Also, the .log file has hints about correcting the error.

     If we want to load the .log file instead of the quickfix window, we
could define a custom file type.  We would explicitly

:set ft=texlog

instead of trying to have the filetype detected automatically.  Then we
could define custom syntax and key mappings to get the desired
behavior.  A lot of work, but possible.  It might be possible (or
easier) to get the same effect by fiddling with the quickfix window.

> Less of that happens in quickfix mode.  The cursor is not positioned
> at the point of the error.  (Of course, with :cn one can go to the line
> of the error, but not the position within the line).  Only a one-line
> description of the error is given, while the .log file has lots of
> information.

     I agree:  I often miss the extra information in the .log file. 
Some time, I want to discuss the defaults:  I think the warning level
affects this.

> Another issue is with xdvi.  I don't know the situation with windows.
[snip]
> 
> I prefer automatic updating of xdvi.

     MikTeX (on windows) automatically updates the viewer when it gains
focus.  This is A Good Thing.  That reminds me:  is there any reason not
to have RunLaTeX() start with :update ?

> For this reason, I have 2 sets of macros.  One of them has xdvi
> automatically updating, but the errors do not automatically show up.
> In the second, you have to click in xdvi to update, but the errors
> automatically show up.
[snip]

     I am sorry, I do not have time to look at these now.  (Maybe not
for a while ...)  Are your two scripts exclusive?  That is, can you not
get both improvements at the same time?

					--Benji

Re: [Vim-latex-devel] running latex

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

On Tue, Nov 19, 2002 at 02:31:32PM -0500, Carl Mueller wrote:
> You might also want to consider a macro a got from Charles Campbell (and
> modified), which allows you to run latex on a file or a highlighted region.

Sorry, I meant running ispell, not latex.

Best wishes,
Carl 

[Vim-latex-devel] running latex

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

I have some suggestions about running latex and viewing the errors.

Once again, emacs did it right, in my opinion (in the auctex package).
After running latex, the .log file appears in its own window.
Typing C-c` will take you to the next tex error.  The cursor is 
placed on the exact position of the error.  This is indicated in 
the .log file by a split line, with the split at the postion of the 
error.  Also, the .log file has hints about correcting the error.

Less of that happens in quickfix mode.  The cursor is not positioned 
at the point of the error.  (Of course, with :cn one can go to the line
of the error, but not the position within the line).  Only a one-line
description of the error is given, while the .log file has lots of 
information.

Another issue is with xdvi.  I don't know the situation with windows.
On Unix, if you run latex within vim, the xdvi viewer does not 
automatically update, and you have to click in it.  But if you run 
latex within an x-terminal, xdvi does automatically update the view.  
Also, if you give vim the command to launch an x-term, and then tell vim 
to start looking at the .log file, it will look at the .log file before 
latex has finished running.  With Vim-LaTex, you get to view the errors
right away, but xdvi doesn't automatically update.  

I prefer automatic updating of xdvi.

For this reason, I have 2 sets of macros.  One of them has xdvi
automatically updating, but the errors do not automatically show up.
In the second, you have to click in xdvi to update, but the errors
automatically show up.

I know people have put in a lot of work on the quickfix way of 
displaying tex errors.  Could my suggestions be considered as 
an option?

Carl Mueller

I'm listing 2 sets of functions.  Both allow you to run latex, view the
.log file with syntax highlighting, and automatically go to the position 
of the error.  There are also functions to view \ref{} and \cite{}
errors, or look at the log file, and go to the line mentioned in the file.
You might also want to consider a macro a got from Charles Campbell (and
modified), which allows you to run latex on a file or a highlighted region.
The key bindings in these files are bad;  they're not the important part.

"""""""""""""""""""""""""""""""""""""""""""
" Macros with automatic updating of xdvi

" Latex command.

let b:latex_command = "! xterm -bg ivory -fn 7x14 -e latex % &"
"let b:latex_command = "! latex \\\\nonstopmode \\\\input\\{%\\}"

" Key Bindings  {{{

" Run Latex;  change these bindings if you like.
noremap <buffer> \ml :call <SID>RunLatex()<CR><Esc>
noremap <buffer> \mr :call <SID>CheckReferences("Reference", "ref")<CR><Space>
noremap <buffer> \mc :call <SID>CheckReferences("Citation", "cite")<CR><Space>
noremap <buffer> \mg :call <SID>LookAtLogFile()<CR>gg/LaTeX Warning\\|^!<CR>
noremap <buffer> \mn :call <SID>NextTexError()<CR><Space>
noremap <buffer> \mv :call <SID>Xdvi()<CR><Space>
noremap <buffer> \mi :w<CR>:silent ! xterm -bg ivory -fn 10x20 -e ispell %<CR>:e %<CR><Space>

noremap <buffer> K :call <SID>RunLatex()<CR><Esc>
noremap <buffer> <C-K> :call <SID>NextTexError()<CR><Space>

" Run Ispell on either the buffer, or the visually selected word.
noremap <buffer> <S-Insert> :w<CR>:silent ! xterm -bg ivory -fn 10x20 -e ispell %<CR>:e %<CR><Space>
inoremap <buffer> <S-Insert> <Esc>:w<CR>:silent ! xterm -bg ivory -fn 10x20 -e ispell %<CR>:e %<CR><Space>
vnoremap <buffer> <S-Insert> <C-C>`<v`>s<Space><Esc>mq:e ispell.tmp<CR>i<C-R>"<Esc>:w<CR>:silent ! xterm -bg ivory -fn 10x20 -e ispell %<CR>:e %<CR><CR>ggVG<Esc>`<v`>s<Esc>:bwipeout!<CR>:!rm ispell.tmp*<CR>`q"_s<C-R>"<Esc>

" }}}

" Functions  {{{

function! s:RunLatex()
    update
    exe "silent " . b:latex_command
endfunction

" Stop warnings, since the log file is modified externally and then 
" read again.
au BufRead *.log    set bufhidden=unload

function! s:NextTexError()
    silent only
    edit +1 %<.log
    syntax clear
    syntax match err /! .*/
    syn match err /^ l\.\d.*\n.*$/
    highlight link err ToDo
    if search('^l\.\d') == 0
	edit #
	redraw
	call input("\nNo (More) Errors Found\n\nPress 'enter' to go on.")
    else
	let linenumber = matchstr(getline('.'), '\d\+')
	let errorposition = col("$") - strlen(linenumber) - 4
	    "Put a space in the .log file so that you can see where you were,
	    "and move on to the next latex error.
	s/^/ /
	write
	split #
	exe "normal " . linenumber . "G" . errorposition . "lzz\<C-W>wzz\<C-W>w"
    endif
endfunction

function! s:CheckReferences(name, ref)
    "exe "noremap \<buffer> \<C-L> :call \<SID>CheckReferences(\"" . a:name . "\",\"" . a:ref . "\")\<CR>\<Space>"
    only
    edit +1 %<.log
    syntax clear
    syntax match err /LaTeX Warning/
    highlight link err ToDo
    if search('^LaTeX Warning: ' . a:name) == 0
	edit #
	redraw
	call input("\nNo (More) " . a:name . " Errors Found\n\nPress 'enter' to go on.")
    else
	let linenumber = matchstr(getline('.'), '\d\+\.$')
	let linenumber = strpart(linenumber, 0, strlen(linenumber)-1)
	let reference = matchstr(getline('.'), "`.*\'")
	let reference = strpart(reference, 1, strlen(reference)-2)
	    "Put a space in the .log file so that you can see where you were,
	    "and move on to the next latex error.
	s/^/ /
	write
	split #
	exe "normal " . linenumber . "Gzz\<C-W>wzz\<C-W>w"
	exe "normal /\\\\" . a:ref . "{" . reference . "}\<CR>"
	exe "normal /" . reference . "\<CR>"
    endif
endfunction

function! s:LookAtLogFile()
    only
    edit +1 %<.log
    syntax clear
    syntax match err /LaTeX Warning/
    syntax match err /! .*/
    syntax match err /^Overfull/
    syntax match err /^Underfull/
    highlight link err ToDo
    noremap <buffer> K :call <SID>GetLineFromLogFile()<CR>
    split #
    wincmd b
    /LaTeX Warning\|^\s*!\|^Overfull\|^Underfull
    let @/='LaTeX Warning\|^\s*!\|^Overfull\|^Underfull'
    echo "\nGo to the line in the log file which mentions the error\nthen type K to go to the line\nn to go to the next warning\n"
endfunction

function! s:GetLineFromLogFile()
    let line = matchstr(getline("."), 'line \d\+')
    wincmd t
    exe strpart(line, 5, strlen(line)-5)
endfunction

" }}}

" vim:fdm=marker



"""""""""""""""""""""""""""""""""""""""""""
" Macros which automatically show the errors.

" Latex command.

let b:latex_command = "! xterm -bg ivory -fn 7x14 -e latex % &"
"let b:latex_command = "! latex \\\\nonstopmode \\\\input\\{%\\}"

" Key Bindings  {{{

" Run Latex;  change these bindings if you like.
noremap <buffer> \ml :call <SID>RunLatex()<CR><Esc>
noremap <buffer> \mr :call <SID>CheckReferences("Reference", "ref")<CR><Space>
noremap <buffer> \mc :call <SID>CheckReferences("Citation", "cite")<CR><Space>
noremap <buffer> \mg :call <SID>LookAtLogFile()<CR>gg/LaTeX Warning\\|^!<CR>
noremap <buffer> \mn :call <SID>NextTexError()<CR><Space>
noremap <buffer> \mv :call <SID>Xdvi()<CR><Space>
noremap <buffer> \mi :w<CR>:silent ! xterm -bg ivory -fn 10x20 -e ispell %<CR>:e %<CR><Space>

noremap <buffer> K :call <SID>RunLatex()<CR><Esc>
noremap <buffer> <C-K> :call <SID>NextTexError()<CR><Space>

" Run Ispell on either the buffer, or the visually selected word.
noremap <buffer> <S-Insert> :w<CR>:silent ! xterm -bg ivory -fn 10x20 -e ispell %<CR>:e %<CR><Space>
inoremap <buffer> <S-Insert> <Esc>:w<CR>:silent ! xterm -bg ivory -fn 10x20 -e ispell %<CR>:e %<CR><Space>
vnoremap <buffer> <S-Insert> <C-C>`<v`>s<Space><Esc>mq:e ispell.tmp<CR>i<C-R>"<Esc>:w<CR>:silent ! xterm -bg ivory -fn 10x20 -e ispell %<CR>:e %<CR><CR>ggVG<Esc>`<v`>s<Esc>:bwipeout!<CR>:!rm ispell.tmp*<CR>`q"_s<C-R>"<Esc>

" }}}

" Functions  {{{

function! s:RunLatex()
    update
    exe "silent " . b:latex_command
    call <SID>NextTexError()
endfunction

" Stop warnings, since the log file is modified externally and then 
" read again.
au BufRead *.log    set bufhidden=unload

function! s:NextTexError()
    silent only
    split
    wincmd j
    edit +1 %<.log
    if search('^l\.\d') == 0
	bwipeout
	redraw
	call input("\nNo (More) Errors Found\n\nPress 'enter' to go on.")
    else
	syntax clear
	syntax match err /! .*/
	syn match err /^ l\.\d.*\n.*$/
	highlight link err ToDo
	let linenumber = matchstr(getline('.'), '\d\+')
	let errorposition = col("$") - strlen(linenumber) - 4
	    "Put a space in the .log file so that you can see where you were,
	    "and move on to the next latex error.
	s/^/ /
	write
	wincmd k
	exe "normal " . linenumber . "G" . errorposition . "lzz\<C-W>wzz\<C-W>w"
    endif
endfunction

function! s:CheckReferences(name, ref)
    "exe "noremap \<buffer> \<C-L> :call \<SID>CheckReferences(\"" . a:name . "\",\"" . a:ref . "\")\<CR>\<Space>"
    only
    edit +1 %<.log
    syntax clear
    syntax match err /LaTeX Warning/
    highlight link err ToDo
    if search('^LaTeX Warning: ' . a:name) == 0
	edit #
	redraw
	call input("\nNo (More) " . a:name . " Errors Found\n\nPress 'enter' to go on.")
    else
	let linenumber = matchstr(getline('.'), '\d\+\.$')
	let linenumber = strpart(linenumber, 0, strlen(linenumber)-1)
	let reference = matchstr(getline('.'), "`.*\'")
	let reference = strpart(reference, 1, strlen(reference)-2)
	    "Put a space in the .log file so that you can see where you were,
	    "and move on to the next latex error.
	s/^/ /
	write
	split #
	exe "normal " . linenumber . "Gzz\<C-W>wzz\<C-W>w"
	exe "normal /\\\\" . a:ref . "{" . reference . "}\<CR>"
	exe "normal /" . reference . "\<CR>"
    endif
endfunction

function! s:LookAtLogFile()
    only
    edit +1 %<.log
    syntax clear
    syntax match err /LaTeX Warning/
    syntax match err /! .*/
    syntax match err /^Overfull/
    syntax match err /^Underfull/
    highlight link err ToDo
    noremap <buffer> K :call <SID>GetLineFromLogFile()<CR>
    split #
    wincmd b
    /LaTeX Warning\|^\s*!\|^Overfull\|^Underfull
    let @/='LaTeX Warning\|^\s*!\|^Overfull\|^Underfull'
    echo "\nGo to the line in the log file which mentions the error\nthen type K to go to the line\nn to go to the next warning\n"
endfunction

function! s:GetLineFromLogFile()
    let line = matchstr(getline("."), 'line \d\+')
    wincmd t
    exe strpart(line, 5, strlen(line)-5)
endfunction

" }}}

" vim:fdm=marker

[Vim-latex-devel] minor bug

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

Hi.
Latex-suite changes the color into brackets in a different way between
\ref and \pageref. Is that right?

Also, [OT], does anybody knows about package "nameref" ? It bring some
trouble to me.

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

Re: [Vim-latex-devel] envmacros.vim

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

On Sun, Nov 17, 2002 at 10:23:32AM -0800, Srinath Avadhanula wrote:
> However, if we do begin caring about file content, we should look out
> for whether this is the main file or not. For example, if there is a
> main.tex.latexmain in the current directory and we are not editing
> main.tex, then only use behavior I, irrespective of file content.

Simpler is just checking if in current file is \documentclass
declaration.

> > 3. More than one word in line
> > ----------
> >
> > asdf asdfx
> >
> > ---------
> > Looks for environment and try to change it.
> I dont understand this... What would be an example?
a.
 ----------
\begin{quote}
 asdf asdfx
\end{quote}

 ---------
After <F5> you will get:
You are inside quote environment.
Do you want to change it to:

b.
 ----------
\begin{quote}
 asdfx
\end{quote}

 ---------
After <F5>
 ----------
\begin{quote}
 \begin{asdf}
    x
 \end{asdf}
\end{quote}

 ---------



> > II. Non empty file (only \documentclass declaration)
> Shouldn't this be: If in the preamble of the main file? We could check
> for being in the preamble by whether we are after \documentclass but
> before \begin{document}

Yes. But what if there is no \begin{document} line?

> > 1. Empty line
> > ----------
> > \documentclass{article}
> > x
> >
> > ---------
> > Asks for package
> > 2. One word in line
> > ----------
> > \documentclass{article}
> > asdfx
> >
> > ---------
> > Treats "asdf" as name of the package (and checks if supported)
> > 2. If line contains \usepackage
> > ----------
> > \documentclass{article}
> > \usepackage{asdf}x
> >
> > ---------
> > Change package. Useful when changing supported packages.
> Okay. This does sound useful, but use the Tex_GetMainFileName() if you
> implement something like this.

OK.
> > III. Template
> > ----------
> > \documentclass{article}
> >
> > \begin{document}
> >
> > \end{document}
> > ---------
> > If cursor is above \begin{document} behaviour as in II, if below as in
> > I.
> Hmmm... The template is created only once during the entire editing
> cycle. I dont think we need to have shortcuts for it since its highly
> improbable that a user will keep changing templates!

But sometimes you want to change package, add one.

m.

[Vim-latex-devel] About folding, again

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

Well, the trouble is similar to the previous one.
This time, after the last 

\section{title}
blah
blah
blah

...I start Appendixes this way:

\appendix
\input{a1}
\input{a2}

... and so on.

Well, once again, all the text starting from \appendix 'till the end is folded with
the last section!

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

[Vim-latex-devel] About folding, again

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

Well, the trouble is similar to the previous one.
This time, after the last 

\section{title}
blah
blah
blah

...I start Appendixes this way:

\appendix
\input{a1}
\input{a2}

... and so on.

Well, once again, all the text starting from \appendix 'till the end is folded with
the last section!

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

[Vim-latex-devel] Re: envmacros.vim

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

* On Sun, Nov 17, 2002 at 07:36:27PM -0800, Srinath Avadhanula <sr...@ee...> wrote:
> > Otherwise, I should be able to provide you a more advanced templates
> > mecanism completly independant of any LaTeX considerations.
> 
> What new functionality will these provide?

As I said, it will be independant of the type of the buffers manipulated
; ie one plugin (made of 3-4 files) for latex, vimL, C++, xslt, ...
It is based on mu-template [BTW, I have some features in mind that I
want to provide and then I will contact Gergely Kontra in case he is
still maintening (t)his plugin].

Otherwise, the other features are:
- Empty lines coming from '¡...¡' or '¿...¿' are purged
- A template skeleton can be reindented after it has been loaded
- The templates can be placed in any directory from
  {runtimepath}/template or $VIMTEMPLATE (list of directories)
  Useful for shared projects or installations
- Several options permit to deactivate some automatic and undesirable
  behaviours when needed
- I've defined a mapping (i_CTRL-R_TAB) that will search for template
  files matching: "template.{&ft}-{<cWORD>}" or "{&ft}/template.{cWORD}"
  ; in case there are several choices, a dialog will ask the user which
  template to insert ; cf xslt/ and tex/ templates in mu-template.tar.gz
  in my http://hermitte.free.fr/vim/ressources/ directory.
  i_CTRL-R_SPACE will work instead with the keyword preceding the
  position of the cursor.
  i_CTRL-R_xxx mappings can be changed to anything we want from outside
  the plugin thanks to the <Plug> mecanism.
- It supports markers from my version of bracketing.base.vim, Robert
  Kelly IV's markjump or your placeholders from imaps.vim

The current 0.26 version is functional and so far I have only one "bug"
left (my vim windows blinks one time ; ie I got one flash in insert
mode -- not critical, but undesired).

I haven't written the documentation yet. But as you will notice, it is
not complicated to use. Check the templates skeletons I propose for
examples.


-- 
Luc Hermitte

Re: [Vim-latex-devel] Re: envmacros.vim

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

> > to the environments in those. This way, we will have customization and
> > if someone decides that he doesn't want these shortcuts, he can leave
> > g:Tex_CommonEnvironments = ''
>
> I don't like the idea of having <xx-Fd> keys messed up with anything. So
> leaving an option to disable this feature is a good idea.
>
Yes... disabling this feature will simply mean leaving
g:Tex_CommonEnvironments = ''

> Otherwise, I should be able to provide you a more advanced templates
> mecanism completly independant of any LaTeX considerations.

What new functionality will these provide?

Srinath


-- 
Srinath Avadhanula
Nov 17 7:34pm
New crypt.  See /usr/news/crypt.

[Vim-latex-devel] Re: envmacros.vim

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

Hello,

* On Sun, Nov 17, 2002 at 10:23:32AM -0800, Srinath Avadhanula <sr...@ee...> wrote:
> > III. Template
> > ----------

> Hmmm... The template is created only once during the entire editing
> cycle. I dont think we need to have shortcuts for it since its highly
> improbable that a user will keep changing templates!

I Agree!

> Also, another idea. As of now, Carl's suggestion of having <S-F1>
> through <S-F4> map to commonly used environments is not implemented. A
> good way to do this will be to have a setting:
> g:Tex_CommonEnvironments
> 
> in texrc and map <S-F1> through <S-F4> (note that its <S-F1>, not <F1>),
> to the environments in those. This way, we will have customization and
> if someone decides that he doesn't want these shortcuts, he can leave
> g:Tex_CommonEnvironments = ''

I don't like the idea of having <xx-Fd> keys messed up with anything. So
leaving an option to disable this feature is a good idea.

Otherwise, I should be able to provide you a more advanced templates
mecanism completly independant of any LaTeX considerations.

-- 
Luc Hermitte

Re: [Vim-latex-devel] envmacros.vim

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

Hey Mikolaj!


On Sun, 17 Nov 2002, Mikolaj Machowski wrote:

>
> I am redirecting to devel list.
>
> On Sat, Nov 16, 2002 at 04:54:27PM -0800, Srinath Avadhanula wrote:
> > Hello!
> > I did most of this myself because I couldn't resist ;)
> > So the TODO which remains for envmacros.vim:
> > 1. EFI in menu and EFI in maps insert different things.
> > 2. Introduce a new setting g:Tex_UseMenuWizard in texrc to see if user
> >    wants wizard behavior or not.
> > 3. Change s:Tex_change_environments to also use the
> >    s:PromptForEnvironment function.
> > 4. Put a "Choose Environment" in the environments main menu (which
> >    should shortcut to Tex_FastEnvironmentInsert()).
> > 5. Documentation!!! All these features are presently hidden from user.
>
> Eeee, what exactly is left to do?

:) Plenty. See the TODO list above. none of these are implemented yet.
The _most important_ thing still unimplemented imo is number 2 above.
This according to me is really really important. This setting will have
to be used by each of the Tex_itemize() and such functions. For example,
pressing <F5> now and choosing 'figure' asks many many questions. I
would prefer just inserting a template with placeholders.

> I'd like to introduce one more feature: more intelligent F5 key. It will
> act:
> x - cursor
> I. Empty file
> 1. Empty line
> ----------
>
> x
>
> ---------
> Asks for environment.
> 2. One word in line
> ----------
>
> asdfx
>
> ---------
> Treats "asdf" as name of the environment
>
This is already the behavior. When there is a word, it constructs an
environment from that, otherwise it prompts. Try it out... As of now, it
doesn't care about whether there is stuff in the file or not.

However, if we do begin caring about file content, we should look out
for whether this is the main file or not. For example, if there is a
main.tex.latexmain in the current directory and we are not editing
main.tex, then only use behavior I, irrespective of file content.

> 3. More than one word in line
> ----------
>
> asdf asdfx
>
> ---------
> Looks for environment and try to change it.

I dont understand this... What would be an example?

> II. Non empty file (only \documentclass declaration)

Shouldn't this be: If in the preamble of the main file? We could check
for being in the preamble by whether we are after \documentclass but
before \begin{document}

> 1. Empty line
> ----------
> \documentclass{article}
> x
>
> ---------
> Asks for package
> 2. One word in line
> ----------
> \documentclass{article}
> asdfx
>
> ---------
> Treats "asdf" as name of the package (and checks if supported)
> 2. If line contains \usepackage
> ----------
> \documentclass{article}
> \usepackage{asdf}x
>
> ---------
> Change package. Useful when changing supported packages.

Okay. This does sound useful, but use the Tex_GetMainFileName() if you
implement something like this.

> III. Template
> ----------
> \documentclass{article}
>
> \begin{document}
>
> \end{document}
> ---------
> If cursor is above \begin{document} behaviour as in II, if below as in
> I.

Hmmm... The template is created only once during the entire editing
cycle. I dont think we need to have shortcuts for it since its highly
improbable that a user will keep changing templates!

Also, another idea. As of now, Carl's suggestion of having <S-F1>
through <S-F4> map to commonly used environments is not implemented. A
good way to do this will be to have a setting:

g:Tex_CommonEnvironments

in texrc and map <S-F1> through <S-F4> (note that its <S-F1>, not <F1>),
to the environments in those. This way, we will have customization and
if someone decides that he doesn't want these shortcuts, he can leave

g:Tex_CommonEnvironments = ''

So thats another TODO item... Plenty of things to choose from :)

Srinath


-- 
Srinath Avadhanula
Nov 17 10:02am
"I used to think that the brain was the most wonderful organ in my
body.  Then I realized who was telling me this."
		-- Emo Phillips

Re: [Vim-latex-devel] Off-Topic: Mikolaj's address working okay?

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

On Sat, Nov 16, 2002 at 04:58:08PM -0800, Srinath Avadhanula wrote:
> Hello,
> Whenever, I send email to mikolaj, I get warnings that the email
> couldn't be delivered for so many hours. So I am wondering if he is
> getting my email (or anyone elses).
> Mikolaj: If you receive this, please reply.

My mail service (wp.pl) was down for several hours.

m.

[Vim-latex-devel] envmacros.vim

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

I am redirecting to devel list.

On Sat, Nov 16, 2002 at 04:54:27PM -0800, Srinath Avadhanula wrote:
> Hello!
> I did most of this myself because I couldn't resist ;)
> So the TODO which remains for envmacros.vim:
> 1. EFI in menu and EFI in maps insert different things.
> 2. Introduce a new setting g:Tex_UseMenuWizard in texrc to see if user
>    wants wizard behavior or not.
> 3. Change s:Tex_change_environments to also use the
>    s:PromptForEnvironment function.
> 4. Put a "Choose Environment" in the environments main menu (which
>    should shortcut to Tex_FastEnvironmentInsert()).
> 5. Documentation!!! All these features are presently hidden from user.
> The reason for making a seperate function is that in the future, we might
> let the user choose which are the environments he most commonly uses
> instead of hardcoding them into s:common_environments.

Eeee, what exactly is left to do?
I'd like to introduce one more feature: more intelligent F5 key. It will
act:
x - cursor
I. Empty file
1. Empty line
----------

x

---------
Asks for environment.
2. One word in line
----------

asdfx

---------
Treats "asdf" as name of the environment
3. More than one word in line
----------

asdf asdfx

---------
Looks for environment and try to change it.
II. Non empty file (only \documentclass declaration)
1. Empty line
----------
\documentclass{article}
x

---------
Asks for package
2. One word in line
----------
\documentclass{article}
asdfx

---------
Treats "asdf" as name of the package (and checks if supported)
2. If line contains \usepackage
----------
\documentclass{article}
\usepackage{asdf}x

---------
Change package. Useful when changing supported packages.
III. Template
----------
\documentclass{article}

\begin{document}

\end{document}
---------
If cursor is above \begin{document} behaviour as in II, if below as in
I.

What do you think about it?

Mikolaj

[Vim-latex-devel] Off-Topic: Mikolaj's address working okay?

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

Hello,

Whenever, I send email to mikolaj, I get warnings that the email
couldn't be delivered for so many hours. So I am wondering if he is
getting my email (or anyone elses).

Mikolaj: If you receive this, please reply.

Thanks,
Srinath

-- 
Srinath Avadhanula
Nov 16 4:56pm
An artist should be fit for the best society and keep out of it.

[Vim-latex-devel] I am deeply impressed

[Carsten N. <cni...@gm...>]

Hello

I just wanted to thank you for your work. I am using vim and latex for ages 
and never found a really good way to do my work. Your scripts are _great_, 
esp. in combination with kvim.

So again: Thanks!

Carsten

Re: [Vim-latex-devel] Accents

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

On Fri, Nov 15, 2002 at 02:26:27PM +0000, Fabio Spelta wrote:
> I'd like to have the suite converting ? ? ? ... and so on into
> \`e, \`a ... , not into \\varepsilon...
> How can I do? (where I have to change some setting?)

Try to change value of g:Tex_Leader in texrc.
And shortcuts for diacritics described in this file by g:Tex_Diacritics.

Mikolaj

Re: [Vim-latex-devel] ugly bug (?) with folding

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

Hey Fabio,

I fixed this bug.
I'll upload the newer version sometime this afternoon.

Thanks,
Srinath

On 15 Nov 2002, Fabio Spelta wrote:

> Hi.
> I got a file structured this way:
>
> \chapter{ch_name}
> 	\section{xxx}
> 	\section{yyy}
> \chapter{ch2_name}
> 	\section{zzz}
> 	\section{qqq}
>
> Folding does not work.
> When it starts or when I fold it up with <F6> the result is:
>
> \chapter{ch_name}
> FOLD(xxx)
> FOLD(yyy)
> FOLD(zzz)
> FOLD(qqq)
>
> stop.
>
> The second chapter finish blobbed in one section.
> What can I do?
> Thank you.
>
>
> --
>   Fabio Spelta
>
>    email: fab...@ti...
>    jabber: fe...@ja...
>    ecdl project: http://ecdllibre.sf.net
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: To learn the basics of securing
> your web site with SSL, click here to get a FREE TRIAL of a Thawte
> Server Certificate: http://www.gothawte.com/rd524.html
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

-- 
Srinath Avadhanula
Nov 15 10:38am
British Israelites:
	The British Israelites believe the white Anglo-Saxons of
Britain to be descended from the ten lost tribes of Israel deported by
Sargon of Assyria on the fall of Sumeria in 721 B.C. ... They further
believe that the future can be foretold by the measurements of the
Great Pyramid, which probably means it will be big and yellow and in
the hand of the Arabs.  They also believe that if you sleep with your
head under the pillow a fairy will come and take all your teeth.
		-- Mike Harding, "The Armchair Anarchist's Almanac"

[Vim-latex-devel] Accents

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

I'd like to have the suite converting =E8 =E0 =F2 ... and so on into
\`e, \`a ... , not into \\varepsilon...
How can I do? (where I have to change some setting?)

Also; can I make that working also with letters inside a word, and not
only with single letters?
When I :abbreviated them, they worked only "by itself", but don't if
inside a word, like "perch=E8".

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

[Vim-latex-devel] ugly bug (?) with folding

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

Hi.
I got a file structured this way:

\chapter{ch_name}
	\section{xxx}
	\section{yyy}
\chapter{ch2_name}
	\section{zzz}
	\section{qqq}

Folding does not work.
When it starts or when I fold it up with <F6> the result is:

\chapter{ch_name}
FOLD(xxx)
FOLD(yyy)
FOLD(zzz)
FOLD(qqq)

stop.

The second chapter finish blobbed in one section. 
What can I do?
Thank you.
 

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

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

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

Please see

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

for how latex-suite does this.

Thanks,

Srinath

On 13 Nov 2002, Fabio Spelta wrote:

> Sorry...
> the output is:
>
>  makeprg=latex  \\nonstopmode \\input\{$*\}
>
> Anyway, it does'nt change... I have to run \ll on the first (main) file.
>
> --
>   Fabio Spelta
>

-- 
Srinath Avadhanula
Nov 13 11:36am
As long as I am mayor of this city [Jersey City, New Jersey] the great
industries are secure.  We hear about constitutional rights, free
speech and the free press.  Every time I hear these words I say to
myself, "That man is a Red, that man is a Communist".  You never hear a
real American talk like that.
		-- Frank Hague (1896-1956)

Re: [Vim-latex-devel] running latex; further thoughts

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

Hey Carl,

vim-latex already provides the mechanism to do this... The way to do
this will be to modify Tex_IgnoredWarnings to something like this:

> " this is the list of patterns which will be ignored from the compiler ou=
tput.
> " This is a handy way of specifying which warnings/errors to ignore. This=
 is a
> " list of patterns seperated by '=A1'
> TexLet g:Tex_IgnoredWarnings =3D
> =09\'Underfull=A1'.
> =09\'Overfull=A1'.
> =09\'specifier changed to=A1'.
> =09\'You have requested=A1'.
> =09\'Missing number, treated as zero.=A1'.
> =09\'There were undefined references=A1'.
> =09\'Citation %.%# undefined=A1'
>
> " the 'ignore level' of the 'efm'. A value of 4 says that the first 4 kin=
ds of
> " warnings in the list above will be ignored. Use the command TCLevel to =
set a
> " level dynamically.
> TexLet g:Tex_IgnoreLevel =3D 7

By default, you can have g:Tex_IgnoreLevel set to 7. This will ignore
all the citation reference missing and stuff. After you're doing doing
math, you can do

:TCLevel 4

which will begin showing you citation reference missing errors...

See

:help latex-suite-compiler

for further details.

Does that help?

Srinath

On Wed, 13 Nov 2002, Carl Mueller wrote:

> I had some more thoughts about running latex.
>
> 1.  As I have already said, on the first run, there are a lot of spurious
> warnings of the kind "Reference `xxx' undefined" because the .aux file ha=
s
> not yet been created.
>
> 2.  Even if this problem is fixed, there will be a problem with undefined
> citations (\cite{xxx}).  If you are like me, when you write an article, y=
ou
> work on the math first.  When the article is ready, then you run bibtex a=
nd
> work on getting the citations right.  One proposal was to automatically r=
un
> bibtex if necessary.  This would fail if the user has not yet updated his
> bibtex file to include the most recent references.  Probably, if he is
> working on the math, he will not even have moved his bibtex file to the
> current directory.  He just wants to check for math errors, and would not
> like it if vim-latex forced him to work on the references before he is re=
ady.
>
> I guess Knuth recognized this situation.  The latex program stops only fo=
r
> latex math errors.  The others are recorded in the .log file, but the use=
r
> can ignore them if he wants.
>
> So, maybe there should be 2 commands to run latex:
>
> 1.  \ll would only check for latex math errors.
>
> 2.  \LL would check for latex math errors, \ref{xx} errors, and \cite{xx}
> errors.  This would be the same as the current \ll command.
>
> -------------
>
> Another issue is that for math errors, the quickfix window doesn't show a=
ll
> of the information in the .log file.  For instance, for the line
>
>   There is a mistake here $2^{x$.  Can you see it?
>
> the quickfix window gives
>
>   test.tex|11 error| Missing } inserted.
>
> while the log file gives
>
>   ! Missing } inserted.
>   <inserted text>
> =09=09  }
>   l.11 There is a mistake here $2^{x$
> =09=09=09=09     .  Can you see it?
>   I've inserted something that you may have forgotten.
>   (See the <inserted text> above.)
>   With luck, this will get me unwedged. But if you
>   really didn't forget anything, try typing `2' now; then
>   my insertion and my current dilemma will both disappear.
>
> which is much more informative, especially with the broken
> line, which gives the position of the error.
>
> -------------
>
> EVEN MORE IMPORTANT!!, after running latex, the cursor is not moved to th=
e
> position of the error.  This feature is a part of emacs auctex, so I want=
ed
> to be sure I had it in auctex.vim.  I hope that vim will not be second be=
st
> to emacs.
>
> You might want to look at the following function.  After latex is run,
> calling the function splits the window, displays the relevant part of
> the .log file, and moves the cursor to the position of the error.  It mov=
es
> it to the correct line, and the correct position within the line.  It doe=
s
> that by looking at the broken line provided in the .log file.  The length
> of the first part of the broken line gives the position of the error
> within the line.  To keep track of which errors have been viewed, the
> function makes an extra indent in the .log file.
>
> --------------
>
> function! s:NextTexError()
>     only
>     edit +1 %<.log
>     if search('^l\.\d') =3D=3D 0
> =09edit #
> =09redraw
> =09call input("\nNo (More) Errors Found\n\nPress 'enter' to go on.")
>     else
> =09let linenumber =3D matchstr(getline('.'), '\d\+')
> =09let errorposition =3D col("$") - strlen(linenumber) - 4
> =09    "Put a space in the .log file so that you can see where you were,
> =09    "and move on to the next latex error.
> =09s/^/ /
> =09write
> =09split #
> =09exe "normal " . linenumber . "G" . errorposition . "lzz\<C-W>wzz\<C-W>=
w"
>     endif
> endfunction
>
> ----------------
>
> Best wishes,
> Carl Mueller
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Are you worried about
> your web server security? Click here for a FREE Thawte
> Apache SSL Guide and answer your Apache SSL security
> needs: http://www.gothawte.com/rd523.html
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

--=20
Srinath Avadhanula
Nov 13 11:16am
The goal of science is to build better mousetraps.  The goal of nature
is to build better mice.

[Vim-latex-devel] running latex; further thoughts

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

I had some more thoughts about running latex.

1.  As I have already said, on the first run, there are a lot of spurious
warnings of the kind "Reference `xxx' undefined" because the .aux file has
not yet been created.

2.  Even if this problem is fixed, there will be a problem with undefined
citations (\cite{xxx}).  If you are like me, when you write an article, you
work on the math first.  When the article is ready, then you run bibtex and
work on getting the citations right.  One proposal was to automatically run
bibtex if necessary.  This would fail if the user has not yet updated his
bibtex file to include the most recent references.  Probably, if he is
working on the math, he will not even have moved his bibtex file to the
current directory.  He just wants to check for math errors, and would not
like it if vim-latex forced him to work on the references before he is ready.

I guess Knuth recognized this situation.  The latex program stops only for
latex math errors.  The others are recorded in the .log file, but the user
can ignore them if he wants.

So, maybe there should be 2 commands to run latex:

1.  \ll would only check for latex math errors.

2.  \LL would check for latex math errors, \ref{xx} errors, and \cite{xx}
errors.  This would be the same as the current \ll command.

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

Another issue is that for math errors, the quickfix window doesn't show all
of the information in the .log file.  For instance, for the line

  There is a mistake here $2^{x$.  Can you see it?

the quickfix window gives

  test.tex|11 error| Missing } inserted.

while the log file gives

  ! Missing } inserted.
  <inserted text> 
		  }
  l.11 There is a mistake here $2^{x$
				     .  Can you see it?
  I've inserted something that you may have forgotten.
  (See the <inserted text> above.)
  With luck, this will get me unwedged. But if you
  really didn't forget anything, try typing `2' now; then
  my insertion and my current dilemma will both disappear.

which is much more informative, especially with the broken
line, which gives the position of the error.

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

EVEN MORE IMPORTANT!!, after running latex, the cursor is not moved to the
position of the error.  This feature is a part of emacs auctex, so I wanted
to be sure I had it in auctex.vim.  I hope that vim will not be second best 
to emacs.  

You might want to look at the following function.  After latex is run,
calling the function splits the window, displays the relevant part of
the .log file, and moves the cursor to the position of the error.  It moves
it to the correct line, and the correct position within the line.  It does
that by looking at the broken line provided in the .log file.  The length
of the first part of the broken line gives the position of the error
within the line.  To keep track of which errors have been viewed, the
function makes an extra indent in the .log file.

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

function! s:NextTexError()
    only
    edit +1 %<.log
    if search('^l\.\d') == 0
	edit #
	redraw
	call input("\nNo (More) Errors Found\n\nPress 'enter' to go on.")
    else
	let linenumber = matchstr(getline('.'), '\d\+')
	let errorposition = col("$") - strlen(linenumber) - 4
	    "Put a space in the .log file so that you can see where you were,
	    "and move on to the next latex error.
	s/^/ /
	write
	split #
	exe "normal " . linenumber . "G" . errorposition . "lzz\<C-W>wzz\<C-W>w"
    endif
endfunction

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

Best wishes,
Carl Mueller

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

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

Sorry...
the output is:

 makeprg=latex  \\nonstopmode \\input\{$*\}

Anyway, it does'nt change... I have to run \ll on the first (main) file.

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

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

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

> When you open up a tex file, what does
> 	:set makeprg?

makeprg=make

(???)

Mr. Fisher,
I got latest CVS and xdvi opens oly once.
\ll
seems to work and compile my file!

Thank you; bye

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

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

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

Benji Fisher wrote:
>      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

      I meant to say "\ll", not "\lv".

      I think that the behavior noted by Fabio is to be expected. 
Calling RunLaTeX() usually invokes

:make foo

(or maybe :make foo.tex) if I am editing foo.tex .  You can type this 
form of the :make command yourself.  To save typing, try

:make %

      You can set things up so that main.tex does \include{chap1.tex} 
and, while editing chap1.tex, RunLaTeX() will invoke

:make main

which is what you want.  I do not see a good way to enable this feature 
and still have a plain

:make

work.

					--Benji