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

[Vim-latex-devel] Open files in \input

[Udo H. <udo...@we...>]

Hello,

it would be convenient if one could easily open a file that is included
in another using \input. Since the file one is editing may be located in
a folder "far away" from the current one, this might be very convenient.
Is there any way to do this using vim-latexsuite?

Best,
Udo

Re: [Vim-latex-devel] After error during compilation cannot return to .tex document

[Udo H. <udo...@we...>]

On Wed, Mar 24, 2010 at 01:08:55AM +0300, ZyX wrote:
> Ответ на сообщение «[Vim-latex-devel] After error during compilation cannot 
> return to .tex document», 
> присланное в 13:57:01 23 марта 2010, Вторник,
> отправитель Udo Hortian:
> 
> Try <C-o> in normal mode.
Thanks. This seems to work (sometimes). But still I find it annoying to
find myself for example in the quickfix window (sometimes I do not want
to fix a warning immediately). So each time I have to switch back to
switch back to the main document for example with ctrl+ww. Is there a
way to tell vim-latexsuite to stay in the main window (the file I am
editing)?

Best,
Udo

Re: [Vim-latex-devel] Set TTarget automatically for specific files

[Udo H. <udo...@we...>]

Hi Ted,

On Wed, Mar 24, 2010 at 01:19:49PM -0400, Ted Pavlic wrote:
> > You might be able to add something for this in a .latexmain file, but
> > then you would need to have two files. The docs should give some more
> > information about the .latexmain file.
> 
> Another option is to create a Makefile that responds in your desired way 
> regardless of which target is called. Again, you would have two files, 
> but this way you could still execute easily execute your custom build 
> commands from the CLI as well as from within vim.
Thanks for this tip. It sounds to be quite universal to me, so I would
like to use it. I am not aware of having changed Tex_UseMakefile, so it
should default to 1. How can I test this? But when I just do \ll it
seems that the default target (dvi) is used and make is not called. How
can I make vim to call make <filename>?

Best,
Udo

[Vim-latex-devel] Strange symbols apprear instead of \

[Udo H. <udo...@we...>]

Dear vim-latexsuite developers and users,

I am happily using vim-latexsuite for quite a while and like it very
much, although there are still a few things I would like to improve.

One thing that is annoying me recently is the following: Instead of "\"
sometimes a strange symbol is shown. But it is just displayed as this
and when I copy it, it appears as normal "\", so I took a screenshot
that you can find here:

http://img3.imageshack.us/img3/2669/vimstrangesymbols.png

Sometimes also this appears:

http://img526.imageshack.us/img526/2873/vimstrangesymbols2.png

It appears only when I start gvim with a latex document. When I use vim
this does not happen.

Also it does not happen all the time and changes depending on the
position of my cursor. Sometimes I see the symbol from the first picture
just if the cursor is located over this "\".

Do you have any hints what might cause this?

Best,
Udo

Re: [Vim-latex-devel] latex-aware paragraph formatting

[ludovico v. <lud...@gm...>]

On 5/4/10, Mike Richman <mik...@gm...> wrote:
> I've attached a tex.vim that includes the solution I now use, which is
> mostly the result of a discussion on this list a few months ago.

thanks!

Re: [Vim-latex-devel] Syntaxerror Curley Braces

[Dan M. O. H. <dm...@st...>]

Den 4. mai 2010 kl. 02.05 skrev Vijay Kaul:
> Den 2. mai 2010 kl. 15.14 skrev iustifico:
>> Am 02.05.2010 um 00:12 schrieb Dan Michael Olsen Heggø:
>>> Den 1. mai 2010 kl. 22.51 skrev iustifico:
>>> 
>>>> I tryed the tutorial to get in touch with latex-suite. When I was in the position **** in the example below I typed "e^^" like in the tutorial suggested. To get e^{x}.
>>>> 
>>>> But after hitting "^^" this appeared: e^{}<++>}<++>}<++>
>>> 
>>> What vim version/variant do you use on what os? On my Mac, I get the same problem as you with MacVim, but I get the correct behaviour with Vim in Terminal. Both vim 7.2. 
>> 
>> I am using VI Improved 7.2 on MacOS Snow Leopard (latest version). I tried it now in the Terminal and it works fine. We seem to have the same issues.
> 
> I can't seem to get the problem to reproduce in Vim or MacVim... Steps to reproduce?

To reproduce, just type "e^^" in insert mode in a tex-document.... but I just discovered that it depends on the keyboard layout. I can reproduce this with my Norwegian keyboard layout (and many other European ones), but I get the correct behaviour with a US keyboard layout. So this has to do with the caret key acting differently with different keyboard layouts. On many European keyboard layouts, it's main role is as a diacritical mark, so after typing it, the character is actually highlighted until the next character is typed.

Since everything works fine in Terminal, I think this is more a MacVim issue than a Vim-Latex one. If you define you'r own mappings with carets, they will have the same problems (I tried ":imap ^^ hello"). I will file a MacVim bug on this, but I guess macros with the caret key are generally troublesome with these kinds of keyboard layouts. 

Re: [Vim-latex-devel] adding filetypes for invoking latex-suite

[Gary J. <gar...@sp...>]

On 2010-05-04, Vitali Karasenko wrote:
> Hello everyone,
> 
> I use firefox with the imperator plugin, which allows me to write in vim when I
> am writing a forum post. Since I frequently use forums which support latex it
> would be very useful if the latex-suite would startup when I am invoking gvim
> from within vimperator. Unfortunately vimperator opens a .tmp file, changing
> the filetype afterwards also isn't an option. The best way to solve this imo is
> to let latex-suite also start when I'm editing .tmp files, but i don't know
> where to change that.

There are a number of ways to do this.  If the temporary file has a
uniquely identifiable name--perhaps it includes "vimperator" or part
of the web site's URL--you can tell Vim that that name is a LaTeX
file.  If the name is too general for that, you might be able to
identify the file from its contents as well as its name.

How to do this is explained in Vim's help:

    :help 43.2
    :help new-filetype

You can look in $VIMRUNTIME/filetype.vim for examples of how Vim
determines the file type from name and contents.
$VIMRUNTIME/scripts.vim contains examples of how Vim determines the
file type from contents alone.

I use these techniques to determine when Vim is editing a file
created by the ViewSourceWith Firefox add-on and which contains an
e-mail message.  ViewSourceWith creates temporary files whose names
contain the web site's URL, so I have this rule in my
~/.vim/filetype.vim file:

    au! BufRead,BufNewFile webmail.spocom.com*.txt setfiletype mail

HTH,
Gary

[Vim-latex-devel] executing macros highlights curly braces

[Vitali K. <bis...@gm...>]

When I execute macros like $$ or any other latex-suite macro, every } gets
highlighted. I haven't found in the helpfile if it is intender or which
purpose it possibly might serve, but this annoys me anyways. How can I get
rid of this behaviour?
I have a strong feeling that this has something to do with my vim settings
and isn't a problem primarily with the latex-suite. I'm guessing that
attachments don't work with the mailing list, so I can post the code of my
_vimrc if needed, it's not that long. There isn't anything special about it
anyways, none of the settings should cause this, but maybe there is
something about the defaults that cause this. This is the only part of the
vimrc, that I don't know exactly what it does:

set nocompatible
source $VIMRUNTIME/vimrc_example.vim
source $VIMRUNTIME/mswin.vim
behave mswin

set diffexpr=MyDiff()
function MyDiff()
  let opt = '-a --binary '
  if &diffopt =~ 'icase' | let opt = opt . '-i ' | endif
  if &diffopt =~ 'iwhite' | let opt = opt . '-b ' | endif
  let arg1 = v:fname_in
  if arg1 =~ ' ' | let arg1 = '"' . arg1 . '"' | endif
  let arg2 = v:fname_new
  if arg2 =~ ' ' | let arg2 = '"' . arg2 . '"' | endif
  let arg3 = v:fname_out
  if arg3 =~ ' ' | let arg3 = '"' . arg3 . '"' | endif
  let eq = ''
  if $VIMRUNTIME =~ ' '
    if &sh =~ '\<cmd'
      let cmd = '""' . $VIMRUNTIME . '\diff"'
      let eq = '"'
    else
      let cmd = substitute($VIMRUNTIME, ' ', '" ', '') . '\diff"'
    endif
  else
    let cmd = $VIMRUNTIME . '\diff'
  endif
  silent execute '!' . cmd . ' ' . opt . arg1 . ' ' . arg2 . ' > ' . arg3 .
eq
endfunction

The files in my plugins folder are:

bufexplorer.vim
color_sample_pack.vim
FirstEffectiveLine.vim
imaps.vim
libList.vim
remoteOpen.vim
ScrollColor.vim
Sessionman.vim
SyntaxFolds.vim
filebrowser.vim

as always, suggestions and tips are highly welcome  ,)

regards, bishop

[Vim-latex-devel] adding filetypes for invoking latex-suite

[Vitali K. <bis...@gm...>]

Hello everyone,

I use firefox with the imperator plugin, which allows me to write in vim
when I am writing a forum post. Since I frequently use forums which support
latex it would be very useful if the latex-suite would startup when I am
invoking gvim from within vimperator. Unfortunately vimperator opens a .tmp
file, changing the filetype afterwards also isn't an option. The best way to
solve this imo is to let latex-suite also start when I'm editing .tmp files,
but i don't know where to change that.

If you have any solutions, please let me know

regards, bishop

[Vim-latex-devel] latex-aware paragraph formatting

[ludovico v. <lud...@gm...>]

first of all, thanks to all vim-latex developers for their awesome work.

i'd like to know what is the best solution for having latex-aware
paragraph formatting using the "gwip" command (format inner
paragraph).

i searched on the web and on this mailing list and i've seen some
solutions and lots of discussion on the topic. So, what's the best way
to achieve this? What do you use?

maybe using an external reformatter? Is there al latex-equivalent for
the tidy program (which only works on HTML code)?

Will this feature be included in vim-latex in the future?

thanks from a vim-addicted newbie

Re: [Vim-latex-devel] Syntaxerror Curley Braces

[Vijay K. <vij...@gm...>]

I can't seem to get the problem to reproduce in Vim or MacVim... Steps to reproduce?

On 2 May 2010, at 9:08 , Mario Santagiuliana wrote:

> No problem for me, I am on fedora 12, my packages are:
> $ rpm -qa|grep vim|sort
> vim-common-7.2.411-1.fc12.x86_64
> vim-enhanced-7.2.411-1.fc12.x86_64
> vim-latex-1.8.23-1.20091230.r1079.fc12.noarch
> vim-latex-doc-1.8.23-1.20091230.r1079.fc12.noarch
> vim-minimal-7.2.411-1.fc12.x86_64
> vim-X11-7.2.411-1.fc12.x86_64
> 
> 
> In data 2/5/2010 00:12:02, Dan Michael Olsen Heggø ha scritto:
>> Den 1. mai 2010 kl. 22.51 skrev iustifico:
>>> I tryed the tutorial to get in touch with latex-suite. When I was in the
>>> position **** in the example below I typed "e^^" like in the tutorial
>>> suggested. To get e^{x}.
>>> 
>>> But after hitting "^^" this appeared: e^{}<++>}<++>}<++>
>> 
>> What vim version/variant do you use on what os? On my Mac, I get the same
>> problem as you with MacVim, but I get the correct behaviour with Vim in
>> Terminal. Both vim 7.2.
>> 
>> Dan Michael
>> ---------------------------------------------------------------------------
>> --- _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> -- 
> Mario Santagiuliana
> www.marionline.it
> ------------------------------------------------------------------------------
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] Syntaxerror Curley Braces

[Mario S. <ma...@ma...>]

No problem for me, I am on fedora 12, my packages are:
$ rpm -qa|grep vim|sort
vim-common-7.2.411-1.fc12.x86_64
vim-enhanced-7.2.411-1.fc12.x86_64
vim-latex-1.8.23-1.20091230.r1079.fc12.noarch
vim-latex-doc-1.8.23-1.20091230.r1079.fc12.noarch
vim-minimal-7.2.411-1.fc12.x86_64
vim-X11-7.2.411-1.fc12.x86_64


In data 2/5/2010 00:12:02, Dan Michael Olsen Heggø ha scritto:
> Den 1. mai 2010 kl. 22.51 skrev iustifico:
> > I tryed the tutorial to get in touch with latex-suite. When I was in the
> > position **** in the example below I typed "e^^" like in the tutorial
> > suggested. To get e^{x}.
> > 
> > But after hitting "^^" this appeared: e^{}<++>}<++>}<++>
> 
> What vim version/variant do you use on what os? On my Mac, I get the same
> problem as you with MacVim, but I get the correct behaviour with Vim in
> Terminal. Both vim 7.2.
> 
> Dan Michael
> ---------------------------------------------------------------------------
> --- _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
-- 
Mario Santagiuliana
www.marionline.it

Re: [Vim-latex-devel] Syntaxerror Curley Braces

[Dan M. O. H. <dm...@st...>]

Den 1. mai 2010 kl. 22.51 skrev iustifico:

> I tryed the tutorial to get in touch with latex-suite. When I was in the position **** in the example below I typed "e^^" like in the tutorial suggested. To get e^{x}.
> 
> But after hitting "^^" this appeared: e^{}<++>}<++>}<++>

What vim version/variant do you use on what os? On my Mac, I get the same problem as you with MacVim, but I get the correct behaviour with Vim in Terminal. Both vim 7.2. 

Dan Michael

[Vim-latex-devel] Syntaxerror Curley Braces

[iustifico <ius...@gm...>]

Hello everyone, 

I tryed the tutorial to get in touch with latex-suite. When I was in the position **** in the example below I typed "e^^" like in the tutorial suggested. To get e^{x}.

But after hitting "^^" this appeared: e^{}<++>}<++>}<++>

As you can see, there are 2 wrong curley braces. What does that mean? Is this a bug or am I using the command wrong?

Thank you for any suggestion!
iustifico

%        File: test.tex
%     Created: Sa Mai 01 10:00 pm 2010 C
% Last Change: Sa Mai 01 10:00 pm 2010 C
%
\documentclass[a4paper]{article}
\usepackage[sumlimits]{amsmath}
\begin{document}
\begin{eqnarray}
  ****
  \label{eqn:euler}
\end{eqnarray}
\end{document} 

[Vim-latex-devel] Compilation opens up log file

[martin t. <mar...@gm...>]

Hi,

Everytime I compile using \ll (with multiple passes), the corresponding log
file gets loaded into the buffer.
It gets distracting when I recompile again as VIM warns about the file
changing since editing started (W11).
And the viewport in focus also shifts to the quicklist (I get a different
behaviour in my Linux installation - it goes back to the window I was on).

I am using MacVim with the latest vim-latex suite package.

Thanks!

Martin

Re: [Vim-latex-devel] inverse search with xdvi and okular

[Mario S. <ma...@ma...>]

Hy, I report here your first email and the email you send to me to make more order.

First email send to mailing-list:
> Hello,
> 
> I tried to use inverse search with vim-latex. But I couldn't use this
> 
> function with okular or xdvi.
> 
> With the old version, I can use xdvi with inverse search by set
> 
> let g:Tex_ViewRule_dvi="xdvi -editor 'gvim --servername latex-suite --remote-
> 
> silent'"
> 
> and run gvim with
> 
> "gvim --servername latex-suite --remote-silent"
> 
> In the new version, this won't work, I have tried to set
> 
> let g:Tex_ViewRule_dvi="xdvi -editor 'gvim --servername gvim --remote-silent'"
> 
> (both forward search (with "\ls") won't work)
> 
> or
> 
> let g:Tex_ViewRule_dvi="xdvi" (inverse search won't work.).
> 
> I am more inclined to use okular. So I tried to solve this with okular.
> 
> When I set "let g:Tex_ViewRule_dvi = 'okular'". It didn't work.
> 
> So I read the source file compiler.vim, and found that kdvi was obsolete. I
> 
> replaced all "kdvi" with "okular", and change
> 
> let execString = 'silent! !okular --unique
> 
> file:'.mainfnameRoot.'.dvi\#src:'.line('.') .expand("%")
> 
> to
> 
> "let execString = 'silent! !okular --unique
> 
> '.mainfnameRoot.'.dvi\#src:'.line('.').expand("%")
> 
> I can use okular with forward and backward search now?
> 
> I want to how to solve this with xdvi.
> 
> Kenneth

You write to me:
> Please See my email "inverse search with xdvi and okular"
> 
> I solved this with okular, but no luck with xdvi, the solution is similar to
> yours.
Is your compiler.vim patched with my patch or with your?

In my vim-latex version (from fedora):
$ rpm -q vim-latex
vim-latex-1.8.23-1.20091230.r1079.fc12.noarch

I can make forward search with \lv and \ls with my patch and using just this rule in vimrc:
let g:tex_flavor='latex'
let g:Tex_CompileRule_dvi='latex -src-specials -interaction=nonstopmode $*'
let g:Tex_ViewRuleComplete_dvi="xdvi -editor 'vim --servername test --remote'"
I start a new vim session with this:
$ vim --servername test
Than I open my dvi file from vim. The inverse search work, I can see my source in new vim 
session just opened.
-- 
Mario Santagiuliana
www.marionline.it

Re: [Vim-latex-devel] inverse search with xdvi and okular

[李磊 <ll...@16...>]

Dear Mario, 
This is my previous email.
      Kenneth 

Re: [Vim-latex-devel] vim-latex okular search forward

[Mario S. <ma...@ma...>]

I resolve partially the problem.

I change something in compiler.vim.
I add some rule for okular.
In attachment diff file from old compiler.vim file to new.

Now my configs line in vimrc for vim-latex are:
autocmd FileType tex setlocal spell spelllang=it
let g:tex_flavor='latex'
let g:Tex_CompileRule_dvi='latex -src-specials -interaction=nonstopmode $*'
let g:Tex_ViewRule_dvi = 'okular'
autocmd Filetype tex imap <C-i> <Plug>Tex_InsertItemOnThisLine
let g:Tex_ItemStyle_list = '\item <++>'

I can start okular and view dvi file with \lv.
I can start search forward in okular with \ls.

I have got one question: is it possible to start just one time okular with \ls and the second 
time I use \ls tell to okular to move the view in the specific line under the cursor and not 
open another time another okular view?

Can you give me a feedback?

Thank you.


In data 24/4/2010 01:17:24, Mario Santagiuliana ha scritto:
> Hy, I'm Mario Santagiuliana.
> I am an Italian Medical Student. Excuse me for my bad English.
> 
> I want to configure vim-latex to search forward in dvi file.
> I'm working on fedora 12 64-bit. My desktop enviroment is Kde 4.4.2 so I
> use Okular.
> 
> My vim installation:
> $ rpm -qa|grep vim|sort
> vim-common-7.2.411-1.fc12.x86_64
> vim-enhanced-7.2.411-1.fc12.x86_64
> vim-latex-1.8.23-1.20091230.r1079.fc12.noarch
> vim-latex-doc-1.8.23-1.20091230.r1079.fc12.noarch
> vim-minimal-7.2.411-1.fc12.x86_64
> vim-X11-7.2.411-1.fc12.x86_64
> 
> My vimrc configuration for vim-latex:
> autocmd FileType tex setlocal spell spelllang=it
> let g:tex_flavor='latex'
> let g:Tex_CompileRule_dvi='latex -src-specials -interaction=nonstopmode $*'
> let g:Tex_ViewRuleComplete_dvi = 'okular $*.dvi >/dev/null 2>&1 &'
> autocmd Filetype tex imap <C-i> <Plug>Tex_InsertItemOnThisLine
> let g:Tex_ItemStyle_list = '\item <++>'
> 
> In Okular I setup my editor with this line:
> vimx --remote-tab-silent +%l %f
> 
> I start to edit a tex file without problem in vim. Generally I edit file
> with: $ vimx --servername VIMX file.tex
> so from Okular I can performe inverse search into my vim just opened.
> From vim with \ll I can compile my code. With \lv I can open Okular e from
> that I can do inverse search.
> 
> With \ls I have nothing.
> 
> From bash I can open my dvi file and view the line that I remember from vim
> session. For example I edit line 45 and I want to view (search forward) my
> change, whit \ls I can't do that, from commad line (bash) I can do that:
> $ okular file.dvi#src:45
> 
> Have you got any suggestion?
> 
> Okular from versione 0.10 support forward search:
> http://okular.kde.org/news.php#itemOkular010released
> 
> Thank you very much :)
-- 
Mario Santagiuliana
www.marionline.it

[Vim-latex-devel] vim-latex okular search forward

[Mario S. <ma...@ma...>]

Hy, I'm Mario Santagiuliana.
I am an Italian Medical Student. Excuse me for my bad English.

I want to configure vim-latex to search forward in dvi file.
I'm working on fedora 12 64-bit. My desktop enviroment is Kde 4.4.2 so I use Okular.

My vim installation:
$ rpm -qa|grep vim|sort
vim-common-7.2.411-1.fc12.x86_64
vim-enhanced-7.2.411-1.fc12.x86_64
vim-latex-1.8.23-1.20091230.r1079.fc12.noarch
vim-latex-doc-1.8.23-1.20091230.r1079.fc12.noarch
vim-minimal-7.2.411-1.fc12.x86_64
vim-X11-7.2.411-1.fc12.x86_64

My vimrc configuration for vim-latex:
autocmd FileType tex setlocal spell spelllang=it
let g:tex_flavor='latex'
let g:Tex_CompileRule_dvi='latex -src-specials -interaction=nonstopmode $*'
let g:Tex_ViewRuleComplete_dvi = 'okular $*.dvi >/dev/null 2>&1 &'
autocmd Filetype tex imap <C-i> <Plug>Tex_InsertItemOnThisLine
let g:Tex_ItemStyle_list = '\item <++>'

In Okular I setup my editor with this line:
vimx --remote-tab-silent +%l %f

I start to edit a tex file without problem in vim. Generally I edit file with:
$ vimx --servername VIMX file.tex
so from Okular I can performe inverse search into my vim just opened.
From vim with \ll I can compile my code. With \lv I can open Okular e from that I can do inverse 
search.

With \ls I have nothing.

From bash I can open my dvi file and view the line that I remember from vim session. For example 
I edit line 45 and I want to view (search forward) my change, whit \ls I can't do that, from 
commad line (bash) I can do that:
$ okular file.dvi#src:45

Have you got any suggestion?

Okular from versione 0.10 support forward search:
http://okular.kde.org/news.php#itemOkular010released

Thank you very much :)
-- 
Mario Santagiuliana
www.marionline.it

[Vim-latex-devel] \lv error: Undefined variable s:viewer

[martin t. <mar...@gm...>]

HI all,

I get this error whenever I use \lv (after a successful compile):

Error detected while processing function Tex_ViewLaTeX:
line   34:
E121: Undefined variable: s:viewer
E116: Invalid arguments for function strlen(s:viewer)
E15: Invalid expression: strlen(s:viewer)
line   39:
E121: Undefined variable: appOpt
E15: Invalid expression: 'open '.appOpt.s:viewer.' $*.'.s:target
line   79:
E121: Undefined variable: execString
E116: Invalid arguments for function substitute(execString, '\V$*',
mainfname, '
g')
E15: Invalid expression: substitute(execString, '\V$*', mainfname, 'g')
line   80:
E121: Undefined variable: execString
E116: Invalid arguments for function Tex_Debug
line   82:
E121: Undefined variable: execString
E15: Invalid expression: 'silent! !'.execString

I can't find any info regarding s:viewer online unfortunately.

Additional info:
Using mVim on OS X 10.6, with the latest vim-latex from sourceforge. I have
not changed any of the view rules.

Thanks in advance for any help!

Cheers,

Martin

[Vim-latex-devel] inverse search with xdvi and okular

[lli03 <ll...@12...>]

Hello, 

I tried to use inverse search with vim-latex. But I couldn't use this 

function with okular or xdvi. 

With the old version, I can use xdvi with inverse search by set 

let g:Tex_ViewRule_dvi="xdvi -editor 'gvim --servername latex-suite --remote-

silent'"

and run gvim with 

"gvim --servername latex-suite --remote-silent"

In the new version, this won't work, I have tried to set 

let g:Tex_ViewRule_dvi="xdvi -editor 'gvim --servername gvim --remote-silent'" 

(both forward search (with "\ls") won't work)

or

let g:Tex_ViewRule_dvi="xdvi" (inverse search won't work.).

I am more inclined to use okular. So I tried to solve this with okular. 

When I set "let g:Tex_ViewRule_dvi = 'okular'". It didn't work.

So I read the source file compiler.vim, and found that kdvi was obsolete. I 

replaced all "kdvi" with "okular", and change 

let execString = 'silent! !okular --unique 

file:'.mainfnameRoot.'.dvi\#src:'.line('.') .expand("%")

to

"let execString = 'silent! !okular --unique 

'.mainfnameRoot.'.dvi\#src:'.line('.').expand("%")

I can use okular with forward and backward search now?

I want to how to solve this with xdvi.

Kenneth

Re: [Vim-latex-devel] indentation

[Gary J. <gar...@sp...>]

On 2010-04-04, fain182 wrote:
> Hello,
> i don't know how to indent my latex code..
> if i go to the first line with gg, and indent all with =G, the rules
> for indentation are wrong..(for example, indent if at the end of line
> there is a "\\" or a ",")
> 
> Vim-latexsuite includes latex indentation rules? How can i set them in
> my .vimrc?

Yes, the vim-latex-suite does include indentation rules.  They
should be in this file:  ~/.vim/indent/tex.vim.

They are enabled in your .vimrc the same as any other filetype
dependent indentation rules, with a command like this:
    
    filetype plugin indent on

See

    :help 30.3
    :help filetype-indent-on

HTH,
Gary

Re: [Vim-latex-devel] indentation

[fain182 <fa...@gm...>]

no one indents latex? or you use other tools?

2010/4/4 fain182 <fa...@gm...>:
> Hello,
> i don't know how to indent my latex code..
> if i go to the first line with gg, and indent all with =G, the rules
> for indentation are wrong..(for example, indent if at the end of line
> there is a "\\" or a ",")
>
> Vim-latexsuite includes latex indentation rules? How can i set them in
> my .vimrc?
>
> thank you
>
> --
> pietro
>



-- 
pietro

Re: [Vim-latex-devel] scrap from xpdf or evince in the screen

[Gastón A. <gar...@ie...>]

Thank you Martin! that's work fine!

let g:Tex_ViewRuleComplete_pdf = 'evince $*.pdf >/dev/null 2>&1 &'

2010/4/14 Martin Sander <mar...@tn...>:
> Hey,
>
> let g:Tex_ViewRuleComplete_pdf = 'okular $*.pdf >/dev/null 2>&1 &'
>
> or use gvim if you like gtk.
>
> Regards
>
> Martin
>



-- 
Gastón Araguás
______________________________________________________
CIII - Centro de Investigación en Informática para la Ingeniería
Univ. Tecnológica Nacional Facultad Regional Córdoba. Argentina

Re: [Vim-latex-devel] Question about Tex_UseMakefile

[Yan Z. <zho...@gm...>]

I check the script of vim-latex, it seems that it will change the makeprg anyway as long as the default format is set, i.e.,  as long as latex suite is loaded.

I put a filetype plugin, tex.vim in ~/.vim/after/ftplugin, The file contains the following code:

   if exists("did_load_tex_local_after")
       finish
   endif
   let did_load_tex_local_after=1
   
   set makeprg=make


The following are from the vim-manual. 

							                                        *after-directory*
	4. In the "after" directory in the system-wide Vim directory.  This is
	   for the system administrator to overrule or add to the distributed
	   defaults (rarely needed)
	5. In the "after" directory in your home directory.  This is for
	   personal preferences to overrule or add to the distributed defaults
	   or system-wide settings (rarely needed).

At least it seems to work, but I am not very sure if I got the right idea. I am just starting to learn about vim script. Previously I am merely a "user" who has little idea in which order vim load runtime files. 

I actually don't understand why latex-suite try to modify the makeprg in the first place. Since there is already function and hot-key to do the compilation of tex file. The makeprg should be left unmodified. In most cases make is used to manage larger projects with tex files as well as other files, e.g., R source code. So usually there is no reason to change it to something other than simply "make" or its variants.



On 13 Apr 2010, at 16:23, LAG Grimminck wrote:

> Sorry, I meant the vim manual. getcwd () is the function that determines
> the current directory and my guess is also what directory the Makefile
> should be in. What is the 'after directory'?
> 
> 
> On 04/13/2010 02:26 PM, Yan Zhou wrote:
>> They are not documented in the manual. The manual is rather incomplete, it's a user manual and one has to check the source code to find the problem.
>> 
>> However, I have used the after directory to overrule the vim-latex suite behaviour.
>> 
>> On 13 Apr 2010, at 08:47, LAG Grimminck wrote:
>> 
>> 
>>> Dear Yan,
>>> 
>>> .. put your TESTED Makefile in the directory where you let your
>>> vim-latex compile? Otherwise maybe you should check what vim-latex uses
>>> as current working directory internally, check the manual for that I think.
>>> 
>>> cheers,
>>> 
>>> Dennis
>>> 
>>> On 04/12/2010 08:06 PM, Yan Zhou wrote:
>>> 
>>>> Dear all,
>>>> 
>>>> I have a question about the Tex_UseMakefile. Whatever value I set it, either 1 or 0. The latex suite always define makeprg to whatever is defined by the g:Tex_CompileRule_target setting. How can I disable this behaviour and forbid latex suite to set the makeprg option?
>>>> 
>>>> Many thanks in advance.
>>>> 
>>>> Yan,
>>>> ------------------------------------------------------------------------------
>>>> Download Intel® Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> Vim-latex-devel mailing list
>>>> Vim...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>>> 
>>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Download Intel® Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev
>>> _______________________________________________
>>> Vim-latex-devel mailing list
>>> Vim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>> 
>> 
>