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

Re: [Vim-latex-devel] Re: new dir for bibliography?

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

On Tue, Apr 08, 2003 at 01:33:50PM +0200, Luc Hermitte wrote:

Thanks for your reply. Knowing there is no sense to put effort in grep
issue I investigated how exactly LaTeX deals with bibliography files.

Results are encouraging. There can be only one \bibliography command in
file. It can be list of files with exact paths (no dealing with
TEXINPUTS) separated with commas. We have only to find \bibliography and
iterate through list and grep this files looking for bibkeys. This is
easy. If there is no \bibliography we will grep current directory looking
for *.bib and *.bbl files. No need for special variable. Also we should
check MainFile if there is \bibliography command. But should we check it
only if in current file this command doesn't exist? I think yes. But...
Ok small "algorithm"

Check if \bibliography exists in this file
Yes                    No        
Grep files from list   Grep files in directory  
                    \ /
                     Y
Grepadd current file for bibitem{
Check if in packages list is chapterbib
Yes
Check if current file is main file
Yes             No
END             Check if \bibliography exists in mainfile
                Yes                     No
                Grepadd files in list   Grepadd files in dir of mainfile
                                     \ /
                                      Y
                          Grepadd mainfile for bibitem{

The only problem I see is with .bbl files mentioned by Srinath.
\include accepts only .tex files . In addition grepping *.bbl files (as
is now) will grep half-products of regular bib files. I will change 
grep 'bibitem{' *.bbl into
grep 'bibitem{ *.tex
Is it right?
Diagram above will change slightly but it is easy to imagine, I will not
draw it again.

> > 			call <SID>Tex_c_window_setup()
> Where is this function defined ?

tex/texviewer.vim

Thanks again for your research.

m.

[Vim-latex-devel] Re: new dir for bibliography?

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

Hello,
* On Tue, Apr 08, 2003 at 10:12:18AM +0200, Mikolaj Machowski <mi...@wp...> wrote:
> I have got request to make possible looking for bibliography in other
> directory than directory of edited file.
> 
> The best solution is to use grep but it needs such combination:
> 
> 		elseif exists("s:type") && s:type =~ 'cite'
> 			let grep_prg = &grepprg
> 			set grepprg=grep\ -Hrn\ --include='*.bib'\ $*\ /dev/null
> 			exe 'silent! grep! "@.*{'.s:prefix.'" '.s:search_directory 

BTW, the use of quotes or double quotes may cause a problem with
&shellquote and &shellxquote.

Anyway, I have tried to set &grepprg by hand, but still, I'm not able to
use /usr/bin/grep (with your parameters) from my win32-vim + cygwin-bash
as shell. Actually, I think I have never been able to do so.
 [ grepprg == grep\ -Hrn\ --include='*.bib'\ $*  (± /dev/null)
 [ :grep '@.*{' /cygdrive/c/localtexmf/bibtex
 [ -> E303: Can not open the .swp file for 
 [    "/cygdrive/c/localtexmf/bibtex/ASTORIA/astoria.bib", retrieval
 [    impossible ... or something like that.
 [ with:
 [ shellquote = 
 [ shellxquote="
 [ shell      =c:\cygwin\bin\bash.exe
 [ shellredir =>%s 2>&1
 [ shellpipe  = 2>&1| tee
 [ shellslash = 1

The same command from bash works very well, and don't require I propose
/dev/null as the last argument.
 

> [...]
> 			call <SID>Tex_c_window_setup()

Where is this function defined ?

> With changing value of &grepprg. Alas, I don't know how to make it
> cross-platform. grep is easy to configure (GNU grep compatible grep tool
> as requirement and variable in texrc) but what about /dev/null?
> Without that lS doesn't work on terminal. Maybe something like that
> (example line):
> 
> exe "set grepprg=".g:Tex_grepprg."\ -Hrn\ --include='*.bbl'\ $*".s:devnull

If the grep program is "findstr", ie the default win32-vim (called from
the file-explorer or $COMSPEC), I doubt that -Hrn or --include will be
supported.
Some of its various useful options are:
    /n -> print line numbers
    /S -> recursion
    /R -> use regular expressions
    /M -> only the filename of the matching files
    /D:r,p -> search in a list of directories delimited by semi-comma.
           [it seems there is a little error in the doc at this point]


> And at the beginning:
> if has("unix") || has("mac_unix") || has("cygwin")

Personnally, I'd rather test &sh =~'sh'. I found it more accurate than
has('cygwin').
BTW, I have developped a little plugin aimed at easying the development
of portable plugins -- I still have the documentation to finish and some
tests to conduct. So far it seems quite functional.[1] 

> How such combination would work on other than Linux systems?

Impossible to make it work on my system (cygwin-bash + win32-vim). :-(
I don't know if it is due to an error of configuration on my side or
anything else.

[1] http://hermitte.free.fr/vim/ressources/system_utils.tar.gz
    html version of the documentation at:
    http://hermitte.free.fr/vim/ressources/vimfiles/doc/system_utils.html
-- 
Luc Hermitte
http://hermitte.free.fr/vim/

Re: [Vim-latex-devel] environments

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

On Mon, Apr 07, 2003 at 05:52:42PM +0100, Alessandro Platania wrote:
> Hi,
> I'm using vim latex with vim version 6.1.165, in Linux Redhat 8.0.
> If I press <F5> in the insert mode while on an empty line, I get
> the following error messages:
> Error detected while processing function
> Tex_FastEnvironmentInsert..Tex_package_from_line..Tex_pack_one..
> Tex_CreatePrompt:
> Line 3:
> E117: Unknown function: GetLisCount
> E15: Invalid expression: GetListCount(a:promptList)
> E121: Undefined variable: num_common
> E15: Invalid expression: i <= num_common
> ...and no list is displayed
> What's going on? (I'm a beginner... no doubt I did some mistakes...
> the vimlatex help seems to work, and many other features are OK...)

Hmm. I cannot confirm this behaviour - everything works for me, but:
If you exactly copy&paste messages it looks like there is a mispell:
> E117: Unknown function: GetLisCount

Try to find it and s/GetLisCount/GetListCount/ (List)

You can try to obtain version from CVS. Some nice addtitions in last
week :) (but beware cvs tarball - i have commit stupid mistake and
better wait till tomorrow)

m.

[Vim-latex-devel] latesSuite release

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

Hello,

I was looking  for few things on sf.net and I noticed latexSuite has no
official release yet. Maybe its time? Srinath - as an admin could you
take care of it?

m.
ps. Of course after solving BibDir dilemna. In next two days. OK?

[Vim-latex-devel] new dir for bibliography?

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

Hello,

I have got request to make possible looking for bibliography in other
directory than directory of edited file.

The best solution is to use grep but it needs such combination:

		elseif exists("s:type") && s:type =~ 'cite'
			let grep_prg = &grepprg
			set grepprg=grep\ -Hrn\ --include='*.bib'\ $*\ /dev/null
			exe 'silent! grep! "@.*{'.s:prefix.'" '.s:search_directory 
			set grepprg=grep\ -Hrn\ --include='*.bbl'\ $*\ /dev/null
			exe 'silent! grepadd! "bibitem{'.s:prefix.'" '.s:search_directory
			set grepprg=grep\ -Hrn\ $*\ /dev/null
			exe 'silent! grepadd! "bibitem{'.s:prefix.'" %'
			let &grepprg = grep_prg
			call <SID>Tex_c_window_setup()

With changing value of &grepprg. Alas, I don't know how to make it
cross-platform. grep is easy to configure (GNU grep compatible grep tool
as requirement and variable in texrc) but what about /dev/null?
Without that lS doesn't work on terminal. Maybe something like that
(example line):

exe "set grepprg=".g:Tex_grepprg."\ -Hrn\ --include='*.bbl'\ $*".s:devnull

And at the beginning:
if has("unix") || has("mac_unix") || has("cygwin")
	let s:devnull = '\ /dev/null'
else
	let s:devnull = ''
endif

How such compbination would work on other than Linux systems?

m.

[Vim-latex-devel] environments

[Alessandro P. <A.P...@st...>]

Hi,

I'm using vim latex with vim version 6.1.165, in Linux Redhat 8.0.
If I press <F5> in the insert mode while on an empty line, I get
the following error messages:

Error detected while processing function
Tex_FastEnvironmentInsert..Tex_package_from_line..Tex_pack_one..
Tex_CreatePrompt:
Line 3:
E117: Unknown function: GetLisCount
E15: Invalid expression: GetListCount(a:promptList)
E121: Undefined variable: num_common
E15: Invalid expression: i <= num_common

...and no list is displayed

What's going on? (I'm a beginner... no doubt I did some mistakes...
the vimlatex help seems to work, and many other features are OK...)
Thank you very much for your help and for vim-latex.

All the best

Alessandro

//////////////////////////////////////
//                                  //
//	Alessandro Platania         //
//	226 Cherry Hinton Rd        //
//	Cambridge CB1 4AW, GB       //
//                                  //
//	DPMMS                       //
//	Statistical Laboratory      //
//	Wilberforce Road            //
//	Cambridge CB3 0WB, GB       //
//	Tel: +44 1223 337922        //
//                                  //
//////////////////////////////////////

Re: [Vim-latex-devel] Bug report (xdvi inverse search)

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

On Sun, Apr 06, 2003 at 11:25:29PM +0200, S?ren Debois wrote:
> Hi there, 
> I've been experimenting with the inverse search facility for latex-suite 
> (i.e., making a click in the xdvi window warp my gvim to the appropriate 
> source file/line). The default distribution (March 25th 2003) doesn't work 
> for me, since the '%' in the "-editor ... " switch for xdvi seems to get 
> expanded by vim. 

Thanks.
BTW I have impression I did it few months ago... Maybe this is settings
specific?

m.

Re: [Vim-latex-devel] texviewer and Win

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

On Sat, 5 Apr 2003, Mikolaj Machowski wrote:

> > I think you are misunderstanding me... I mean that the <F9> key should
> > be customizable... For example, in imaps.vim, we first provide a map
> > called <Plug>IMAP_JumpForward and then map <C-j> to it if the user has
>
> Ah, I have already done that. The only thing I need to move mapping to
> <Plug> to some central place. main.vim?
>
No! Let the mappings remain in texviewer.vim... Since its in the
ftplugin/tex directory, they'll get executed every time anyway...

No need to clutter up main.vim with things its not meant for.

Srinath

-- 
Srinath Avadhanula
Apr 6 4:01pm
Join in the new game that's sweeping the country.  It's called
"Bureaucracy".  Everybody stands in a circle.  The first person to do
anything loses.

[Vim-latex-devel] Bug report (xdvi inverse search)

[<de...@di...>]

Hi there, 

I've been experimenting with the inverse search facility for latex-suite 
(i.e., making a click in the xdvi window warp my gvim to the appropriate 
source file/line). The default distribution (March 25th 2003) doesn't work 
for me, since the '%' in the "-editor ... " switch for xdvi seems to get 
expanded by vim. 

I've included a diff (beware! my very first attempt at constructing a 
patchable diff) that solves my problem. 

BTW, thanks for the splendid latexsuite!

-- 
Debois

Re: [Vim-latex-devel] uninstall

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

On Sat, Apr 05, 2003 at 01:11:13PM +0200, Andreas Wick wrote:
> How can I uninstall vim-latex?

Check http://vim-latex.sf.net site. Download section.
There is list of files.
In short:
from ftplugin dir:
latex-suite/
tex_latexSuite.vim
from plugin dir:
imaps.vim
libList.vim
SyntaxFolds.vim
from compiler dir:
tex.vim

m.m
-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/
Learn Touch Typing with Vim:
 http://vim.sourceforge.net/script.php?script_id=461
vim.pl - http://skawina.eu.org/mikolaj

Re: [Vim-latex-devel] texviewer and Win

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

On Fri, Apr 04, 2003 at 11:28:23AM -0800, Srinath Avadhanula wrote:
> On Thu, 3 Apr 2003, Mikolaj Machowski wrote:
> > > 3. Make the <F9> key customizable using the same technique in imaps.vim
> >
> > How customizable? As I wrote before I don't like here IMAPS mechanism.
> >
> I think you are misunderstanding me... I mean that the <F9> key should
> be customizable... For example, in imaps.vim, we first provide a map
> called <Plug>IMAP_JumpForward and then map <C-j> to it if the user has

Ah, I have already done that. The only thing I need to move mapping to
<Plug> to some central place. main.vim?

m.

[Vim-latex-devel] uninstall

[Andreas W. <an...@ca...>]

How can I uninstall vim-latex?

Andreas

Re: [Vim-latex-devel] texviewer and Win

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

On Thu, 3 Apr 2003, Mikolaj Machowski wrote:

> > 3. Make the <F9> key customizable using the same technique in imaps.vim
>
> How customizable? As I wrote before I don't like here IMAPS mechanism.
>
I think you are misunderstanding me... I mean that the <F9> key should
be customizable... For example, in imaps.vim, we first provide a map
called <Plug>IMAP_JumpForward and then map <C-j> to it if the user has
not already mapped some other key to <Plug>IMAP_JumpForward. This allows
people to use other keys according to their convinience. (I personally
use <C-Space> for imaps and have <C-j> mapped to <down> in insert mode).
This mechanism also allows a console user to use this functionality. As
of now, neither <F9> nor the menu mapping is available to a true console
user. This way at least we provide a way for him to construct something
for himself.

Srinath

[Vim-latex-devel] Partial compiling of document

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

Hello,

I am commiting function, menus and compiler if/else/endif
for compiling and viewing only part of document. Full documentation
tomorrow. Short description.

Mark fragment of document (Visual, mark, range). Press <F10> (TODO:
proper shortcut handling). Preamble of document (if needed from
mainfile) with \begin{document}, marked fragment and \end{document} will
be written to temporary file defined with tempname() Vim function. This
file will be compiled using current settings. Output files will be in
temporary directory. View main output file (dvi, pdf) with menu or \lp

You have take care about what is marked. You can use matchit.vim to
handle environments but that's all. Don't include begin/end document.

Please test it on other platforms (Windows, Mac) and if it works with
mainfile. Proper documentation and comments for code follow tomorrow. 

m.

Re: [Vim-latex-devel] texviewer and Win

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

On Wed, Apr 02, 2003 at 02:18:52PM -0800, Srinath Avadhanula wrote:
> Hey Mikolaj,
> This is very cool! It works out of the box for me :) (with a few small
> hitches which are "ignorable"). I wonder if you have some settings
> different.
> For me:
> shell=cmd.exe
> shellquote=
> shellxquote=
> grepprg=fgrep\ -n\ $*

'grep -n' doesn't give info about file name if only one file match.
I have add info about this in latex-suite.txt. I have grep from cygwin.
Where are coming from your fgrep? If this is standalone app maybe this
should be Official lS Grep Utility with link from download page and
special settings in texrc?

> A couple of suggestions:
> 1. In the cwindow, the first item always seems to be highlighted in
>    addition to the line on which the cursor is.

Highlighting of first line indicates current error number in quickfix
engine. Viewer use cwindow but not :cnext and :cprev. First of all - I don't
know how to get rid of this highlighting. Second - I am not sure if this
is really necessary. In this way you can always use quickfix methods.
IMO info about this in docs is enough (done).

> 2. Could you make the preview window show the label line in the center
>    of the preview window instead of at the top. Also make the preview
>    window larger. If possible make it customizable with some setting :)

Done.

> 3. Make the <F9> key customizable using the same technique in imaps.vim

How customizable? As I wrote before I don't like here IMAPS mechanism.

> 4. Put this as a menu item in "Tex-Suite->Complete Ref/Cite"

Done.

> Another thing is that as of now, citations are only searched for in .bib
> files. Often times, for small papers, I prefer the .bbl file which
> contains things like
> -----------------------------------%<-----------------------------------
> \begin{thebibliography}{99}
> 	\bibitem{shimoyama:93}
> 		I.~Shimoyama, H.~Miura, K.~Suzuki, and Y.~Ezura, ``Insect-like microrobots
> 		with external skeletons,'' {\em IEEE Control Sys. Magazine}, 13:37--41,
> 		February 1993.
> \end{thebibliography}
> -----------------------------------%<-----------------------------------
> Can support for this be built as well? Sometimes, the .bbl file is not
> used and the above can be directly inserted into the .tex file....

Done.
Strange thing. Vim (or grep) doesn't want look for "\\bibitem{", accepts
only "bibitem{". I hope it is robust enough.

m.
-- 
LaTeX + Vim = http://vim-latex.sourceforge.net/
Learn Touch Typing with Vim:
 http://vim.sourceforge.net/script.php?script_id=461
vim.pl - http://skawina.eu.org/mikolaj

[Vim-latex-devel] warning question: found the problem

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

I found the problem while reading the code, and this is something that
might be changed in the documentation.

The problem is that only the first g:Tex_IgnoreLevel items of
g:Tex_IgnoredWarnings are ignored, so if one adds something to
g:Tex_IgnoredWarnings, he must make sure that it is placed accordingly
in the list (ie before anything that should be considered an error) and
that g:Tex_IgnoreLevel has the correct value.

Alan

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

Re: [Vim-latex-devel] how is texrc processed ?

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

* Benji Fisher (be...@me...) wrote:
> Alan Schmitt wrote:
> >Hi,
> >
> >I'm playing with some options of the local copy of my texrc (the one in
> >ftplugin/tex), and some things do not work. For instance, I used to have
> >in my .vimrc the following:
> >let g:Tex_IgnoredWarnings =3D
> >	\'Underfull=A1'.
> >	\'Overfull=A1'.
> >	\'specifier changed to=A1'.
> >	\'You have requested=A1'.
> >	\'Missing number, treated as zero.=A1'.
> >	\'There were undefined references=A1'.
> >	\'Citation %.%# undefined=A1'.
> >	\'LaTeX Font Warning=A1'
> >
> >It worked as planned. I discovered I could put it in the texrc as:
> >TexLet g:Tex_IgnoredWarnings =3D
> >	\'Underfull=A1'.
> >	\'Overfull=A1'.
> >	\'specifier changed to=A1'.
> >	\'You have requested=A1'.
> >	\'Missing number, treated as zero.=A1'.
> >	\'There were undefined references=A1'.
> >	\'Citation %.%# undefined=A1'.
> >	\'LaTeX Font Warning=A1'
> >
> >But it does not work (ie I still get "LaTeX Font" warnings). It's as if
> >some other texrc was overriding this one.
> >
> >What am I doing wrong here ?
>=20
>      I am not sure what is going on, but I can tell you what :TexLet does=
.=20
> (This command is defined in texrc .)  It checks whether the variable is=
=20
> already defined.  If it is, :TexLet does nothing; if the variable is not=
=20
> already defined, :TexLet acts like :let .  In other words, the first use =
of=20
> :TexLet wins, whereas the last use of :let wins.
>=20
>      What should happen is that the user texrc is read before the default=
=20
> texrc, so that the user's :TexLet is effective.  Of course, your vimrc fi=
le=20
> gets read long before either texrc.  You can check that the texrc files a=
re=20
> read in the right order by using
>=20
> :scriptnames
>=20
>      I hope that points you in the right direction.

Thanks. It seems that scripts are read in the correct order. Moreover,
when I do an 'echo' of this variable, I get what I expect. I guess I
need to investigate more ;-)

Alan

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

Re: [Vim-latex-devel] how is texrc processed ?

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

Alan Schmitt wrote:
> Hi,
> 
> I'm playing with some options of the local copy of my texrc (the one in
> ftplugin/tex), and some things do not work. For instance, I used to have
> in my .vimrc the following:
> let g:Tex_IgnoredWarnings =
> 	\'Underfull¡'.
> 	\'Overfull¡'.
> 	\'specifier changed to¡'.
> 	\'You have requested¡'.
> 	\'Missing number, treated as zero.¡'.
> 	\'There were undefined references¡'.
> 	\'Citation %.%# undefined¡'.
> 	\'LaTeX Font Warning¡'
> 
> It worked as planned. I discovered I could put it in the texrc as:
> TexLet g:Tex_IgnoredWarnings =
> 	\'Underfull¡'.
> 	\'Overfull¡'.
> 	\'specifier changed to¡'.
> 	\'You have requested¡'.
> 	\'Missing number, treated as zero.¡'.
> 	\'There were undefined references¡'.
> 	\'Citation %.%# undefined¡'.
> 	\'LaTeX Font Warning¡'
> 
> But it does not work (ie I still get "LaTeX Font" warnings). It's as if
> some other texrc was overriding this one.
> 
> What am I doing wrong here ?

      I am not sure what is going on, but I can tell you what :TexLet does. 
(This command is defined in texrc .)  It checks whether the variable is already 
defined.  If it is, :TexLet does nothing; if the variable is not already 
defined, :TexLet acts like :let .  In other words, the first use of :TexLet 
wins, whereas the last use of :let wins.

      What should happen is that the user texrc is read before the default 
texrc, so that the user's :TexLet is effective.  Of course, your vimrc file gets 
read long before either texrc.  You can check that the texrc files are read in 
the right order by using

:scriptnames

      I hope that points you in the right direction.

					--Benji Fisher

Re: [Vim-latex-devel] texviewer and Win

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

Hey Mikolaj,

This is very cool! It works out of the box for me :) (with a few small
hitches which are "ignorable"). I wonder if you have some settings
different.

For me:

shell=cmd.exe
shellquote=
shellxquote=
grepprg=fgrep\ -n\ $*

(I put fgrep in my windows path)

If you want to use shell=bash, remember to also set
:set shellxquote='

otherwise fgrep is called as

bash -c "fgrep -n \\label{"

etc... Those double quotes make my shell prompt just hang...


A couple of suggestions:

1. In the cwindow, the first item always seems to be highlighted in
   addition to the line on which the cursor is.

2. Could you make the preview window show the label line in the center
   of the preview window instead of at the top. Also make the preview
   window larger. If possible make it customizable with some setting :)

3. Make the <F9> key customizable using the same technique in imaps.vim

4. Put this as a menu item in "Tex-Suite->Complete Ref/Cite"

Another thing is that as of now, citations are only searched for in .bib
files. Often times, for small papers, I prefer the .bbl file which
contains things like

-----------------------------------%<-----------------------------------
\begin{thebibliography}{99}
	\bibitem{shimoyama:93}
		I.~Shimoyama, H.~Miura, K.~Suzuki, and Y.~Ezura, ``Insect-like microrobots
		with external skeletons,'' {\em IEEE Control Sys. Magazine}, 13:37--41,
		February 1993.
\end{thebibliography}
-----------------------------------%<-----------------------------------

Can support for this be built as well? Sometimes, the .bbl file is not
used and the above can be directly inserted into the .tex file....

Srinath


On Wed, 2 Apr 2003, Mikolaj Machowski wrote:

> Hello,
>
> Yesterday I commited texviewer.vim file. It works as charm under Linux
> but on Windows it doesn't work at all. I have grep (from cygwin) but it
> looks like grep output was not intercepted.
> Can someone help me?
>
> Mikolaj
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ValueWeb:
> Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
> No other company gives more support or power for your dedicated server
> http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

-- 
Srinath Avadhanula
Apr 2 11:45am
(null cookie; hope that's ok)

[Vim-latex-devel] how is texrc processed ?

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

Hi,

I'm playing with some options of the local copy of my texrc (the one in
ftplugin/tex), and some things do not work. For instance, I used to have
in my .vimrc the following:
let g:Tex_IgnoredWarnings =3D
	\'Underfull=A1'.
	\'Overfull=A1'.
	\'specifier changed to=A1'.
	\'You have requested=A1'.
	\'Missing number, treated as zero.=A1'.
	\'There were undefined references=A1'.
	\'Citation %.%# undefined=A1'.
	\'LaTeX Font Warning=A1'

It worked as planned. I discovered I could put it in the texrc as:
TexLet g:Tex_IgnoredWarnings =3D
	\'Underfull=A1'.
	\'Overfull=A1'.
	\'specifier changed to=A1'.
	\'You have requested=A1'.
	\'Missing number, treated as zero.=A1'.
	\'There were undefined references=A1'.
	\'Citation %.%# undefined=A1'.
	\'LaTeX Font Warning=A1'

But it does not work (ie I still get "LaTeX Font" warnings). It's as if
some other texrc was overriding this one.

What am I doing wrong here ?

Alan

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

[Vim-latex-devel] texviewer and Win

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

Hello,

Yesterday I commited texviewer.vim file. It works as charm under Linux
but on Windows it doesn't work at all. I have grep (from cygwin) but it
looks like grep output was not intercepted.
Can someone help me?

Mikolaj

[Vim-latex-devel] (no subject)

[Babiker O. <bab...@ya...>]

Dear  sir
> 
> I am using  Vim -latex as editor for miktex on
win2000
> , however, I can only compile and view files from :
> C:\texmf\miktex\bin  .
> 
> I failed to compile and view files from other
folders  such as from  desktop ...

> Any  suggestions 
> yours 
> Babs 


__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com

[Vim-latex-devel] [vim-latex - Help] RE: Errors with vim-latex in windows

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

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=1949924
By: ihw

TexLet g:Tex_IgnoredWarnings = \'Underfull?.  \'Overfull?.  \'specifier changed
to?.  \'You have requested?.  \'Missing number, treated as zero?.  \'There were
undefined references?.  \'Citation %.%# undefined

put them into one line


______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/monitor.php?forum_id=173627

[Vim-latex-devel] Re: inverse search

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

Baris Erbas wrote:
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> 
> Dear Benji,
> Soory for the late reply. What I want to do is when I run gvim and then
> click on a file I want that file to be opened in the already opened gvim
> session. For this I start gvim with the --servername option but I
> couldnt get it to work.

      Again, this is not a helpful description of the problem.  *How* did it 
fail to work?

> The second problem I actually mentioned was when
> I compile my latex file by Latex-Suite and view it with yap viewer under
> Windows I want to be able to go back to my original file when I double
> click a line in the dvi file. I put different possible options under
> yap's menu for this such as --remote or --remote-wait but what happens
> is it goes to the already opened gvim session but does open a blank
> window and complains about not finding the file. When I look at the
> buffers menu I see
> c:\test\my_test
> c:\test
> ...
> lines. I assume it is trying to find files called as above which are
> actually the directories and the location of the file. So I am quite
> close to the solution but can not find the last option to add, so to
> speak.

      I think you have to use both the --remote (or --remote-wait) and the 
--servername options.  Have another look at

:help clientserver

I suggest you try to separate this into two problems.  First, figure out how to 
open a file in a running gvim from the command line.  Once that is working, try 
to get it to work from Yap.

HTH					--Benji Fisher

[Vim-latex-devel] RE: inverse search

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

*This message was transferred with a trial version of CommuniGate(tm) Pro*

Dear Benji,
Soory for the late reply. What I want to do is when I run gvim and then
click on a file I want that file to be opened in the already opened gvim
session. For this I start gvim with the --servername option but I
couldnt get it to work. The second problem I actually mentioned was when
I compile my latex file by Latex-Suite and view it with yap viewer under
Windows I want to be able to go back to my original file when I double
click a line in the dvi file. I put different possible options under
yap's menu for this such as --remote or --remote-wait but what happens
is it goes to the already opened gvim session but does open a blank
window and complains about not finding the file. When I look at the
buffers menu I see
c:\test\my_test
c:\test
...
lines. I assume it is trying to find files called as above which are
actually the directories and the location of the file. So I am quite
close to the solution but can not find the last option to add, so to
speak.

I would love to use linux but at work at least for the moment this is
not possible :-(

Thanks for any help

baris

> -----Original Message-----
> From: Benji Fisher [mailto:be...@me...] 
> Sent: Tuesday, March 25, 2003 4:49 PM
> To: Baris Erbas
> Subject: Re: inverse search
> 
> 
> *This message was transferred with a trial version of 
> CommuniGate(tm) Pro* Baris Erbas wrote:
> > *This message was transferred with a trial version of 
> CommuniGate(tm) 
> > Pro* Hi everybody! I have a problem with the inverse search under 
> > windows. I make gvim do inverse search under linux without any 
> > problems but at work place I have to use windows and I cant make it 
> > work. I start gvim with the --servername option and under 
> YAP's option 
> > for invese search I put the line
> > "C:\Program Files\vim\vim61\gvim.exe" --remote-wait %f
> > also I tried other varieties such as only remote or 
> --servername,etc.
> > But it resist to work!
> > 
> > What am I doing wrong?
> > 
> > By the way I use LatexSuite package.
> > 
> > Thanks all!
> > 
> > baris
> 
> Baris:
> 
>       I have not tried this because I do not want to boot my 
> nice Linux machine 
> into Windows.  I suggest either posting this to the vim-latex 
> list or posting 
> again to the vim users' list with a different subject (such 
> as "problem with 
> --remote").  Either way, be more specific about how it fails. 
>  Does vim start at 
> all?
> 
> HTH					--Benji
> 
>