In my personal copy of the latex-suite
(https://github.com/gerw/vim-latex-suite) I used the following change in
ftplugin/latex-suite/texviewer.vim to avoid those empty buffers.
Regards
Gerd
@@ -855,7 +856,8 @@ function! Tex_FindBibFiles()
call Tex_Debug(":Tex_FindBibFiles: ", "view")
Ok, found out that the empty buffers are not generated from compiling.
The empty buffers appear after opening quickfix window for cite completion.
Peter
On Sat, Feb 11, 2012 at 4:02 PM, Peter Vasil
wrote:
> It is strange, but I can't reproduce the problem anymore. Somehow the
> compilation does
It is strange, but I can't reproduce the problem anymore. Somehow the
compilation doesn't create empty buffers anymore. Maybe it was some
other setting which caused this. And yes I always create a file which
has .latexmain as extension. i.e if my main file is main.tex then I
create a file which is
Peter --
Can you give a minimal working example?
Also, let's say you have a file called:
test.tex
and you created a latexmain called:
test.latexmain
It is known that Vim-LaTeX will create an empty buffer called "test." To
get around this, name your latexmain:
test.tex.latexma
> When I compile the file, the cursor doesn't stay where I compiled.It
> always jumps to the beginnig of line.. Although it doesn't bother
> me, I wonder it happens to you too.
This happens to me too. You can always just use `` afterwards to go
back to the same spot. Or, you can make a mapping t
On Wed, Jun 18, 2008 at 01:14:10PM -0400, Ted Pavlic wrote:
> >>> :map \lz \ll\lv
>
> By putting that 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_
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 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
> >
> > be simpler than modifying Vim-LaTeX?
> >
> >
> Yes, it would. My solution was a result
>
> Wouldn't (in .vimrc):
>
> :map \lz \ll\lv
>
> 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
---
> 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! Tex_Se
>
>
> 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 offe
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! Tex_SetCompiler
> 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 wondere
On Wed June 18 2008, Simon Friedberger wrote:
> let g:Tex_ViewRuleComplete_pdf = 'evince $* &'
> didn't work I had to add a ".pdf"
> let g:Tex_ViewRuleComplete_pdf = 'evince $*.pdf &'
Btw, This beheavior is documented in:
vimfiles/ftplugin/latex-suite/texrc
Regards,
Till
signature.asc
Descripti
On Wed June 18 2008, Simon Friedberger wrote:
> I have two issues.
>
> a) I set "let g:Tex_ViewRuleComplete_pdf = 'evince $* &'" but it is not
> automatically opened after compilation, is that the desired behavior?
Iirc it should be enough to set it to 'evince' on UNIX/Linux systems, the
filenam
let g:Tex_ViewRuleComplete_pdf = 'evince $* &'
didn't work I had to add a ".pdf"
let g:Tex_ViewRuleComplete_pdf = 'evince $*.pdf &'
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services f
16 matches
Mail list logo
