Thread: [Vim-latex-devel] (no subject)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

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

Hello,

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

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

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

Cheers.

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



Dear  sir

Thanks for your powerfull vim-Latex ..
I would be gratefull if u could show me how to convert
dvi output (within vim-latex console) to ms-word
 document..

yours
Dr.  Babiker Osman


__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com



On Sun, Jan 19, 2003 at 12:29:29AM -0800, Babiker Osman wrote:
> Dear  sir
> Thanks for your powerfull vim-Latex ..
> I would be gratefull if u could show me how to convert
> dvi output (within vim-latex console) to ms-word

I don't know any tool to make conversion dvi->ms-word.
Maybe you could use latex2html and then import its output
into Word.

Mikolaj



Hello, 

* On Sun, Jan 19, 2003 at 08:45:21PM +0100, Mikolaj Machowski <mi...@wp...> wrote:
> > Thanks for your powerfull vim-Latex ..
> > I would be gratefull if u could show me how to convert dvi output
> > (within vim-latex console) to ms-word
> 
> I don't know any tool to make conversion dvi->ms-word.  Maybe you
> could use latex2html and then import its output into Word.

There is quite an interresting tool able to convert word into LaTeX
(word2tex). I think the writer of the tool also provide another doing
the convertion in the other direction.

Otherwise, I guess it is also possible to convert the dvi/tex into pdf
and then use tools like acrobat writer to produce word-documents. It is
just another licence to buy.


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



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



Hello every body.  Thanks for the latest release of Latex Suite.
I am one who use the script extensively.  Thanks to all those
involved in the project.

I have found a bug, though.  The function keys F5, F9 and
F10 work only in the first file in the buffer.
Say, I have a main tex file run.tex.  I edit the file
with
gvim run.tex
Then go to an included file, say intro.tex, with
:e intro.tex
But the function keys F5 and F9 have no effect in intro.tex

The new part-compilation option is good, but not quiet
usefull for repeated use. Say, I select a part of the document
compile it with F10 which creates a tem file in /temp directory.
If I make some more corrections in the text, select the text
and again part compile it creates a new file in the /temp dir.
It would be nice if the new temp file overwrites the first so
that by pressing \ls and refreshing the dvi I can see the 
changes.

regards

Asokan




___________________________________________________
Get www. mycompany .com and 5 matching email ids.
Just Rs. 1499/ year.
Click here http://www.rediffmailpro.com




On Sun, 8 Jun 2003, Asokan  K wrote:

> I have found a bug, though.  The function keys F5, F9 and
> F10 work only in the first file in the buffer.
> Say, I have a main tex file run.tex.  I edit the file
> with
> gvim run.tex
> Then go to an included file, say intro.tex, with
> :e intro.tex
> But the function keys F5 and F9 have no effect in intro.tex

These problems have been fixed in the laest CVS. It will be a little
while before making another release.

> The new part-compilation option is good, but not quiet
> usefull for repeated use. Say, I select a part of the document
> compile it with F10 which creates a tem file in /temp directory.
> If I make some more corrections in the text, select the text
> and again part compile it creates a new file in the /temp dir.
> It would be nice if the new temp file overwrites the first so
> that by pressing \ls and refreshing the dvi I can see the
> changes.
>
I'll place this on the "to think about" list.

Srinath



On Sun, Jun 08, 2003 at 07:35:18AM -0000, Asokan  K wrote:
> The new part-compilation option is good, but not quiet
> usefull for repeated use. Say, I select a part of the document
> compile it with F10 which creates a tem file in /temp directory.
> If I make some more corrections in the text, select the text
> and again part compile it creates a new file in the /temp dir.
> It would be nice if the new temp file overwrites the first so
> that by pressing \ls and refreshing the dvi I can see the 
> changes.

Hmm. I made it specially this way. I was thinking to be possible to view
several versions of part of text besides with calling like:
:TShowPart 1
:TShowPart 2 and so on (of course nothing is implemented yet). But if
this is not very useful making it with one file should be at least
option?

m.



On Mon, 30 Jun 2003, Mikolaj Machowski wrote:

> On Sun, Jun 08, 2003 at 07:35:18AM -0000, Asokan  K wrote:
> > that by pressing \ls and refreshing the dvi I can see the
> > changes.
>
> Hmm. I made it specially this way. I was thinking to be possible to view
> several versions of part of text besides with calling like:
> :TShowPart 1
> :TShowPart 2 and so on (of course nothing is implemented yet). But if
> this is not very useful making it with one file should be at least
> option?

I changed the way the part compilation thing worked. The previous way
didn't make sense to me. Please read the docs for the current behavior.

I would also much prefer to come up with a short discussion about the
proposed behavior before implementing things. Implementing new behavior
unilaterally is not so healthy for the project in the long run.

The :TShowPart <n> behavior is nice, but again, _please_ put off on
implementing new features. We are still lacking in docs and bug-fixing.

Srinath



The changelog for the latest development version says that kdvi is now
supported. I tried "let g:Tex_ViewRule_dvi = 'kdvi'", but I still end up with
xdvi for viewing. Does anyone have this working?

Brian Keats




----------------------------------------
This mail sent through www.mywaterloo.ca



On Wed, 12 May 2004, Brian Keats wrote:

> The changelog for the latest development version says that kdvi is now
> supported. I tried "let g:Tex_ViewRule_dvi = 'kdvi'", but I still end up with
> xdvi for viewing. Does anyone have this working?
>
I cannot reproduce this. For me, if I set g:Tex_ViewRule_dvi = 'kdvi',
kdvi pops up as expected. Are you using the correct version?

Srinath



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



http://www.kstar.de/images/bestways.php





*
ahmet nurlu
http://www.killerrents.com/wp-content/plugins/yourpoint.php


-------------------
ahmet nurlu
Hi all,

Sorry if the format is wrong--first time submitting a patch anywhere. I
would like to submit the following  simple patch. See below for the details.

Best,

Zach

>From 7ed2740e40741dc58bf1dccc3dcdd54da0d25b5a Mon Sep 17 00:00:00 2001
From: "Zachary M. Boyd" <zb...@gm...>
Date: Thu, 11 Oct 2018 14:57:28 -0400
Subject: [PATCH] Fixed support for user-defined g:Tex_CompileRule_bib

Previously, the value of this variable was ignored.
Now, the trailing $* is stripped off, and then the variable is exec'ed
to run Bibtex.
---
 ftplugin/latex-suite/compiler.vim | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/ftplugin/latex-suite/compiler.vim
b/ftplugin/latex-suite/compiler.vim
index be9e267..d1dcc31 100644
--- a/ftplugin/latex-suite/compiler.vim
+++ b/ftplugin/latex-suite/compiler.vim
@@ -624,9 +624,14 @@ function! Tex_CompileMultipleTimes()
             let biblinesBefore = Tex_CatFile(bibFileName)

             echomsg "Running '".Tex_GetVarValue('Tex_BibtexFlavor')."' ..."
-            let temp_mp = &mp | let &mp =
Tex_GetVarValue('Tex_BibtexFlavor')
-            exec 'silent! make '.mainFileName_root
-            let &mp = temp_mp
+
+            " strip off the $* at the end of Tex_CompileRule_bib
+            if split(g:Tex_CompileRule_bib)[-1] !=# '$*'
+                let tmp_compileRule =
join(split(g:Tex_CompileRule_bib)[:-2])
+            else
+                let tmp_compileRule = g:Tex_CompileRule_bib
+            endif
+            exec 'silent !' . tmp_compileRule . ' ' . mainFileName_root

             let biblinesAfter = Tex_CatFile(bibFileName)


Thread: [Vim-latex-devel] (no subject)

vim-latex-devel