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

Re: [Vim-latex-devel] [Contact] passing a full path to Acrobat

[Berta M. <ber...@ar...>]

Hello Ryan,

I have a similar problem with Acrobat. But now I use GhostView
previewer.

If you go on with using Acrobat, you haven't close Acrobat everytime you
want to re-open the file. Closing the file (the opened window) with ^W
will works to.

Have a nice day, Milan


On Thu, Dec 02, 2004 at 02:39:07PM -0800, Ryan Krauss wrote:
> 
> I am having a problem with the latex viewer command.   It works correctly as long as 
> Acrobat is not already open, but if Acrobat is open, it says it can't find the file.  I was 
> able to duplicate the problem and a potential solution by typing the same commands 
> vim-latex is using directly into a dos command window open to the correct directory.  
> Acrobat seems to need the full path to the file if it is already open, even if the command 
> (i.e. start Acrobat filename) is coming from a DOS prompt open to the correct 
> directory.  Acrobat could handle this correctly if passed the full path to the file.  I 
> don't want to close Acrobat every time because it takes a while to open.  How can the 
> vim-latex command be made to include the full path to the pdf file?  
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] Switch off mappings by group

[Christian E. <bla...@gm...>]

hello,

Is there a possibility to switch off key mappings by group like
switching off the math menu in texrc with

TexLet g:Tex_MathMenus = 0

Do I have to edit main.cf by hand or have I overlooked something?

Very often I do stuff w/o math or greek, so the mappings get in
the way sometimes.

c
-- 
                               --->> <http://www.blacktrash.org/>

Re: [Vim-latex-devel] Problem with name starting with a number

[Berta M. <ber...@ar...>]

On Tue, Feb 08, 2005 at 05:36:22PM +0100, Fabio Stumbo wrote:
> Finally, I would like to ask a question to which I have not been able to 
> find an answer in the documentation: quite often I happen to edit plain 
> tex files. How can I toggle the command \ll to use "tex" instead of 
> "latex"?
> I defined
> 
> noremap \latex :let g:Tex_CompileRule_dvi = 'latex -src-specials 
> -interaction=nonstopmode $*'<CR>
> noremap \tex :let g:Tex_CompileRule_dvi = 'tex -src-specials 
> -interaction=nonstopmode $*'<CR>
> 
> in my .vimrc, so that I just type "\tex" once after starting and then \ll 
> works as I want, but I feel this is not the "best" way to achieve this.

I think this is the best way to solve this. If you edit and
compile plainTeX files once for a time, it is better to use
some mapping that edit the ${HOME}/.vimrc and there comment
or uncomment some lines.

For fifty:fifty usage of plainTeX and LaTeX maybe modeline
option can help:

----- begin (part of .vimrc) -----

" check three line for commands in each file
set modeline modelines=3

----- end (part of .vimrc) -----

I can image that I use often some files either in plain-
either in La- and their first (or last) [N] lines are next:

% vim:set let g:Tex_CompileRule_dvi = 'latex -src-specials -interaction=nonstopmode $*'

and similarly with tex program.

I use latex-suite for a quite long time (I am very satisfied
with it :) and also vim, but I don't know other way how to
solve this.

Have a nice day, Milan

[Vim-latex-devel] Problem with name starting with a number

[Fabio S. <f.s...@un...>]

Hi all,

I already wrote a message similar to this one but as unsubscribed user and 
I never got any kind of reply: maybe I made some error. So please forgive 
me if you just didn't reply because the question was not worth...

The point is that if I have a file starting with a number, when I start 
xdvi with \ls I get an error saying
"No references to source file ".tex" in DVI file."
Please remark that everything is well configured in order that reverse and 
forward search work properly. Moreover, renaming the very same with a name 
made only of letters everything works fine.

This is a problem coming, I guess, from xdvi and the way it is called 
within vim-latex. Reading from man xdvi:

      The  space before filename is only needed if the filename starts
      with a digit.  When the space is used, the argument needs to be
      enclosed  in quotes to prevent the shell from misinterpreting the
      space as argument separator.


I solved, for the moment, defining

noremap <F3> :exe '!xdvi -nofork -sourceposition "' . line (".") . ' ' . expand("%") . '" ' . expand("%:p:r"). " &" \| redraw!<cr>

in my .vimrc, but I don't know how to fix it in vim-latex.

Moreover, with  the same kind of file, sometime I experience a problem 
with the .log file: typesetting it over and over again with \ll, sometime 
I get and error from gvim saying that the log file is already open. But I 
have not been able to produce such error in a systematic way.

Finally, I would like to ask a question to which I have not been able to 
find an answer in the documentation: quite often I happen to edit plain 
tex files. How can I toggle the command \ll to use "tex" instead of 
"latex"?
I defined

noremap \latex :let g:Tex_CompileRule_dvi = 'latex -src-specials -interaction=nonstopmode $*'<CR>
noremap \tex :let g:Tex_CompileRule_dvi = 'tex -src-specials -interaction=nonstopmode $*'<CR>

in my .vimrc, so that I just type "\tex" once after starting and then \ll 
works as I want, but I feel this is not the "best" way to achieve this.

TIA and best greetings

Fabio Stumbo

[Vim-latex-devel] Suggested changes to bibtex.tex

[Berta M. <ber...@ar...>]

Hello,

I want to suggest the change of $VIM/latex-suite/bibtex.vim
file. I think its better for LaTeX and BIBTeX porgrams to
use the following syntax:

@ARTICLE{
  author = "A. Author",
  title = "Title T.",
  journal = "Journal J.",
  ...
}

not the following one, which is currently used:

@ARTICLE{
  author = {A. Author},
  title = {Title T.},
  journal = {Journal J.},
  ...
}

Of course so on with @BOOK and the other 12 items.

It's because of:
- "sth" means that it is the set of strings (and expected
  ending is the comma) and
- {sth} means that it should be taken to LaTeX without
  changing the case (to make some title lower-case), and it
  is sometimes used inside of "sth" (like this "sth1 {ST}h2
  sth3").
  
It is also a suggested construction for bibtex program
(search for documentation on BIBTeX program called btxdoc.ps
or btxdoc.pdf with Google).

I changed my own bibtex.vim file and it works for me the way
I want. I think it's not polite to send the whole file to
the conference, but the changes are not so big, so I attach
the file with differencies to the message (generated by diff
program).

If I am not right, plea and reclamation are welcome.

Greetings! Milan

Milan Berta
Faculty of Mathematics and Physics
Charles University, Prague

[Vim-latex-devel] Re: problem with converting greek letters

[Fabian B. <f.b...@gm...>]

Hi,

I found it :-)

Like with the 'tags'-stuff there was an old file in the same
directory as 'latex-suite' which converted these ...

Greetings!
-- 
Fabian Braennstroem
Duesseldorf/Berlin

[Vim-latex-devel] Re: problems with taglist and ctags

[Fabian B. <f.b...@gm...>]

Hello,

* VIM-Latex schrieb am 19 Jan 2005:

> 
> Hi,
> 
> sorry, it's me again, but unfortunately I have problems with
> the 'taglist.vim' plugin.
> I just read that about the new features from 2003-09-28 that
> 'taglist.vim' is supported:
> 
>     2.
>     taglist.vim support
> 
>     As I mentioned earlier taglist.vim is the most popular interface to
>     ctags (also popular program). Support is enabled by default. You have to
>     have only taglist.vim (2.8 is enough) and ctags (at least 5.0). You
>     don"t need to configure anything else.  Use :Tlist command (taglist.vim)
>     to open window with tags in current file.
> 
> Currently I am using 'vim-latex 20040314', 'taglist.vim'
> version 3.4 and 'ctags' version 5.5.4. So the requirements
> should be fullfilled.
> 
> On the other hand, I thought that ctags does not support any latex files
> and somehow it does not work for me to produce any tags-file!? So I used
> 'ltags' to produce a tag-file, but somehow invoking ':Tlist' for
> 'taglist' does not work on a latex-file (for my .vimrc it works nice)!?
> I get following error-message:
> 
>     Taglist: Failed to generate tags for /home/fab/HOME/HomePage/latex_dissertation.tex
>     ctags: Warning: Ignoring non-option in /home/fab/.ctags^@^@ctags:
>     Warning: Invalid content of \{\}^@ctags: Warning: Invalid content of
>     \{\}^@ctags: Unknown language specified in "language-force" option^@
>     Hit ENTER or type command to continue
> 
> That sounds that 'tagslist' wants to produce a tags-file again, but
> 'ctags' is not able to handle latex-files, isn't it?
> 
> Do you have an ideas to get my tags to work?

If anybody is interested: It works now :-)  I found some old
stuff which was not neede...

Greetings!

-- 
Fabian Braennstroem
Duesseldorf/Berlin

[Vim-latex-devel] Re: problem with converting greek letters

[Fabian B. <f.b...@gm...>]

Hallo VIM-Latex,

* VIM-Latex schrieb am 19 Jan 2005:

> Hi,
> 
> * VIM-Latex schrieb am 13 Jan 2005:
> 
> > 
> > Hi,
> > 
> > I am using vim-latex for a while now and like it a lot.
> > Unfortunately I have some problems with some characters.
> > Especially all my greek letters convert after saving the
> > document to some strange characters. The same happens to
> > german umlaut-characters, but just when I open up an old
> > latex-document which was written in emacs-auctex mode.
> > 
> > Could anybody tell me where I can find the setting for the
> > automatic conversion of the greek letters (the german
> > umlaute are not so important)?
> 
> Sorry, but does nobody have any idea or did I miss it in the
> manual?

I saw now that not only the greek letters, but also the the
smart mapping '\dots' converts to some unreadable characters
after saving. Of course, I could take this smart mapping
out, but there exist probably a better way.

Is there a way to turn this conversion off?

Greetings!
-- 
Fabian Braennstroem
Duesseldorf/Berlin

[Vim-latex-devel] FormatDependency

[Brian K. <bk...@gm...>]

I have a probelm getting vimlatex to compile either ps or pdf using
format dependency. Here are my vimrc settings.

let g:Tex_CompileRule_dvi = 'latex --src-specials -interaction=nonstopmode $*'
let g:Tex_CompileRule_ps = 'dvips -t letter -Ppdf -o $*.ps $*.dvi'
let g:Tex_FormatDependency_ps = 'dvi,ps'

If I have no format dependency and the dvi exists, a ps file is
produced. If I set the format dependency as shown, it produces a dvi
file, but not a post script file. I get similar behaviour for pdf's.
I'm using the csv version. I had the same problem with the latest
development version (December 19, 2004). Any ideas what might be
causing this?


-- 
Brian Keats

[Vim-latex-devel] problems with taglist and ctags

[Fabian B. <f.b...@gm...>]

Hi,

sorry, it's me again, but unfortunately I have problems with
the 'taglist.vim' plugin.
I just read that about the new features from 2003-09-28 that
'taglist.vim' is supported:

    2.
    taglist.vim support

    As I mentioned earlier taglist.vim is the most popular interface to
    ctags (also popular program). Support is enabled by default. You have to
    have only taglist.vim (2.8 is enough) and ctags (at least 5.0). You
    don"t need to configure anything else.  Use :Tlist command (taglist.vim)
    to open window with tags in current file.

Currently I am using 'vim-latex 20040314', 'taglist.vim'
version 3.4 and 'ctags' version 5.5.4. So the requirements
should be fullfilled.

On the other hand, I thought that ctags does not support any latex files
and somehow it does not work for me to produce any tags-file!? So I used
'ltags' to produce a tag-file, but somehow invoking ':Tlist' for
'taglist' does not work on a latex-file (for my .vimrc it works nice)!?
I get following error-message:

    Taglist: Failed to generate tags for /home/fab/HOME/HomePage/latex_dissertation.tex
    ctags: Warning: Ignoring non-option in /home/fab/.ctags^@^@ctags:
    Warning: Invalid content of \{\}^@ctags: Warning: Invalid content of
    \{\}^@ctags: Unknown language specified in "language-force" option^@
    Hit ENTER or type command to continue

That sounds that 'tagslist' wants to produce a tags-file again, but
'ctags' is not able to handle latex-files, isn't it?

Do you have an ideas to get my tags to work?

Best Greetings!

-- 
Fabian Braennstroem
Duesseldorf/Berlin

[Vim-latex-devel] Re: problem with converting greek letters

[Fabian B. <f.b...@gm...>]

Hi,

* VIM-Latex schrieb am 13 Jan 2005:

> 
> Hi,
> 
> I am using vim-latex for a while now and like it a lot.
> Unfortunately I have some problems with some characters.
> Especially all my greek letters convert after saving the
> document to some strange characters. The same happens to
> german umlaut-characters, but just when I open up an old
> latex-document which was written in emacs-auctex mode.
> 
> Could anybody tell me where I can find the setting for the
> automatic conversion of the greek letters (the german
> umlaute are not so important)?

Sorry, but does nobody have any idea or did I miss it in the
manual?

Greetings!
-- 
Fabian Braennstroem
Duesseldorf/Berlin

[Vim-latex-devel] [Contact] xdvi & -bug on solaris

[Rolf <vim...@so...>]

VIM 6.1 on Solaris with X11-Motif GUI

When opening a tex file in gvim directly 
hitting \lv loads xdvi. But when first the document is compiled \ll then xdvi doesn't 
show up anymore after \lv.
In fact any program started with ":!progam &" doesn't 
start. But ":!program" starts normaly.
"set noguipty" fixes the problem 
to.

May be vim bug, also appears with the vimspell package.  

[Vim-latex-devel] [Contact] Problems with Vim-Latex on Mac

[James <vim...@so...>]

Hello,

I've installed Vim 6.2 and the LaTeX-suite on my Mac which runs OS X 10.3.2, 
but I can't seem to get LatTeX to work properly.  (I installed the version of 
LaTeX-suite dated December 19, 2004 on the "Download" page.) I have problems ranging 
from minor to serious:

1.  The LaTeX-suite menus seem incomplete.  For example 
TeX-Suite -> Templates just shows numbers 1:,2:,3:, and 4:.  Shouldn't actually list 
the available templates like "article" etc.?

2.  To fold, the tutorial says "In 
normal mode, press \rf", but    how does this <mapleader> stuff work?  I know that I can 
refresh fold using the menu, but I would really like to use keystrokes.  Is there a 
reference that explains the use of mapleaders simply?

3.  Following the tutorial 
I tried \ref{<f9>} and \ref{<f9>, and a number of other variations, but I can't get the 
auto completion to work.  All I get is 'No bibkey, label or word beginning with "" ', even 
though \label{eqn:euler} is clearly there.  I'm not sure if this is relevant or not, 
but TLook and related commands seem to work fine.

4.  Compile doesn't seem to work 
properly.  When I envoke the compiler from the menu, in one window it says 

tcsh: 
Missing }  

and in the [Error List] it says 

:silent! call 
Tex_RunLaTex()

When I do

:call Tex_RunLaTex()

I get a bunch of errors 
(*not* E117: Unknown function though).  If I need to configure my compiler rules, 
g:Tex_CompileRule_dvi how do I find out what to change the default string 
to?

Thank you in advance for your help.

James  

[Vim-latex-devel] Re: which spellchecker

[Fabian B. <f.b...@gm...>]

Hi,

* Alexandre schrieb am 15 Jan 2005:

> Fabian Braennstroem a écrit :
> >Hi,
> >
> >I would like to which spell-checker you use for your
> >latex-documents?
> >In the beginning I use 'vimspell.vim', but it seems that it
> >does not work in conjunction with vim-latex. Did anybody had
> >the same experience?
> 
> Hi I use vimspell.vim and vim-latex together on a Debian-testing 
> environment. Few problems for now, Just from time to time the "space 
> allready defined" msg but no criticall error.

Unfortunately I have some more problems (like a lot of error
messages and opening an extra 'buffer'), but maybe it is
just some keybinding. I will check it again.
> 
> however, during the holydays, I tried to have them work together on 
> windows XP and they tdidn't seem to apreciate each other. Actually, even 
> using wimspell.vim alone was very difficult, since the wimspell mode 
> couldn't be disabled and the on-the-fly stuff was too slow for my typing.

Right now, I just using Linux, but good to know for the
future.

Thanks and Greetings!

-- 
Fabian Braennstroem
Duesseldorf/Berlin

[Vim-latex-devel] Re: which spellchecker

[Fabian B. <f.b...@gm...>]

Hi,

* Luc schrieb am 15 Jan 2005:

> Hello,
> 
> * On Thu, Jan 13, 2005 at 10:17:27AM +0100, Fabian Braennstroem <f.b...@gm...> wrote:
> > I would like to which spell-checker you use for your latex-documents?
> 
> Personnally I use the plugin I maintain every once and a while
> (lhVimSpell).  It has always been quite experimental and sometimes
> unstable.
 

Thanks! I will take a look at it.

Greetings!
-- 
Fabian Braennstroem
Duesseldorf/Berlin

Re: [Vim-latex-devel] which spellchecker

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

Hello,

* On Thu, Jan 13, 2005 at 10:17:27AM +0100, Fabian Braennstroem <f.b...@gm...> wrote:
> I would like to which spell-checker you use for your latex-documents?

Personnally I use the plugin I maintain every once and a while
(lhVimSpell).  It has always been quite experimental and sometimes
unstable.

> I would like to have the flyspell feature, but as I know it
> 'vimspell.vim' is the only one who can do it.

lhVimSpell does not support the flyspell feature.

HTH,
-- 
Luc Hermitte
http://hermitte.free.fr/vim/

[Vim-latex-devel] which spellchecker

[Fabian B. <f.b...@gm...>]

Hi,

I would like to which spell-checker you use for your
latex-documents?
In the beginning I use 'vimspell.vim', but it seems that it
does not work in conjunction with vim-latex. Did anybody had
the same experience?
I would like to have the flyspell feature, but as I know it
'vimspell.vim' is the only one who can do it.
Maybe, you guys have some hints!?

Best Greetings!
Fabian

[Vim-latex-devel] problem with converting greek letters

[Fabian B. <f.b...@gm...>]

Hi,

I am using vim-latex for a while now and like it a lot.
Unfortunately I have some problems with some characters.
Especially all my greek letters convert after saving the
document to some strange characters. The same happens to
german umlaut-characters, but just when I open up an old
latex-document which was written in emacs-auctex mode.

Could anybody tell me where I can find the setting for the
automatic conversion of the greek letters (the german
umlaute are not so important)?


Best Greetings!
Fabian

Re: [Vim-latex-devel] New Idea for vim-latex

[Marino <mar...@ya...>]

Srinath: I think its a great idea!

> 1. Calculating a difference which is not not line by line but sentence by
>      sentence or even word by word. I beleive that this is an easy problem.

Recently I came across a Vim tip which might give you a lead on how to implement the "easy part".
Please take a look at:

Tip #780: Generalized VISUAL CONTENT onto COMMAND-LINE
http://www.vim.org/tips/tip.php?tip_id=780

It deals with searching a long sentence which may be multiline in the document.

Marino


	
	
		
___________________________________________________________ 
ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com

[Vim-latex-devel] New Idea for vim-latex

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

Hello all,

Its been a long time since the list has seen any emails... I've been
busy and it looks like other than the occassional, "why can I not use my
alt keys" email, there have been no major bugs.

Recently, I was thinking of the next cool thing which could be done in
latex-suite. An idea came up while talking with a friend... I've written
up a description of the idea etc... Please take a look and see if you
think its interesting... I am open to ideas on how to implement this.

Idea follows:

Normally, we view the diff between two text files on a line by line basis.
This works fine for code where most logical structure is demarcated on a
line by line basis. (obfuscators notwithstanding). However, for flowing
text, which latex files resemble more than code, it does not quite make
sense to have differences highlighted on a line by line basis. "Units" of
language can be thought to be sentences. The idea is therefore, a way to
view a diff between two files in a non line by line manner.

Vertically diffsplit windows are also something which work only for line by
line diffs. So for example, suppose one of the files is this:

==================================================
Vertically diffsplit windows are also something
which work only for line by line diffs. For diffs
which do not follow the constraint of end of
lines, the most intuitive way to view diffs seems
to be to have a single window having one version
of the file which the differences basically shown
interpersed in the same view.
==================================================

and another is this

==================================================
Vertically diffsplit windows are also something
which work only for line by line diffs. For diffs
which do not follow the constraint of eol's, the
most intuitive way to view differences between
files seems to be to have a single window having
one version of the file which the differences
basically shown interpersed in the same view.
==================================================

Note how the change from "end of line" to "eol" makes two lines change,
although logically, it was only one change. If we run a simple diff between
the two files using vim's native diffsplit, then apart from the first two
lines which are identical, every other line will show a diff. In actual fact,
there are only a couple of changes:

end of lines -> eol's
diffs -> differences between files

So what is needed is obviously a way to convey to the user the two actual
differences. This is a two part problem:

1. Calculating a difference which is not not line by line but sentence by
     sentence or even word by word. I beleive that this is an easy problem.
     I already have written up a simple python program which prints the word by
     difference. So for example, for the two files above, it would generate the
     following output:

      ==================================================
      Vertically diffsplit windows are also something
      which work only for line by line diffs. For diffs
      which do not follow the constraint of <+end of
      lines+><-eol's->, the most intuitive way to view <+diffs+><-differences 
between
      files-> seems
      to be to have a single window having one version
      of the file which the differences basically shown
      interpersed in the same view.
      ==================================================

2. Find a way to convey this diference to the user in a easily graspable way.
     This in my opinion is the hard part. Ideally, if Vim had in-line folding,
     the "<+original text+>" would be folded away and we would show a little "?"
     in its place. The "<-new text->" would be shown with the "<-" and "->"
     parts folded away and the "new text" colored differently. I tried Vince
     Ngeri's conceal patch and couldn't get it to work quite reliably...
     Whenever I split another window, strange things happen to the
     highlighting... The concealed text reappears etc... If someone can get it
     to work robustly, that will be cool. If someone can think of a completely
     different way to present the diff without the conceal patch, that will be
     even cooler. (I cannot think of a way).

Thanks,
Srinath

[Vim-latex-devel] Re: Bug#281904: loading files hangs with vim if main file is opened

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

On Thu, 18 Nov 2004, martin f krafft wrote:

> $ mkdir /tmp/latexhang
> $ cd !$
> $ touch a.tex a.tex.latexmain b.tex
> $ screen -dm vim a.tex
> $ vim b.tex
> [...]
>
> Some times, a ctrl-c enables the editing of b.tex.

I could reproduce this. Its a trivial bug to fix, sorry for taking so
long. What happens is that when you do:

screen -dm vim a.tex

vim has already created a .a.tex.swp file and then detached. Therefore,
when you do

vim b.tex

vim puts up the "This file is already being edited..." message and
expects the user to press a key to continue. But at this time,
latex-suite has already made some settings which makes this message
"dissapear". Infact, if you had pressed 'r', things would have
continued... But it looks like things have hung.

Please upgrade to the latest release to get the fix.


-- 
Srinath

NOTE: If you are not subscribed to vim-latex-devel, then further replies
 	  to the list will be silently ignored. Please subscribe if you wish to
 	  continue the thread, or use

 		From: vim...@so...valid
 		Reply-To: yo...@em...dress, vim...@li...

       in the header.

[Vim-latex-devel] (no subject)

[<naz...@no...>]

Hello,

I have been experiencing problems with completion under windows :

windows version : XP
gvim version : 6.3
latex-suite version : 1.5

I installed the grep program from the address given in the vim-latex
website : http://unxutils.sourceforge.net/
and changed the windows path environment accordingly to the binaries
location.
However, completion would not work at all,
Then, I found Ryan Krauss' post that specified that only cygwin grep
program would work because it was the only one which would give the file
name when given the "-H" option.
I installed cygwin, changed the path again and know it seems to work OK.
however, I have tried to compare the outputs given by both greps :

win-version :

C:\Vim>grep --version
grep (GNU grep) 2.4.2

Copyright 1988, 1992-1999, 2000 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


C:\Vim>grep -nH if _vimrc
_vimrc:6:set diffexpr=MyDiff()
_vimrc:7:function MyDiff()
_vimrc:9:  if &diffopt =~ 'icase' | let opt = opt . '-i ' | endif
_vimrc:10:  if &diffopt =~ 'iwhite' | let opt = opt . '-b ' | endif
_vimrc:12:  if arg1 =~ ' ' | let arg1 = '"' . arg1 . '"' | endif
_vimrc:14:  if arg2 =~ ' ' | let arg2 = '"' . arg2 . '"' | endif
_vimrc:16:  if arg3 =~ ' ' | let arg3 = '"' . arg3 . '"' | endif
_vimrc:17:  silent execute '!C:\Vim\vim63\diff ' . opt . arg1 . ' ' . arg2
. ' > ' . arg3
_vimrc:20:set guifont=Bitstream_Vera_Sans_Mono:h9:cANSI
_vimrc:28:" IMPORTANT: grep will sometimes skip displaying the file name
if you

cygwin version :


C:\Vim>grep --version
grep (GNU grep) 2.5

Copyright 1988, 1992-1999, 2000, 2001 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


C:\Vim>grep -nH if _vimrc
_vimrc:6:set diffexpr=MyDiff()
_vimrc:7:function MyDiff()
_vimrc:9:  if &diffopt =~ 'icase' | let opt = opt . '-i ' | endif
_vimrc:10:  if &diffopt =~ 'iwhite' | let opt = opt . '-b ' | endif
_vimrc:12:  if arg1 =~ ' ' | let arg1 = '"' . arg1 . '"' | endif
_vimrc:14:  if arg2 =~ ' ' | let arg2 = '"' . arg2 . '"' | endif
_vimrc:16:  if arg3 =~ ' ' | let arg3 = '"' . arg3 . '"' | endif
_vimrc:17:  silent execute '!C:\Vim\vim63\diff ' . opt . arg1 . ' ' . arg2
. ' > ' . arg3
_vimrc:20:set guifont=Bitstream_Vera_Sans_Mono:h9:cANSI
_vimrc:28:" IMPORTANT: grep will sometimes skip displaying the file name
if you

The versions are different but the outputs sound exactly the same to me.
So what is the difference ? Isn't there a way to avoid installing cygwin
in order to have completion working ?

thanks,

A. Fournier

P.D. I have also tried downloading the latest grep from gnuwin32 but it
still doesn't work

[Vim-latex-devel] Multiple Compile Won't Run BibTeX

[Ryan L. <rd...@gm...>]

I apologize if this is a duplicate.  I sent this yesterday but never
received a copy, even though I have set up my account to receive my
own messages.

I checked the archives and could not find the answer to this problem.
I am using gvim on Mac OS 10.3.  My target format is PDF.

When I compile, it will not run Bibtex.  The files and my bibtex
installation are not the problem, because if I run it manually
(:!bibtex filename) it works.

Here are the lines in my texrc:
TexLet g:Tex_MultipleCompileFormats = 'dvi,pdf'
TexLet g:Tex_BibtexFlavor = 'bibtex'
TexLet g:Tex_CompileRule_bib = g:Tex_BibtexFlavor . ' $*'

Any idea why multiple-compilation is not working?  Thank you.

[Vim-latex-devel] Multiple Compile Won't Run BibTeX

[Ryan L. <rd...@gm...>]

I checked the archives and could not find the answer to this problem. 
I am using gvim on Mac OS 10.3.  My target format is PDF.

When I compile, it will not run Bibtex.  The files and my bibtex
installation are not the problem, because if I run it manually
(:!bibtex filename) it works.

Here are the lines in my texrc:
TexLet g:Tex_MultipleCompileFormats = 'dvi,pdf'
TexLet g:Tex_BibtexFlavor = 'bibtex'
TexLet g:Tex_CompileRule_bib = g:Tex_BibtexFlavor . ' $*'

Any idea why multiple-compilation is not working?  Thank you.

Re: [Vim-latex-devel] [Contact] Unfolding All folds

[Christian E. <bla...@gm...>]

* Brent on Fri, Dec 10, 2004 at 01:32PM -0800:
> Is there a way to unfold all sections in a document?

zR
-- 
Nichts gibt so sehr das Gefühl der Unendlichkeit als wie die Dummheit
- Ödön von Horváth