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

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

[Till M. <ope...@ti...>]

On Thu August 7 2008, Ted Pavlic wrote:

> So I wonder if something special should be added to the Vim-LaTeX
> documentation to instruct users to change their tex_flavor if they want
> empty .tex files to load Vim-LaTeX...

I added some documentation about it here:
http://vim-latex.sourceforge.net/index.php?subject=faq&title=FAQ#faq-not-loaded-vim7
http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html

Regards,
Till

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

[Ted P. <te...@te...>]

> Looking at the comments in /usr/share/vim/vim71/filetype.vim it may be a bug 
> im vim, because they default to plain instead of latex, when they do not find 
> any latex commands, but the comment says, they would default to latex. 
> Therefore this should be discussed with upstream first. Maybe they can be 
> persuaded to use latex as default for empty files that have a .tex suffix.

  From a message in vim_dev:

=====
In :h filetype, Vim 7.2c says that "If no keywords are found, it
defaults to plaintex", which is the current behavior when g:tex_flavor
is not defined. Maybe the comment is outdated.
=====

So I wonder if something special should be added to the Vim-LaTeX
documentation to instruct users to change their tex_flavor if they want
empty .tex files to load Vim-LaTeX...

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

[Ted P. <te...@te...>]

> Looking at the comments in /usr/share/vim/vim71/filetype.vim it may be a bug 
> im vim, because they default to plain instead of latex, when they do not find 

Excellent point. I posted a message (referencing your message here) to
the vim_use list. In retrospect, perhaps the vim-dev list would have
been better.

> Btw. it is possible to add a "plaintex_latexSuite.vim -> tex_latexSuite.vim" 
> symlink in the ftplugin dir of vim-latex, then vim-latex will also open for 
> empty .tex files. But I am not sure, whether or not this is a good solution.

Good point. Though, looking at those comments and the code, setting
g:tex_flavor seems like the preferred/sanctioned solution.

--Ted


-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

[Till M. <ope...@ti...>]

On Tue August 5 2008, Ted Pavlic wrote:
> > I have vim 7.1.245 from Fedora, which ships some tex.vim files.
> > Nevertheless vim-latex is still run, e.g. the folding is still done by
> > vim-latex and \ll runs latex. Maybe some features are not working, is
> > there some minimal tex file where something does not work for you without
> > setting tex_flavor? Or where may tex_flaveor be already set, it is not in
> > my .vimrc or
> > in /etc/vimrc.
>
> Try opening an empty file (e.g., "blah.tex") with no preamble.
>
> On my system, if Vim can't find a "\documentclass{article}", it defaults
> to plaintex. As a result, none of the Vim-LaTeX menus load in gvim (or
> mvim in my case) and none of the folding/shortcuts/etc. work.

Looking at the comments in /usr/share/vim/vim71/filetype.vim it may be a bug 
im vim, because they default to plain instead of latex, when they do not find 
any latex commands, but the comment says, they would default to latex. 
Therefore this should be discussed with upstream first. Maybe they can be 
persuaded to use latex as default for empty files that have a .tex suffix.

Btw. it is possible to add a "plaintex_latexSuite.vim -> tex_latexSuite.vim" 
symlink in the ftplugin dir of vim-latex, then vim-latex will also open for 
empty .tex files. But I am not sure, whether or not this is a good solution.

Regards,
Till

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

[Ted P. <te...@te...>]

> I have vim 7.1.245 from Fedora, which ships some tex.vim files. Nevertheless 
> vim-latex is still run, e.g. the folding is still done by vim-latex and \ll 
> runs latex. Maybe some features are not working, is there some minimal tex 
> file where something does not work for you without setting tex_flavor? Or 
> where may tex_flaveor be already set, it is not in my .vimrc or 
> in /etc/vimrc.

Try opening an empty file (e.g., "blah.tex") with no preamble.

On my system, if Vim can't find a "\documentclass{article}", it defaults 
to plaintex. As a result, none of the Vim-LaTeX menus load in gvim (or 
mvim in my case) and none of the folding/shortcuts/etc. work.

--Ted

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

[Eyolf Ø. <ey...@oe...>]

On 05.08.2008 (22:29), Till Maas wrote:
> 
> I have vim 7.1.245 from Fedora, which ships some tex.vim files. Nevertheless 
> vim-latex is still run, e.g. the folding is still done by vim-latex and \ll 
> runs latex. Maybe some features are not working, is there some minimal tex 
> file where something does not work for you without setting tex_flavor? Or 
> where may tex_flaveor be already set, it is not in my .vimrc or 
> in /etc/vimrc.

FWIW, I seem to remember that files without a preamble (i.e. when I use
latexprojects), would get a ft=plaintex if the tex_flavor wasn't set.

Eyolf



-- 
Han Solo:
	Oh! I thought they smelled bad on the *outside*!

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

[Till M. <ope...@ti...>]

On Tue August 5 2008, Ted Pavlic wrote:
> Till --
>
> 	Thanks for looking that up, but I'm not sure how it applies.
>
> 	As of Vim7, if you don't have:
>
> let g:tex_flavor='latex'
>
> then the default filetype behavior to a ".tex" file is to treat it as
> plaintex. In that case, Vim-LaTeX is not invoked at all and thus the
> texrc doesn't get run.

I have vim 7.1.245 from Fedora, which ships some tex.vim files. Nevertheless 
vim-latex is still run, e.g. the folding is still done by vim-latex and \ll 
runs latex. Maybe some features are not working, is there some minimal tex 
file where something does not work for you without setting tex_flavor? Or 
where may tex_flaveor be already set, it is not in my .vimrc or 
in /etc/vimrc.

> 	It looks like some native Vim compiler support was added in Vim7. That
> support wasn't there in 6, and so Vim-LaTeX would get started
> automatically. Now, in a vanilla Vim7 installation with no explicit
> g:tex_flavor set, Vim-LaTeX is ignored.

Here vim provides these files:
/usr/share/vim/vim71/compiler/tex.vim
/usr/share/vim/vim71/ftplugin/initex.vim
/usr/share/vim/vim71/ftplugin/plaintex.vim
/usr/share/vim/vim71/ftplugin/tex.vim
/usr/share/vim/vim71/syntax/initex.vim
/usr/share/vim/vim71/syntax/plaintex.vim
/usr/share/vim/vim71/syntax/tex.vim

I do not know how they interfer with vim-latex, though.

Regards,
Till

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

[Ted P. <te...@te...>]

Till --

	Thanks for looking that up, but I'm not sure how it applies.

	As of Vim7, if you don't have:

let g:tex_flavor='latex'

then the default filetype behavior to a ".tex" file is to treat it as 
plaintex. In that case, Vim-LaTeX is not invoked at all and thus the 
texrc doesn't get run.

	It looks like some native Vim compiler support was added in Vim7. That 
support wasn't there in 6, and so Vim-LaTeX would get started 
automatically. Now, in a vanilla Vim7 installation with no explicit 
g:tex_flavor set, Vim-LaTeX is ignored.

	I frequently respond to messages in other groups where people complain 
about Vim-LaTeX not getting loaded, and that's just because they 
upgraded to Vim7 and didn't know to add the flavor line to their vimrc. 
After that, everything is fine. For some reason, I never thought to post 
here and see if there was a way to modify the Vim-LaTeX distro so that 
setting g:tex_flavor wasn't necessary. <?>

	--Ted

Till Maas wrote:
> On Mon August 4 2008, Ted Pavlic wrote:
>> In the recent patches that were applied to Vim-LaTeX, was the line:
>>
>> 	let g:tex_flavor='latex'
>>
>> added somewhere? Without it, Vim7's filetype plugin fails to load
>> Vim-LaTeX. Something changed between Vim6 and Vim7 that made latex *not*
>> the default, which seems strange.
> 
> According to svn in the file trunk/vimfiles/ftplugin/latex-suite/texrc, there 
> was the following line since 2002-04-30:
> TexLet g:Tex_Flavor = 'latex'
> 
> This is the comment about it:
> " NOTE: The values of g:Tex_Flavor and g:Tex_CompilerFlags are provided as a
> "       way to make compiler/tex.vim standalone. i.e independent of the rest
> "       of latex-suite. These variables are NOT used if you have already
> "       defined g:Tex_CompileRule_dvi above.
> "
> " specifies the current latex flavor.
> 
> Hth,
> Till
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Seting TeX flavor properly in Vim7

[Till M. <ope...@ti...>]

On Mon August 4 2008, Ted Pavlic wrote:
> In the recent patches that were applied to Vim-LaTeX, was the line:
>
> 	let g:tex_flavor='latex'
>
> added somewhere? Without it, Vim7's filetype plugin fails to load
> Vim-LaTeX. Something changed between Vim6 and Vim7 that made latex *not*
> the default, which seems strange.

According to svn in the file trunk/vimfiles/ftplugin/latex-suite/texrc, there 
was the following line since 2002-04-30:
TexLet g:Tex_Flavor = 'latex'

This is the comment about it:
" NOTE: The values of g:Tex_Flavor and g:Tex_CompilerFlags are provided as a
"       way to make compiler/tex.vim standalone. i.e independent of the rest
"       of latex-suite. These variables are NOT used if you have already
"       defined g:Tex_CompileRule_dvi above.
"
" specifies the current latex flavor.

Hth,
Till

[Vim-latex-devel] Seting TeX flavor properly in Vim7

[Ted P. <te...@te...>]

In the recent patches that were applied to Vim-LaTeX, was the line:

	let g:tex_flavor='latex'

added somewhere? Without it, Vim7's filetype plugin fails to load 
Vim-LaTeX. Something changed between Vim6 and Vim7 that made latex *not* 
the default, which seems strange.


-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Compilation

[Martin S. <fo...@un...>]

On Wed, Jun 18, 2008 at 01:14:10PM -0400, Ted Pavlic wrote:
> >>> :map \lz \ll\lv<CR>
>
> By putting that <CR> in there, it should get you passed some of the
> "Press enter to continue" prompts after compilations. I don't use this
> method. It's just a guess.

In .vim/after/ftplugin/tex.vim:

if !has("gui_running")
  :nnoremap <buffer> <Plug>Tex_Compile :call Tex_RunLaTeX()\|<cr><cr>
endif

But it worked a lot better in vim 7.0, now I have to press enter once in
a while.

Also, the earlier mentioned

>> call Tex_MakeMap(s:ml."lz", "<Plug>Tex_SaveCompileView", 'n',
>> '<buffer>')

Is not necessary, see:
:help autowrite

Happy vimming

Martin

Re: [Vim-latex-devel] [ vim-latex-Bugs-1997889 ] `[, `(, `{ shortcuts mess up identation

[Martin S. <fo...@un...>]

On Thu, Jun 19, 2008 at 02:02:09PM +0000, SourceForge.net wrote:
> Summary: `[,`(,`{ shortcuts mess up identation
> 
> Initial Comment:
> this is a matrix i tried to add parentheses or brackets to

Thanks for the minimal example...

Anyways, just wanted to mention that the bug disappears using :set paste
(which obviously is no solution).

Cheers

Martin

Re: [Vim-latex-devel] forward search only for dvi?

[Till M. <ope...@ti...>]

On Thu June 19 2008, Simon Friedberger wrote:
> Does anybody have customizations or ideas how to adopt the forward
> search features for pdflatex + evince/xpdf/kpdf/whatever?

You can use pdfsync (a latex package) and okular (from KDE4) afaik. Probably 
you need to use the current svn version to make it easily work with 
vim-latex.

Regards,
Till

[Vim-latex-devel] forward search only for dvi?

[Simon F. <sim...@a-...>]

Does anybody have customizations or ideas how to adopt the forward
search features for pdflatex + evince/xpdf/kpdf/whatever?

Greetings
	Simon

[Vim-latex-devel] [ vim-latex-Bugs-1997889 ] `[, `(, `{ shortcuts mess up identation

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

Bugs item #1997889, was opened at 2008-06-19 14:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=1997889&group_id=52322

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: `[,`(,`{ shortcuts mess up identation

Initial Comment:
this is a matrix i tried to add parentheses or brackets to

	\begin{array}{cccc|ccc|cc}
		0	& 0	& 0	& 0	& 0	& 0	& 0	& 0	& 0 \\
		b_F	& a_F	& 0	& 0	& 0 	& 0	& 0	& 0	& 0 \\
		0	& v	& 0	& v 	& 0 	& 0	& 0	& 0	& 0 \\
		c_F	& 0	& 0	& 0	& -v 	& 0	& 0	& 0	& 0 \\
		\hline
		0	& 0	& 0	& 0	& 0 	& v	& 0	& 0	& 0 \\ 
		0	& 0	& 0	& 0	& 0 	& -3\frac{v}{L}	& 3\frac{v}{L}	& 0	& 0 \\
		0	& 0	& 0	& 0	& 0 	& 0	& 0	& 0	& 0 \\
		\hline
		0	& 0	& 0	& 0	& 0 	& 0	& 0	& 0	& v \\
		0	& 0	& 0	& 0	& 0 	& 0	& 0	& 0	& 0 
	\end{array}

this is the result for brackets

	\left[ 	\begin{array}{cccc|ccc|cc}
				0	& 0	& 0	& 0	& 0	& 0	& 0	& 0	& 0 \\
						b_F	& a_F	& 0	& 0	& 0 	& 0	& 0	& 0	& 0 \\
								0	& v	& 0	& v 	& 0 	& 0	& 0	& 0	& 0 \\
										c_F	& 0	& 0	& 0	& -v 	& 0	& 0	& 0	& 0 \\
												\hline
														0	& 0	& 0	& 0	& 0 	& v	& 0	& 0	& 0 \\ 
																0	& 0	& 0	& 0	& 0 	& -3\frac{v}{L}	& 3\frac{v}{L}	& 0	& 0 \\
																		0	& 0	& 0	& 0	& 0 	& 0	& 0	& 0	& 0 \\
																				\hline
																						0	& 0	& 0	& 0	& 0 	& 0	& 0	& 0	& v \\
																								0	& 0	& 0	& 0	& 0 	& 0	& 0	& 0	& 0 
																									\end{array}\right]


it may be a little hard to see and since pasting with ":set list" sadly just produces the same output believe me that a level of indentation is added on every line :)

same happens for parentheses and braces and no matter wether line or character visual selection is used





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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=1997889&group_id=52322

Re: [Vim-latex-devel] `( shortcut

[Till M. <ope...@ti...>]

On Wed June 18 2008, Simon Friedberger wrote:
> Using the `( shortcut in visual mode to create braces around a matrix
> thoroughly messes up indentation, maybe someone could check that.

Please create a bug report at
http://sourceforge.net/tracker/?group_id=52322&atid=466456
and provide there some latex code that can be used to easily reproduce the 
problem.

Regards,
Till

Re: [Vim-latex-devel] Compilation

[Ted P. <te...@te...>]

Simon Friedberger wrote:
> That's the solution I used though I believe that would be the better
> default behaviour for \ll or \lv.

I disagree. I think many people who have auto-refreshing PDF viewers 
(e.g., everyone on the floor of my department) would be upset by that 
change.

It's simple to add the behavior you want (by one of the myriad methods 
already described), and it's hard to get rid of it if it's there by default.

Additionally...

>>> :map \lz \ll\lv<CR>

By putting that <CR> in there, it should get you passed some of the 
"Press enter to continue" prompts after compilations. I don't use this 
method. It's just a guess.

--Ted


>>>
>>> be simpler than modifying Vim-LaTeX?
>>>
>>>
>> Yes, it would.  My solution was a result of i) being inclined to understand
>> better how latex-suite worked, and ii) being too stupid to think of using
>> "map".
>>
>> Best wishes, S
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

-- 
Ted Pavlic <te...@te...>

[Vim-latex-devel] `( shortcut

[Simon F. <sim...@a-...>]

Using the `( shortcut in visual mode to create braces around a matrix
thoroughly messes up indentation, maybe someone could check that.

Bye
	Simon

Re: [Vim-latex-devel] Compilation

[Simon F. <sim...@a-...>]

That's the solution I used though I believe that would be the better
default behaviour for \ll or \lv.


On 16:11 Wed 18.06.08, Simon Preston wrote:
> >
> > Wouldn't (in .vimrc):
> >
> > :map \lz \ll\lv<CR>
> >
> > be simpler than modifying Vim-LaTeX?
> >
> >
> Yes, it would.  My solution was a result of i) being inclined to understand
> better how latex-suite worked, and ii) being too stupid to think of using
> "map".
> 
> Best wishes, S

Re: [Vim-latex-devel] Compilation

[Simon P. <pre...@gm...>]

>
> Wouldn't (in .vimrc):
>
> :map \lz \ll\lv<CR>
>
> be simpler than modifying Vim-LaTeX?
>
>
Yes, it would.  My solution was a result of i) being inclined to understand
better how latex-suite worked, and ii) being too stupid to think of using
"map".

Best wishes, S

Re: [Vim-latex-devel] compiling with wrong cross-references

[Ted P. <te...@te...>]

It occurs to me that something else should probably be committed to the 
repo.

As discussed on the vim-mac mailing list, on line 43 of compiler.vim, 
there's a line that **SHOULD** be:

if !(has('win32') || has('macunix')) &&
(!Tex_GetVarValue('Tex_UseMakefile') || (glob('makefile*') == '' &&
glob('Makefile*') == ''))

In other words, *BOTH* Windows and Mac users should have the ability to 
leave their view rules empty because the OS will automatically kick off 
an associated viewer for them (using "open" for OS/X and "start" for 
Windows, as discussed).

Of course, if we added the xdg-open stuff, this line would have to be 
modified to allow Linux users to have empty view rules.

--Ted



Till Maas wrote:
> I just commited a changeset to improve all this:
> 
> http://vim-latex.svn.sourceforge.net/viewvc/vim-latex?view=rev&revision=1039
> 
> Regards,
> Till
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Compilation

[Ted P. <te...@te...>]

> Yes, I think that is the standard behaviour.  It annoyed me a bit, so I 
> added in
> ~/vimfiles/ftplugin/latex-suite/compiler.vim the function:
> function! Tex_SaveCompileView()
>     silent! update
>     call Tex_RunLaTeX()
>     call Tex_ViewLaTeX()
> endfunction
> And inside "function! <SID>Tex_SetCompilerMaps()" I added
> call Tex_MakeMap(s:ml."lz", "<Plug>Tex_SaveCompileView", 'n', '<buffer>')
> so that now "\lz" saves the tex file, compiles, and opens the viewer.

Wouldn't (in .vimrc):

:map \lz \ll\lv<CR>

be simpler than modifying Vim-LaTeX?


A few other points:

1. Many Vim-LaTeX users have PDF (or DVI) viewers that do autorefreshing 
(Skim and TeXniscope in OS/X are terrific examples; Yap in Windows works 
too). In that case, \lv and \ll are all that's needed. Every time an \ll 
completes, the PDF viewer autorefreshes. On Linux, I *believe* kpdf 
autorefreshes (or did at one point).

2. If you really do need to call your PDF viewer EVERY TIME you build, 
you could add an "&& viewer" line in your CompileRule. That should be 
roughly equivalent to adding an "\lz" command (I understand that the 
viewer will get called more than is necessary when Vim-LaTeX runs latex 
several times, but it's a start).

3. Remember that Vim-LaTeX will pass your build target to "make" if it 
finds a Makefile in the current directory (additionally, if you have 
multiple TeX files, you can create a dummy file ending in ".latexmain" 
with the same root name as your main TeX file. That lets Vim-LaTeX know 
what to do when you call \lv (or \lz)). In that case, your makefile can 
do some of the heavy loading (e.g., running the viewer).

4. I've modded my own Vim-LaTeX so that if a flag is set and the target 
is DVI, it runs a dvi-to-pdf command *after* all of the latex runs 
(rather than creating a PDF on each latex run). A similar fix could be 
applied here. That is, if a flag is set, after everything in an "\ll" is 
done, run the viewer.

In the end, I think this problem is solved for most people by either:

*) having an auto-refreshing PDF viewer,

*) adding a ":map" command to their .vimrc that implements an "\lz"


HTH --
--Ted









> 
> Hope that helps,
> Simon
> 
> On Wed, Jun 18, 2008 at 11:21 AM, Simon Friedberger 
> <sim...@a-... <mailto:simon%2Bv...@a-...>> wrote:
> 
>      > Iirc it should be enough to set it to 'evince' on UNIX/Linux
>     systems, the
>      > filename and ampersand are added by default.
>     It does not work without.
> 
>      > But it is not ViewRuleComplete but ViewRule that you need to
>     change to 'evince'.
>     I think you misunderstood me. The command works I just wondered if it
>     should be executed automatically after compilation.
> 
>     Bye
>            Simon
> 
>     -------------------------------------------------------------------------
>     Check out the new SourceForge.net Marketplace.
>     It's the best place to buy or sell services for
>     just about anything Open Source.
>     http://sourceforge.net/services/buy/index.php
>     _______________________________________________
>     Vim-latex-devel mailing list
>     Vim...@li...
>     <mailto:Vim...@li...>
>     https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Compilation

[Simon P. <pre...@gm...>]

>
>
> b) Sometimes after compilation I get a "press a Button" message. So far
> only happened in conjunction with "latex ran once". So it doesn't seem
> to happen if latex runs multiple times.
>
>
On your second point, I also get this behaviour - haven't looked into it
though, and afraid I can offer no insight to why it happens.

Does anybody else know?

Regards, S

Re: [Vim-latex-devel] Compilation

[Simon P. <pre...@gm...>]

Simon,

Yes, I think that is the standard behaviour.  It annoyed me a bit, so I
added in
~/vimfiles/ftplugin/latex-suite/compiler.vim the function:

function! Tex_SaveCompileView()
    silent! update
    call Tex_RunLaTeX()
    call Tex_ViewLaTeX()
endfunction

And inside "function! <SID>Tex_SetCompilerMaps()" I added
call Tex_MakeMap(s:ml."lz", "<Plug>Tex_SaveCompileView", 'n', '<buffer>')

so that now "\lz" saves the tex file, compiles, and opens the viewer.

Hope that helps,
Simon

On Wed, Jun 18, 2008 at 11:21 AM, Simon Friedberger
<sim...@a-...<simon%2Bv...@a-...>>
wrote:

> > Iirc it should be enough to set it to 'evince' on UNIX/Linux systems, the
> > filename and ampersand are added by default.
> It does not work without.
>
> > But it is not ViewRuleComplete but ViewRule that you need to change to
> 'evince'.
> I think you misunderstood me. The command works I just wondered if it
> should be executed automatically after compilation.
>
> Bye
>         Simon
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

Re: [Vim-latex-devel] Compilation

[Simon F. <sim...@a-...>]

> Iirc it should be enough to set it to 'evince' on UNIX/Linux systems, the 
> filename and ampersand are added by default.
It does not work without.

> But it is not ViewRuleComplete but ViewRule that you need to change to 'evince'.
I think you misunderstood me. The command works I just wondered if it
should be executed automatically after compilation.

Bye
	Simon