Re: [Vim-latex-devel] Compilation creates empty buffers
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)
let mainfname = Tex_GetMainFileName(':p')
- exec 'new ' . fnameescape(mainfname)
+ split
+ exec 'silent! e '.fnameescape(mainfname)
if search('\\\(no\)\?bibliography{', 'w')
On 02/23/2012 11:49 AM, Peter Vasil wrote:
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
mailing_li...@petervasil.net wrote:
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 called main.tex.latexmain and everything works.
Sorry for the noise, but the empty buffers were quite annoying.
Peter
On Wed, Feb 8, 2012 at 9:45 PM, Ted Pavlict...@tedpavlic.com wrote:
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.latexmain
This is the name that Vim-LaTeX expects. It just happens that getting
rid of the tex mostly works...
--Ted
On 01/27/2012 06:58 AM, Peter Vasil wrote:
Hi,
I dont know if its just me but compilation creates an empty buffer
with the same name as the .tex file I compile.
Peter
--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
--
Ted Pavlict...@tedpavlic.com
--
Virtualization Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
___
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] Compilation creates empty buffers
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 called main.tex.latexmain and everything works. Sorry for the noise, but the empty buffers were quite annoying. Peter On Wed, Feb 8, 2012 at 9:45 PM, Ted Pavlic t...@tedpavlic.com wrote: 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.latexmain This is the name that Vim-LaTeX expects. It just happens that getting rid of the tex mostly works... --Ted On 01/27/2012 06:58 AM, Peter Vasil wrote: Hi, I dont know if its just me but compilation creates an empty buffer with the same name as the .tex file I compile. Peter -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel -- Ted Pavlic t...@tedpavlic.com -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] Compilation creates empty buffers
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.latexmain This is the name that Vim-LaTeX expects. It just happens that getting rid of the tex mostly works... --Ted On 01/27/2012 06:58 AM, Peter Vasil wrote: Hi, I dont know if its just me but compilation creates an empty buffer with the same name as the .tex file I compile. Peter -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel -- Ted Pavlic t...@tedpavlic.com -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] Compilation
On Wed, Jun 18, 2008 at 01:14:10PM -0400, Ted Pavlic wrote: :map \lz \ll\lvCR 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 PlugTex_Compile :call Tex_RunLaTeX()\|crcr 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, PlugTex_SaveCompileView, 'n', 'buffer') Is not necessary, see: :help autowrite Happy vimming Martin - 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-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] Compilation (Correction)
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 for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] Compilation
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 filename and ampersand are added by default. But it is not ViewRuleComplete but ViewRule that you need to change to 'evince'. Regards, Till signature.asc Description: This is a digitally signed message part. - 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-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] Compilation (Correction)
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 Description: This is a digitally signed message part. - 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-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] Compilation
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 pgpVLWOTkdkxp.pgp Description: PGP signature - 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-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] Compilation
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! SIDTex_SetCompilerMaps() I added call Tex_MakeMap(s:ml.lz, PlugTex_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 [EMAIL PROTECTED][EMAIL PROTECTED] 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-latex-devel@lists.sourceforge.net 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-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] Compilation
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 - 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-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
Re: [Vim-latex-devel] Compilation
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! SIDTex_SetCompilerMaps() I added call Tex_MakeMap(s:ml.lz, PlugTex_SaveCompileView, 'n', 'buffer') so that now \lz saves the tex file, compiles, and opens the viewer. Wouldn't (in .vimrc): :map \lz \ll\lvCR 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 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 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-latex-devel@lists.sourceforge.net mailto:Vim-latex-devel@lists.sourceforge.net 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-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel -- Ted Pavlic [EMAIL PROTECTED] - 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-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
