vim-latex-devel Mailing List for Vim-Latex (Page 7)
Brought to you by:
srinathava,
tmaas
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(120) |
Dec
(118) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(145) |
Feb
(23) |
Mar
(30) |
Apr
(50) |
May
(88) |
Jun
(49) |
Jul
(41) |
Aug
(13) |
Sep
(51) |
Oct
(30) |
Nov
(80) |
Dec
(43) |
2004 |
Jan
(15) |
Feb
(25) |
Mar
(48) |
Apr
(12) |
May
(37) |
Jun
(52) |
Jul
(16) |
Aug
(10) |
Sep
(7) |
Oct
(19) |
Nov
(17) |
Dec
(19) |
2005 |
Jan
(15) |
Feb
(5) |
Mar
(7) |
Apr
(3) |
May
(2) |
Jun
(4) |
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
(16) |
Dec
(16) |
2006 |
Jan
(15) |
Feb
(27) |
Mar
(49) |
Apr
(31) |
May
(24) |
Jun
(12) |
Jul
(23) |
Aug
(13) |
Sep
(22) |
Oct
(6) |
Nov
(8) |
Dec
(10) |
2007 |
Jan
(3) |
Feb
(13) |
Mar
(19) |
Apr
(1) |
May
(5) |
Jun
(10) |
Jul
(2) |
Aug
(13) |
Sep
(10) |
Oct
(2) |
Nov
(30) |
Dec
(15) |
2008 |
Jan
(11) |
Feb
(9) |
Mar
(27) |
Apr
(27) |
May
(22) |
Jun
(29) |
Jul
|
Aug
(21) |
Sep
(6) |
Oct
(4) |
Nov
(9) |
Dec
(2) |
2009 |
Jan
(52) |
Feb
(21) |
Mar
(9) |
Apr
(41) |
May
(13) |
Jun
(8) |
Jul
(5) |
Aug
(31) |
Sep
(14) |
Oct
(10) |
Nov
(17) |
Dec
(17) |
2010 |
Jan
(25) |
Feb
(22) |
Mar
(22) |
Apr
(24) |
May
(35) |
Jun
(23) |
Jul
(22) |
Aug
(10) |
Sep
(6) |
Oct
(29) |
Nov
(8) |
Dec
(6) |
2011 |
Jan
(12) |
Feb
(89) |
Mar
(41) |
Apr
(8) |
May
(17) |
Jun
(11) |
Jul
(3) |
Aug
(13) |
Sep
(14) |
Oct
(23) |
Nov
(8) |
Dec
(9) |
2012 |
Jan
(15) |
Feb
(27) |
Mar
(6) |
Apr
(17) |
May
(29) |
Jun
(9) |
Jul
(50) |
Aug
(15) |
Sep
(11) |
Oct
(12) |
Nov
(22) |
Dec
(7) |
2013 |
Jan
(24) |
Feb
(32) |
Mar
(6) |
Apr
(5) |
May
(2) |
Jun
(15) |
Jul
(20) |
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
(7) |
Dec
(4) |
2014 |
Jan
(3) |
Feb
(7) |
Mar
(4) |
Apr
|
May
(4) |
Jun
(5) |
Jul
(4) |
Aug
(3) |
Sep
(9) |
Oct
|
Nov
(2) |
Dec
(3) |
2015 |
Jan
|
Feb
(4) |
Mar
(9) |
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
(6) |
Sep
(2) |
Oct
|
Nov
(6) |
Dec
|
2016 |
Jan
(1) |
Feb
(11) |
Mar
(4) |
Apr
(2) |
May
(8) |
Jun
(9) |
Jul
|
Aug
(9) |
Sep
(2) |
Oct
(7) |
Nov
|
Dec
|
2017 |
Jan
(7) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
2018 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(1) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Mike R. <ri...@um...> - 2014-05-27 02:45:27
|
Hi Walter, I'd say this is a feature, not a bug. The idea is that you use <C-j> (control-J) to cycle through <++> markers. You write in the equation, press <C-j> and fill in the label, and press <C-j> again to get outside the equation environment where you can then press <enter> and continue writing the prose of the document. You can change this behavior by inserting the following into ~/.vim/ftplugin/tex.vim: call IMAP ('EEQ', \ . "\\begin{equation}\<cr><++>\<cr>" \ . "\\label{<++>}\<cr>" \ . "\\end{equation}", 'tex') Hope this helps. Cheers, Mike On Mon, May 26, 2014 at 9:03 PM, Walter Rabus <wal...@we...> wrote: > Hi, > > I noticed a weird behavior when expanding a line with the vim-latexsuite > and F5. Take the following code-snipped, pressing F5 in the line with > the upper "equation" the line gets expanded to the lower construct: > > \documentclass[12pt,a4paper,oneside]{article} > \usepackage{amssymb,amsmath} > \begin{document} > > equation > > \begin{equation} > foo > \label{<++>} > \end{equation}<++> > > \end{document} > > The problem I see with this is the <++> after "end{equation}" leads to > "¡++¿" in the final document when compiled. As I think this is not > intended to be there, I'd like to ask whether this is a bug or intended > behavior for some reason and whether someone can reproduce it. > > I tested it with the git-version of vim-latexsuite as well. > > If it can be confirmed to be a reproducable bug, I would like to propose > to remove the trailing "<++>" as I see no purpose it serves. > > > Walter > > ------------------------------------------------------------------------------ > The best possible search technologies are now affordable for all companies. > Download your FREE open source Enterprise Search Engine today! > Our experts will assist you in its installation for $59/mo, no commitment. > Test it for FREE on our Cloud platform anytime! > http://pubads.g.doubleclick.net/gampad/clk?id=145328191&iu=/4140/ostg.clktrk > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |
From: Walter R. <wal...@we...> - 2014-05-27 01:03:54
|
Hi, I noticed a weird behavior when expanding a line with the vim-latexsuite and F5. Take the following code-snipped, pressing F5 in the line with the upper "equation" the line gets expanded to the lower construct: \documentclass[12pt,a4paper,oneside]{article} \usepackage{amssymb,amsmath} \begin{document} equation \begin{equation} foo \label{<++>} \end{equation}<++> \end{document} The problem I see with this is the <++> after "end{equation}" leads to "¡++¿" in the final document when compiled. As I think this is not intended to be there, I'd like to ask whether this is a bug or intended behavior for some reason and whether someone can reproduce it. I tested it with the git-version of vim-latexsuite as well. If it can be confirmed to be a reproducable bug, I would like to propose to remove the trailing "<++>" as I see no purpose it serves. Walter |
From: Mark M. <mar...@gm...> - 2014-03-21 15:05:04
|
I am a new latex user so forgive the newbie nature of this but after a couple days searching Google and the list here I am still at a loss. I have a clean install of vim 7.4. It is installed locally at ~/local/linux (We work with multiple unix architectures hence the linux directory in my own local). My path will search the bin in this area before system paths. I installed the last vim-latex from January 2013 in my local .vim directory. I also have about 10 additional plugins however I have also tried this with a clean .vim. I have a presentation tex file. I open in vim and compile with \ll. I get the error. I can't find file 'presentation.tex'. presentation.tex Emergency stop. If I place this file in my home directory it compiles fine. And of course I can compile fine from the command line regardless of where the file is. Any guidance how to track this down? Mark |
From: Dan S. <da...@st...> - 2014-03-19 17:49:54
|
It would be nice to allow selection of the text within dollar signs by typing vi$ (similarly, replacing this text with ci$, etc.). This is the only feature I miss from LatexBox. To see how LatexBox does it, search their code for "SelectInlineMath". I was able to steal this functionality by copying this and a few support functions into my after/ftplugin/tex.vim. A less sophisticated way is explained in http://vim.wikia.com/wiki/Text_object_for_formulas_in_Latex And thanks to all of the developers who make vim-latex a success! - Dan |
From: Ruthard B. <rut...@we...> - 2014-03-11 19:14:56
|
>== Auszüge aus der Nachricht von Xavier Fontaine vom 2014-03-05 18:16: > Dear all, > > I experience a problem when compiling a .tex file whenever there is a white > space in the filename. Using the vim-latex compile shortcut? It might be not very helpful, but: 1) Whitespace in file names is MS Evil! 2) I'm using pdflatex or xetex directly from vim: :!pdflatex % && pdf-viewer %<.pdf Where "pdf-viewer" is your pdf viewer of choice. If there is MS Evil (whitespace) in the file name, you have to put the % in '"': :!pdflatex "%" && pdf-viewer "%<.pdf", and it should work. I suspect to get the vim-latex native compile function to work, you have to add some '"' in the source No real answer to your question, hope it helps as a work-around at least. Greetings, Ruthard |
From: Xavier F. <xav...@gm...> - 2014-03-05 17:16:53
|
Dear all, I experience a problem when compiling a .tex file whenever there is a white space in the filename. I am trying to compile a minimal tex file using vim-latex. Everything works fine, except when there is a white space in the filename. For instance, I have created two tex files : "test.tex", and "test 2.tex". Compiling runs smoothly in the first case. In the second, I get the following : *! I can't find file `test'.<*> test 2.tex(Press Enter to retry, or Control-D to exit)* This happens both when I try to compile in dvi and in pdf. I should mention that compiling outside vim (so in bash) by typing either "latex test\ 2.tex" or "latex 'test 2.tex'" works very well. I would like to know whether you have any idea about what is happening here? A few details that could be useful: Version of Vim : 7.4, run in terminal mode Version of Vim-Latex : latest one (downloaded from Sourceforge and installed today) OS : Xubuntu Tex distribution : texlive (package texlive-full) I would greatly appreciate any help you could give me! Best, Xavier |
From: Andreas G. <and...@tu...> - 2014-02-27 11:40:24
|
Hi everybody, Thanks to the comment from another user I have complemented my functions by the following function calls: call Tex_SetTeXCompilerTarget('Compile',g:Tex_DefaultTargetFormat) call Tex_SetTeXCompilerTarget('View',g:Tex_DefaultTargetFormat) Now everything works as expected. Thanks and best regards. Andreas Am 02/26/2014 11:09 AM, schrieb Andreas Groh: > Hi @ all, > > I am using vim latex suite for a while an I am quite happy with how it > is working. I often have to switch between tex-projects in German (using > pdflatex with biber) and project in English (using latex with bibtex). > Hence, up to now I have to change the settings in my .vimrc before I > start working on another project. These are my settings: > > "vim-latex plugin settings > set grepprg=grep\ -nH\ $* > let g:tex_flavor = 'latex' > let g:Tex_BibtexFlavor = 'biber' " use biber instead of bibtex > "let g:Tex_BibtexFlavor = 'bibtex' " using bibtex > let g:Tex_UseMakefile = 0 > let g:Tex_ShowErrorContext = 0 > let g:Tex_AutoFolding = 0 > > let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*' > let g:Tex_CompileRule_ps = 'dvips -o $*.ps $*.dvi' > let g:Tex_CompileRule_pdf = 'pdflatex --interaction=nonstopmode $*' > > let g:Tex_FormatDependency_ps = 'dvi,ps' > let g:Tex_FormatDependency_pdf = 'pdf' > > let g:Tex_MultipleCompileFormats = 'dvi,ps,pdf' > > let g:Tex_DefaultTargetFormat = 'pdf' > "let g:Tex_DefaultTargetFormat = 'ps' > > So before switching from a German to an English project a toggle the > comments for the Tex_DefaultTargetFormat and the Tex_BibtexFlavor (and > the spell checking options). Since this is quite inconvenient I thought > about defining two function which do the job. I added > > :function German() > : :set spell spelllang=de_20 > : :let g:Tex_DefaultTargetFormat = 'pdf' > : :let g:Tex_BibtexFlavor = 'biber' > :endfunction > autocmd FileType tex :command! German :cal German() > > :function English() > : :set spell spelllang=en_gb > : :let g:Tex_DefaultTargetFormat = 'ps' > : :let g:Tex_BibtexFlavor = 'bibtex' > :endfunction > autocmd FileType tex :command! English :cal English() > > to my .vimrc. When I am calling the function English the spell checking > and the bibliography settings are changed correctly. Even the default > format is changed (checked by calling :TTarget) but it is not working as > expected. After calling \ll a pdf file is still build, instead of a ps > file. Sometimes (until now I could find out under which circumstance) a > dvi is build, but not a ps like it should. > > Any ideas what is wrong with my function definition? What do I have to > do in order to correctly change the default target from a function. Any > hint is appreciated. > > Thanks and best regards. > > Andreas > > > -- ------------------------------------------------------------------------ Andreas Groh phone : +49-351-463.34974 Institut fuer Planetare Geodaesie fax : +49-351-463.37063 Technische Universitaet Dresden email : and...@tu... D-01062 Dresden, Germany web : tpg.geo.tu-dresden.de ------------------------------------------------------------------------ |
From: Andreas G. <and...@tu...> - 2014-02-26 12:10:52
|
Dear Francesco, Thanks for the hint. Following your instructions I set the pdf/biber options in my .vimrc and placed the alternative options in the corresponding *.latexmain file. I first run for the ps/bibtex project ended up with a dvi only. After deleting all latex-related files another run correctly produced the ps. So your solutions seems to work. Thanks a lot. Nevertheless, if somebody has an idea why the call of the appropriate function is not working as expected please let me know. Best regards. Andreas Am 02/26/2014 11:24 AM, schrieb Francesco Montesano: > Hi Andreas, > > This might work: > > Put your default settings (e.g. English) in your .vimrc (or > ftplugin/tex) file. > In the directory where you want you use the other language (e.g. German) > create a > main.tex.latexmain file [1] (I'm assuming that the main latex file is > main.tex). > Then put in main.tex.latexmain: > set spell spelllang=de_20 > let g:Tex_DefaultTargetFormat = 'pdf' > let g:Tex_BibtexFlavor = 'biber' > > This file is loaded after all the .vimrc and .vim/* files. > > I've used successfully this trick to compile with pdflatex specific > projects, while keeping standard latex as default. > > Cheers, > > Fra > > ref: > [1] > http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project.html > > ps: you might think about changing the spelllang only in the current > buffer, in particular if you open different filetypes in the same session > > > > 2014-02-26 11:09 GMT+01:00 Andreas Groh <and...@tu... > <mailto:and...@tu...>>: > > Hi @ all, > > I am using vim latex suite for a while an I am quite happy with how it > is working. I often have to switch between tex-projects in German (using > pdflatex with biber) and project in English (using latex with bibtex). > Hence, up to now I have to change the settings in my .vimrc before I > start working on another project. These are my settings: > > "vim-latex plugin settings > set grepprg=grep\ -nH\ $* > let g:tex_flavor = 'latex' > let g:Tex_BibtexFlavor = 'biber' " use biber instead of bibtex > "let g:Tex_BibtexFlavor = 'bibtex' " using bibtex > let g:Tex_UseMakefile = 0 > let g:Tex_ShowErrorContext = 0 > let g:Tex_AutoFolding = 0 > > let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*' > let g:Tex_CompileRule_ps = 'dvips -o $*.ps $*.dvi' > let g:Tex_CompileRule_pdf = 'pdflatex --interaction=nonstopmode $*' > > let g:Tex_FormatDependency_ps = 'dvi,ps' > let g:Tex_FormatDependency_pdf = 'pdf' > > let g:Tex_MultipleCompileFormats = 'dvi,ps,pdf' > > let g:Tex_DefaultTargetFormat = 'pdf' > "let g:Tex_DefaultTargetFormat = 'ps' > > So before switching from a German to an English project a toggle the > comments for the Tex_DefaultTargetFormat and the Tex_BibtexFlavor (and > the spell checking options). Since this is quite inconvenient I thought > about defining two function which do the job. I added > > :function German() > : :set spell spelllang=de_20 > : :let g:Tex_DefaultTargetFormat = 'pdf' > : :let g:Tex_BibtexFlavor = 'biber' > :endfunction > autocmd FileType tex :command! German :cal German() > > :function English() > : :set spell spelllang=en_gb > : :let g:Tex_DefaultTargetFormat = 'ps' > : :let g:Tex_BibtexFlavor = 'bibtex' > :endfunction > autocmd FileType tex :command! English :cal English() > > to my .vimrc. When I am calling the function English the spell checking > and the bibliography settings are changed correctly. Even the default > format is changed (checked by calling :TTarget) but it is not working as > expected. After calling \ll a pdf file is still build, instead of a ps > file. Sometimes (until now I could find out under which circumstance) a > dvi is build, but not a ps like it should. > > Any ideas what is wrong with my function definition? What do I have to > do in order to correctly change the default target from a function. Any > hint is appreciated. > > Thanks and best regards. > > Andreas > > > > -- > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > <mailto:Vim...@li...> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > -- ------------------------------------------------------------------------ Andreas Groh phone : +49-351-463.34974 Institut fuer Planetare Geodaesie fax : +49-351-463.37063 Technische Universitaet Dresden email : and...@tu... D-01062 Dresden, Germany web : tpg.geo.tu-dresden.de ------------------------------------------------------------------------ |
From: Francesco M. <fra...@gm...> - 2014-02-26 10:24:27
|
Hi Andreas, This might work: Put your default settings (e.g. English) in your .vimrc (or ftplugin/tex) file. In the directory where you want you use the other language (e.g. German) create a main.tex.latexmain file [1] (I'm assuming that the main latex file is main.tex). Then put in main.tex.latexmain: set spell spelllang=de_20 let g:Tex_DefaultTargetFormat = 'pdf' let g:Tex_BibtexFlavor = 'biber' This file is loaded after all the .vimrc and .vim/* files. I've used successfully this trick to compile with pdflatex specific projects, while keeping standard latex as default. Cheers, Fra ref: [1] http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project.html ps: you might think about changing the spelllang only in the current buffer, in particular if you open different filetypes in the same session 2014-02-26 11:09 GMT+01:00 Andreas Groh <and...@tu...>: > Hi @ all, > > I am using vim latex suite for a while an I am quite happy with how it > is working. I often have to switch between tex-projects in German (using > pdflatex with biber) and project in English (using latex with bibtex). > Hence, up to now I have to change the settings in my .vimrc before I > start working on another project. These are my settings: > > "vim-latex plugin settings > set grepprg=grep\ -nH\ $* > let g:tex_flavor = 'latex' > let g:Tex_BibtexFlavor = 'biber' " use biber instead of bibtex > "let g:Tex_BibtexFlavor = 'bibtex' " using bibtex > let g:Tex_UseMakefile = 0 > let g:Tex_ShowErrorContext = 0 > let g:Tex_AutoFolding = 0 > > let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*' > let g:Tex_CompileRule_ps = 'dvips -o $*.ps $*.dvi' > let g:Tex_CompileRule_pdf = 'pdflatex --interaction=nonstopmode $*' > > let g:Tex_FormatDependency_ps = 'dvi,ps' > let g:Tex_FormatDependency_pdf = 'pdf' > > let g:Tex_MultipleCompileFormats = 'dvi,ps,pdf' > > let g:Tex_DefaultTargetFormat = 'pdf' > "let g:Tex_DefaultTargetFormat = 'ps' > > So before switching from a German to an English project a toggle the > comments for the Tex_DefaultTargetFormat and the Tex_BibtexFlavor (and > the spell checking options). Since this is quite inconvenient I thought > about defining two function which do the job. I added > > :function German() > : :set spell spelllang=de_20 > : :let g:Tex_DefaultTargetFormat = 'pdf' > : :let g:Tex_BibtexFlavor = 'biber' > :endfunction > autocmd FileType tex :command! German :cal German() > > :function English() > : :set spell spelllang=en_gb > : :let g:Tex_DefaultTargetFormat = 'ps' > : :let g:Tex_BibtexFlavor = 'bibtex' > :endfunction > autocmd FileType tex :command! English :cal English() > > to my .vimrc. When I am calling the function English the spell checking > and the bibliography settings are changed correctly. Even the default > format is changed (checked by calling :TTarget) but it is not working as > expected. After calling \ll a pdf file is still build, instead of a ps > file. Sometimes (until now I could find out under which circumstance) a > dvi is build, but not a ps like it should. > > Any ideas what is wrong with my function definition? What do I have to > do in order to correctly change the default target from a function. Any > hint is appreciated. > > Thanks and best regards. > > Andreas > > > > -- > > > ------------------------------------------------------------------------------ > Flow-based real-time traffic analytics software. Cisco certified tool. > Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer > Customize your own dashboards, set traffic alerts and generate reports. > Network behavioral analysis & security monitoring. All-in-one tool. > > http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Andreas G. <and...@tu...> - 2014-02-26 10:09:19
|
Hi @ all, I am using vim latex suite for a while an I am quite happy with how it is working. I often have to switch between tex-projects in German (using pdflatex with biber) and project in English (using latex with bibtex). Hence, up to now I have to change the settings in my .vimrc before I start working on another project. These are my settings: "vim-latex plugin settings set grepprg=grep\ -nH\ $* let g:tex_flavor = 'latex' let g:Tex_BibtexFlavor = 'biber' " use biber instead of bibtex "let g:Tex_BibtexFlavor = 'bibtex' " using bibtex let g:Tex_UseMakefile = 0 let g:Tex_ShowErrorContext = 0 let g:Tex_AutoFolding = 0 let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*' let g:Tex_CompileRule_ps = 'dvips -o $*.ps $*.dvi' let g:Tex_CompileRule_pdf = 'pdflatex --interaction=nonstopmode $*' let g:Tex_FormatDependency_ps = 'dvi,ps' let g:Tex_FormatDependency_pdf = 'pdf' let g:Tex_MultipleCompileFormats = 'dvi,ps,pdf' let g:Tex_DefaultTargetFormat = 'pdf' "let g:Tex_DefaultTargetFormat = 'ps' So before switching from a German to an English project a toggle the comments for the Tex_DefaultTargetFormat and the Tex_BibtexFlavor (and the spell checking options). Since this is quite inconvenient I thought about defining two function which do the job. I added :function German() : :set spell spelllang=de_20 : :let g:Tex_DefaultTargetFormat = 'pdf' : :let g:Tex_BibtexFlavor = 'biber' :endfunction autocmd FileType tex :command! German :cal German() :function English() : :set spell spelllang=en_gb : :let g:Tex_DefaultTargetFormat = 'ps' : :let g:Tex_BibtexFlavor = 'bibtex' :endfunction autocmd FileType tex :command! English :cal English() to my .vimrc. When I am calling the function English the spell checking and the bibliography settings are changed correctly. Even the default format is changed (checked by calling :TTarget) but it is not working as expected. After calling \ll a pdf file is still build, instead of a ps file. Sometimes (until now I could find out under which circumstance) a dvi is build, but not a ps like it should. Any ideas what is wrong with my function definition? What do I have to do in order to correctly change the default target from a function. Any hint is appreciated. Thanks and best regards. Andreas -- |
From: Gary K. <gar...@go...> - 2014-02-13 18:32:23
|
Hello! A short while ago I switched back from Emacs and have to write some Latex documents now. So I downloaded the latex-suite via git submodule add git://git.code.sf.net/p/vim-latex/vim-latex .vim/bundle/vim-latex since my vim configuration is a repository. As you might notice, I use pathogen for package management. Some features, I tried so far work fine, like <F5> for environment generation and <F9> for reference choice, but when I tried to use 'SSE' in insert mode, the result is as follows SSE\section{<++>}<++> so it is appending and not replacing the mapping. I read, that it is an IMAP, so I defined one by myself: IMAP('sss', 'ttt', 'tex') which also had the append effect. When writing 'sss', I get 'sssttt' instead of 'ttt'. This undesired behavior seems to be independent of the document, I write in. Usually, I use documents without any header at all, and put the document together via \input, but I also tried a minimal version with some documentclass defined and the document environment, without any package inclusion. I use gvim --version VIM - Vi IMproved 7.3 (2010 Aug 15) ... Any idea of what the problem is? Cheers, Gary |
From: Arne S. <arn...@gm...> - 2014-02-04 14:10:20
|
I use BibLaTeX for my references, which has a \Cite* family of citation commands. The attached patch makes <F9> completion work with these commands too. |
From: Niels K. <ni...@ko...> - 2014-02-04 08:57:04
|
Hi, I found now a solution and maybe it helps other. I had vim-latex installed via a package-manager (first vundle, then NeoBundle). It worked fine for most parts but not his. After installing vim-latex manually, bib-autocompletion works as expected and the Outline-window shows now up. Niels On Sat, Jan 25, 2014, at 21:22, Niels Kobschätzki wrote: Hi, I am on OS 10.9, with vim 7.4.141 or MacVim 7.4.52 and I think the newest Latex Suite (I keep it up to date with NeoBundle). The following error happens in vim and in MacVim When I try to auto-complete a cite-command with F9 two splits open up. One that shows the cite-keys. But it isn't called OUTLINE but :grep -nH _HIGHLYIMPROPABLE__ Below that the Bibfile is shown as bib-code. In the Quickfix-window I can move up and down with j and k and it will move the Bib-file to the corresponding bib-entry and hitting enter will enter the cite-key into the tex-file. But f,n and p are not working. When I do a ":verbose map! f" I get the following output which seems to be correct i f * =59_LookupCharacter("f") Last set from ~/Dropbox/Dotfiles/vim/bundle/LaTeX-Suite-aka-Vim-LaTeX/plugin/imaps.vi m I also thought that I get sort of abbreviated entries shown in the window where I see the bib-code instead of the code itself. Any ideas what could be the problem? Niels Email had 1 attachment: * signature.asc * 1k (application/pgp-signature) |
From: Niels K. <ni...@ko...> - 2014-01-25 20:22:24
|
Hi, I am on OS 10.9, with vim 7.4.141 or MacVim 7.4.52 and I think the newest Latex Suite (I keep it up to date with NeoBundle). The following error happens in vim and in MacVim When I try to auto-complete a cite-command with F9 two splits open up. One that shows the cite-keys. But it isn't called ___OUTLINE___ but :grep -nH ____HIGHLY_IMPROPABLE____ Below that the Bibfile is shown as bib-code. In the Quickfix-window I can move up and down with j and k and it will move the Bib-file to the corresponding bib-entry and hitting enter will enter the cite-key into the tex-file. But f,n and p are not working. When I do a ":verbose map! f" I get the following output which seems to be correct i f * <C-R>=<SNR>59_LookupCharacter("f")<CR> Last set from ~/Dropbox/Dotfiles/vim/bundle/LaTeX-Suite-aka-Vim-LaTeX/plugin/imaps.vim I also thought that I get sort of abbreviated entries shown in the window where I see the bib-code instead of the code itself. Any ideas what could be the problem? Niels |
From: Dalon W. <dw...@gm...> - 2014-01-24 20:52:54
|
Sorry to bug, but I'm not entirely sure what's going on here. I'm working on my thesis, and am impressed with Latex-Suite so far. I cannot get the \ref completion to work. When I push F9 in an empty \ref command I get an empty __OUTLINE__ window. So far I've made sure python support is enabled. I have my thesis.tex.latexmain file setup in the home directory. It is a multi-file project, with the main file thesis.tex in the main directory. All other included files are in a tex/ subdirectory These are included with \include{./tex/chapter*} I tried to get a minimal (not) working example with a main file and two included files with the same directory structure, only to find out that the \ref completion actually works for that project! My question is this: any ideas on what could be going wrong, and how can I go about debugging this to find out what is going wrong? Thanks! Dalon -- Dalon Work |
From: Ruthard B. <rut...@we...> - 2014-01-05 14:48:13
|
>== Auszüge aus der Nachricht von Vandra vom 2013-12-25 17:38: > Dear developpers, > > Is it possible to make IMAP definitions not in > /.vim/ftplugin/latex-suite/main.vim > but just in ~/.vimrc? > (actually my .vimrc source a file located in cloud so I have the same vim > config on several computers) > When I try to define a macros in ~/.vimrc: > call IMAP (g:Tex_Leader.'R', "\\replaced[id=il]{<++>}{", 'tex') > it says that IMAP command not found. put a line source /path/to/.vim/plugin/imaps.vim above your IMAP call and it should work Yours, Ruthard |
From: YANG L. <lin...@gm...> - 2013-12-31 06:06:00
|
After nearly one year, I finally got the point. Because I am using pathogen to manage all plugins of vim, and in some previous version of vim-latex, there is no "compiler" folder in the plugin, so everything is compatible with pathogen. but after some updates, the compiler folder emerged, and need to be copied to the installation path of vim. On Windows, vim cannot handle such situation, so no "TCLevel" command and no initialization of "s:target", therefore cannot compile the source file. However, on OSX, it's OK. So just copy the compiler folder to vim and everything is fine. Happy new year! On Wed, Jan 30, 2013 at 12:31 AM, Ted Pavlic <tp...@as...> wrote: > Can you be more specific about the update? > > Are you pulling from the code repository directly? If so, do you know the > changeset (or at least range of possible changesets) that caused the > problem? > > --Ted > > -- > Sent from the mobile device of Ted Pavlic. > Please excuse typos, swypos, or very brief responses. > On Jan 29, 2013 2:54 AM, "YANG LINCHANG" <lin...@gm...> wrote: > >> Hi there, >> first, thank you for developing such a good plugin for tex users. It >> worked fine on both of my Windows desktop and Macbook Pro. >> However, I encountered the problem after one update of vim-latex that it >> cannot work on Windows. >> When I press /ll to compile, vim will throw out a series of error >> messages: >> >> Error detected while processing function Tex_RunLaTeX: >> line 7: >> E121: Undefined variable: s:target >> E15: Invalid expression: s:target >> line 10: >> E121: Undefined variable: s:target >> E116: Invalid arguments for function Tex_Debug >> line 12: >> E121: Undefined variable: s:target >> E116: Invalid arguments for function >> Tex_GetVarValue('Tex_FormatDependency_'.s:t >> arget) != '' >> E15: Invalid expression: >> Tex_GetVarValue('Tex_FormatDependency_'.s:target) != '' >> >> line 21: >> E121: Undefined variable: dependency >> E116: Invalid arguments for function Tex_Debug >> line 25: >> E121: Undefined variable: dependency >> E116: Invalid arguments for function Tex_Strntok(dependency, ',', i) != >> '' >> E15: Invalid expression: Tex_Strntok(dependency, ',', i) != '' >> line 51: >> E121: Undefined variable: initTarget >> E15: Invalid expression: initTarget >> >> And also the similar error messages of \lv and \ls. >> >> but I can still compile .tex files on Mac. It seems that the malfunction >> is related to the target format and I set the right >> "g:Tex_DefaultTargetFormat" in my .vimrc and it used to work. >> please advise me some possible solutions. >> regards >> >> >> >> ------------------------------------------------------------------------------ >> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, >> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current >> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft >> MVPs and experts. ON SALE this month only -- learn more at: >> http://p.sf.net/sfu/learnnow-d2d >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim...@li... >> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >> >> |
From: Peng S. <sha...@gm...> - 2013-12-25 16:51:06
|
I put them in the after directory: .vim/after/ftplugin/tex.vim to avoid modifying main.vim. Hopefully it helps if .vimrc is not the right place IMAP should go. On Wed, Dec 25, 2013 at 11:38 AM, Vandra <va...@ra...> wrote: > Dear developpers, > > Is it possible to make IMAP definitions not in > /.vim/ftplugin/latex-suite/main.vim > but just in ~/.vimrc? > (actually my .vimrc source a file located in cloud so I have the same vim > config on several computers) > When I try to define a macros in ~/.vimrc: > call IMAP (g:Tex_Leader.'R', "\\replaced[id=il]{<++>}{", 'tex') > it says that IMAP command not found. > Preceeding it by > au FileType tex so ~/.vim/ftplugin/tex_latexSuite.vim > does not help. > > Thank you > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics > Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Vandra <va...@ra...> - 2013-12-25 16:39:01
|
Dear developpers, Is it possible to make IMAP definitions not in /.vim/ftplugin/latex-suite/main.vim but just in ~/.vimrc? (actually my .vimrc source a file located in cloud so I have the same vim config on several computers) When I try to define a macros in ~/.vimrc: call IMAP (g:Tex_Leader.'R', "\\replaced[id=il]{<++>}{", 'tex') it says that IMAP command not found. Preceeding it by au FileType tex so ~/.vim/ftplugin/tex_latexSuite.vim does not help. Thank you |
From: <mo...@po...> - 2013-12-01 13:34:39
|
If an error or warning occurse while a tex-build the vim-latexsuite show me the error message (open the error-log) and show me the error occuring position in the source (open the source file). Problem is that if the error occurse not in my tex-file but in a sub-file (toc, bib, toc1, ...) vim-latexsuite close my tex-file and open the sub-file. Then I have to close everything and restart vim-latexssuite to come back to my own tex-file. Is there a way to fix that behaviour? |
From: Mauro S. <mau...@gm...> - 2013-11-30 20:36:27
|
For from a rather long time the default backend for biblatex is biber and no more bibtex, why configuration files of latex-suite are not yet up-to-date, but continue to set bibtex as default? do u think do change this default? thanx ms -- Linux user no.: 353546 public key at http://keyserver.linux.it |
From: Ruthard B. <rut...@we...> - 2013-11-29 21:47:57
|
>== Auszüge aus der Nachricht von John Reid vom 2013-11-05 10:18: > Hi, > > If I don't do ':set paste on' before using ':TTemplate', the indentation > of the template is all messed up. Is it possible to get vim-latex to > turn this on when using templates? To convince vim-latex to do that you have to hack the source -- and every update would make your efforts worthless ;-( BUT... it is possible to define functions and commands in your .vimrc, or better in a .vim/after/ftplugin/tex.vim file that would be loaded as filetype plugin after vim-latex has been loaded. You have to create the "after/ftplugin" directories and the "tex.vim" file if they do not exist yet. In vim a function is defined like this (confere to :help function): ------------------->%----------------------- function SetPasteTTemplate() set paste TTemplate set nopaste endfunction ------------------->%----------------------- and is called: :call SetPasteTTemplate() Typing all this is a bit tedious over the time and not a lot better than typing :set paste, :TTTemplate, :set nopaste, so let's define a handy command (cf. :help command) in our .vimrc or .vim/after/ftplugin/tex.vim! ------------------->%----------------------- command TT call SetPasteTTemplate() ------------------->%----------------------- et voilà -- type :TT in command mode and you've got it. Thank you for asking -- I wanted to figure this out for years, and just didn't have the idea of using .vimrc instead of the vim-latex source. This way it's easy, works, and won't be messed up by the next vim-latex update :-) Greetings, Ruthard |
From: Francesco M. <fra...@gm...> - 2013-11-25 11:01:48
|
Hi, I'm using vim-latex under opensuse 13.1, vim 7.4.52, vim-latex github master (I use pathogen and git submodules for organising the plugins) I am customizing the figure environments. I managed to modify the default figure environment adding let g:Tex_Env_figure = "..." into my .vimrc/ftplugin/tex.vim. Then I want to add a Tex_Env_figure* (for page wide figures). According to the documentation<http://vim-latex.sourceforge.net/documentation/latex-suite/customizing-macros.html#Tex_Env_name> I should be able to > let g:Tex_Env_{'figure*'} = "..." but I get an error "E461: Illegal variable name: Tex_Env_figure*". Is this a bug? So for now, I use "let g:Tex_Env_figures" and if I type "figures" and then hit <F5> it works as desired. Cheers, Fra |
From: Mauro S. <mau...@gm...> - 2013-11-21 19:15:05
|
Although I read some posts on the net about vim and biber, still I'm not able to compile correctly. Following some suggestion, I put in my texcr (at line 96) ======================================================= TexLet g:Tex_MultipleCompileFormats = 'pdf,bbl' ======================================================= and at line 126 ======================================================= TexLet g:Tex_BibtexFlavor = 'biber' ======================================================= Moreover, I changed my compiler.vim this way at lines 567-8: ======================================================= if runCount == 0 && Tex_IsPresentInFile('\\bibdata', mainFileName_root.'.bcf') let bibFileName = mainFileName_root.'.bbl' ======================================================= However, during the compilation I receive the message: ======================================================= LaTeX Warning: Empty Bibliography on line 27 ======================================================= (the line of the source file tex where I put \printbibliography). I find only bcf file, not bbl nor blg So I really I don'k know what else I can do to solve thanx m -- Linux user no.: 353546 public key at http://keyserver.linux.it |
From: Mario D <eg...@gm...> - 2013-11-21 18:33:35
|
Hi all, I just installed vim-latex on an Ubuntu system with vim 7.3.429. I extracted the source vim-latex-1.8.23-20130116.788-git2ef9956.tar.gz and then I ran Make install and it installed in /usr/local/share/vim. To use it, I added set runtimepath^=/usr/local/share/vim to my .vimrc and everything is fine: it works perfectly (BTW, thanks a lot for this wonderful script!). The problem is when I try to customize it: following the instructions in texrc, I created the file ~/.vim/ftplugin/tex.vim Inside it, I put: let g:Tex_CompileRule_dvi = 'vimlatex latex -interaction=nonstopmode -src-special $*' let g:Tex_ViewRuleComplete_dvi = 'xdvi 2>/dev/null' let g:Tex_ViewRule_dvi = 'xdvi 2>/dev/null' let g:Tex_Folding = '0' let g:Tex_AutoFolding = '0' let g:Tex_Leader = ',' let g:Tex_UseUtfMenus = '1' call IMAP('sss', '^{<++>}<++>', 'tex') When I open a tex file, this is correctly source since, for example, the sss map works correctly. I can also see that the variables get the correct value; yet, some of them do not have the expected result. Namely: - The file is opened folded, despite Folding and AoutFolding are 0. - Leader is still ` (and, again, :let Tex_Leader returns , correctly) - In the menu Tex-Math I don't see the graphic of the symbols - Also, I had to set _both_ Tex_ViewRule_dvi and Tex_ViewRuleComplete_dvi: setting only one of them I missed one of the ,ls or ,lv shortcuts Please note that if I make all the changes in /usr/local/share/vim/ftplugin/latex-suite/texrc then everything works as expected but, as indicated in the starting comment of texrc, I would prefer not to do so, so that I do not have to bother in case of upgrade. Can someone please help me? Am I missing something? Thanks a lot Mario |