vim-latex-devel Mailing List for Vim-Latex (Page 9)
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: Gerd W. <ger...@ma...> - 2013-07-09 14:12:29
|
One should rather define Tex_Env_figure or add the code if !exists("g:Tex_package_detected") let g:Tex_package_detected = 'graphicx' elseif g:Tex_package_detected !~ '\<graphicx\>' let g:Tex_package_detected = g:Tex_package_detected.',graphicx' endif to .vim/after/ftplugin/tex.vim. Read the manual. http://vim-latex.sourceforge.net/documentation/latex-suite.html#customizing-macros On 07/09/2013 02:50 PM, Ruthard Baudach wrote: > > Just redefine EFI in .vim/after/ftplugin/tex.vim or in .vimrc: > > > call IMAP ( 'EFI', "\\begin{figure}[<+htpb+>]\<CR> \\centering\<CR> \\includegraphics[scale=<++>]{<+figure+>}\<CR> \\caption{<+caption text+>}\<CR> \\label{fig:<+label+>}\<CR>\\end{figure}<++>", 'tex') > > > The files in .vim/after are loaded after the normal plugin processing > took place, and are intended to override plugin code locally. > > As .vimrc is loaded as last file, this code could be placed there, too. > > Normally it was a bad idea to override a filetype plugin in .vimrc, > as the definitions here affect all file types, but IMAP has the > third parameter filetype, thus this redefinition in the .vimrc will > affect only .tex files. > > For a deeper understanding of IMAP try :help IMAP. > > Take care to escape all "\" and the first "<" of the vim keycode for > "Enter" (<CR>), and to use " for the second string. > > There is one problem left: if you use this code, the formatting will be > shifted one space each line. I think this might be due to the default > "nopaste" mode of vim, and don't know how vim-latex solves this. > > Either, if they shifted the default mode to "paste", it should work, or > you will have to take a look on vim-latex's code to solve it. > > Greetings, > > Ruthard > > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Ruthard B. <rut...@we...> - 2013-07-09 13:15:31
|
Just redefine EFI in .vim/after/ftplugin/tex.vim or in .vimrc: call IMAP ( 'EFI', "\\begin{figure}[<+htpb+>]\<CR> \\centering\<CR> \\includegraphics[scale=<++>]{<+figure+>}\<CR> \\caption{<+caption text+>}\<CR> \\label{fig:<+label+>}\<CR>\\end{figure}<++>", 'tex') The files in .vim/after are loaded after the normal plugin processing took place, and are intended to override plugin code locally. As .vimrc is loaded as last file, this code could be placed there, too. Normally it was a bad idea to override a filetype plugin in .vimrc, as the definitions here affect all file types, but IMAP has the third parameter filetype, thus this redefinition in the .vimrc will affect only .tex files. For a deeper understanding of IMAP try :help IMAP. Take care to escape all "\" and the first "<" of the vim keycode for "Enter" (<CR>), and to use " for the second string. There is one problem left: if you use this code, the formatting will be shifted one space each line. I think this might be due to the default "nopaste" mode of vim, and don't know how vim-latex solves this. Either, if they shifted the default mode to "paste", it should work, or you will have to take a look on vim-latex's code to solve it. Greetings, Ruthard |
From: Rudra B. <rud...@ao...> - 2013-07-08 10:39:18
|
Hello friends, in vim-latex, EFI expands as \begin{figure}[<+htpb+>] \centering \psfig{figure=<+eps file+>} \caption{<+caption text+>} \label{fig:<+label+>} \end{figure}<++> I want to change this as \begin{figure}[<+htpb+>] \centering \includegraphics[scale=<++>]{<+figure+>} \caption{<+caption text+>} \label{fig:<+label+>} \end{figure}<++> %since I generally do pdflatex, and use \includegraphics, rather then psfig. Any way to achieve it? -- Rudra |
From: Raphael C. <cer...@gm...> - 2013-06-22 13:42:13
|
Thank you all for the insight. I find the suggestions on here helpful :) On Fri, Jun 21, 2013 at 2:49 PM, Alessandro Pezzoni < ale...@la...> wrote: > On 21 June 2013 19:33, Mike Richman <ri...@um...> wrote: > > > " mappings for frame, block, and columns environments > > call IMAP ('EBFE', s:undostring."\\begin{frame}\<cr>{<++>}\<cr>" > > \ . "<++>\<cr>\\end{frame}<++>", 'tex') > > call IMAP ('EBBL', s:undostring."\\begin{block}{<++>}\<cr>" > > \ . "<++>\<cr>\\end{block}<++>", 'tex') > > call IMAP ('EBCO', s:undostring."\\begin{columns}\<cr>" > > \ . "\\column{.5\\textwidth}\<cr>" > > \ . "<++>\<cr>\\end{columns}<++>", 'tex') > > > > " this causes frames to be folded. sometimes the parsing goes poorly > > " and a bunch of extraneous folds are added, but it's still nice to > > " fully fold and unfold the frames using zC and zO. > > let Tex_FoldedEnvironments = 'verbatim,comment,frame,eq,gather,align,' > > > \.'figure,table,thebibliography,keywords,abstract,' > > \.'titlepage' > > Yes, although something like: > > let g:Tex_Env_frame = > \\begin{frame}\<cr>{<++>}\<cr><++>\<cr>\\end{frame}<++>" > call IMAP('EBFE', "\<C-r>=Tex_PutEnvironment('frame')\<cr>", 'tex') > > (and similarly for the others) feels cleaner. Just my 2c. > > Alessandro > > |
From: Alessandro P. <ale...@la...> - 2013-06-21 18:50:08
|
On 21 June 2013 19:33, Mike Richman <ri...@um...> wrote: > " mappings for frame, block, and columns environments > call IMAP ('EBFE', s:undostring."\\begin{frame}\<cr>{<++>}\<cr>" > \ . "<++>\<cr>\\end{frame}<++>", 'tex') > call IMAP ('EBBL', s:undostring."\\begin{block}{<++>}\<cr>" > \ . "<++>\<cr>\\end{block}<++>", 'tex') > call IMAP ('EBCO', s:undostring."\\begin{columns}\<cr>" > \ . "\\column{.5\\textwidth}\<cr>" > \ . "<++>\<cr>\\end{columns}<++>", 'tex') > > " this causes frames to be folded. sometimes the parsing goes poorly > " and a bunch of extraneous folds are added, but it's still nice to > " fully fold and unfold the frames using zC and zO. > let Tex_FoldedEnvironments = 'verbatim,comment,frame,eq,gather,align,' > \.'figure,table,thebibliography,keywords,abstract,' > \.'titlepage' Yes, although something like: let g:Tex_Env_frame = \\begin{frame}\<cr>{<++>}\<cr><++>\<cr>\\end{frame}<++>" call IMAP('EBFE', "\<C-r>=Tex_PutEnvironment('frame')\<cr>", 'tex') (and similarly for the others) feels cleaner. Just my 2c. Alessandro |
From: Mike R. <ri...@um...> - 2013-06-21 17:34:29
|
Hi Raphael, vim-latex doesn't have any extra support for beamer, but I've added the following mappings and customizations in ~/.vim/ftplugin/tex.vim to help with it: " mappings for frame, block, and columns environments call IMAP ('EBFE', s:undostring."\\begin{frame}\<cr>{<++>}\<cr>" \ . "<++>\<cr>\\end{frame}<++>", 'tex') call IMAP ('EBBL', s:undostring."\\begin{block}{<++>}\<cr>" \ . "<++>\<cr>\\end{block}<++>", 'tex') call IMAP ('EBCO', s:undostring."\\begin{columns}\<cr>" \ . "\\column{.5\\textwidth}\<cr>" \ . "<++>\<cr>\\end{columns}<++>", 'tex') " this causes frames to be folded. sometimes the parsing goes poorly " and a bunch of extraneous folds are added, but it's still nice to " fully fold and unfold the frames using zC and zO. let Tex_FoldedEnvironments = 'verbatim,comment,frame,eq,gather,align,' \.'figure,table,thebibliography,keywords,abstract,' \.'titlepage' Hope this is useful! Cheers, Mike On Fri, Jun 21, 2013 at 7:55 AM, Rudra Banerjee <rud...@ao...> wrote: > In support, if you mean, if it has any beamer template or key bindings > for frame, frametitle etc. then it does not. You have to do it in > generic way. > But yes, I use it without problem. > > On Thu, 2013-06-20 at 22:26 -0400, Raphael Cervantes wrote: >> Hi guys, >> >> Does vim-latex have support for beamer? I searched but couldn't find >> any. >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Windows: >> >> Build for Windows Store. >> >> http://p.sf.net/sfu/windows-dev2dev >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim...@li... >> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |
From: Raniere S. <ra0...@im...> - 2013-06-21 11:56:56
|
Hi Rafael, > Does vim-latex have support for beamer? I searched but couldn't find any. What do you mean by support? AFAIK, Vim-latex haven't yet any template for beamer's environments. IMHO, it isn't need because it haven't many options. As Francesco, I used vim-latex with beamer some times without any problem. Raniere |
From: Rudra B. <rud...@ao...> - 2013-06-21 11:55:39
|
In support, if you mean, if it has any beamer template or key bindings for frame, frametitle etc. then it does not. You have to do it in generic way. But yes, I use it without problem. On Thu, 2013-06-20 at 22:26 -0400, Raphael Cervantes wrote: > Hi guys, > > Does vim-latex have support for beamer? I searched but couldn't find > any. > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |
From: Francesco M. <fra...@gm...> - 2013-06-21 05:28:40
|
Hi Rafael, I used vim-latex with beamer a couple of weeks ago without problems. Francesco Il giorno 21/giu/2013 04:26, "Raphael Cervantes" < cer...@gm...> ha scritto: > Hi guys, > Does vim-latex have support for beamer? I searched but couldn't find any. > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > |
From: Raphael C. <cer...@gm...> - 2013-06-21 02:26:15
|
Hi guys, Does vim-latex have support for beamer? I searched but couldn't find any. |
From: Paul G. <li...@ge...> - 2013-06-14 21:25:10
|
Giovanni, Thanks for the tip. I do need biber, but I think I got it to work. What I did was in latex-suite/texrc around line 235 I set: TexLet g:Tex_BibtexFlavor = 'biber' And then in latex-suite/compiler.vim around line 567, I changed the first few lines to: if runCount == 0 && Tex_IsPresentInFile('bibdata', mainFileName_root.'.bcf') let bibFileName = mainFileName_root.'.bbl' let biblinesBefore = Tex_CatFile(bibFileName) This checks for bibliography info in the bcf file. I set it to run biber just on the root filename, and biber is smart enough to look for the bcf extension, This seemed to work. The main change was telling biber to look in the bcf instead of the aux file for the bib info. The only downside is I think it runs biber every time you have any bibliography info in your tex file, since bibdata is always in the bcf, even if it has not changed. But it does not run if you do not have any bibliography info. The problem is that I cannot get updates to vim-latex without losing these changes. So I would like to see some sort of option for choosing bibtex or biber. As you can see, the code change is small, so it would be easy enough to associate different file extensions with different bibliography backends. Thanks paul On 6/14/13 7:25 AM, "vim...@li..." <vim...@li...> wrote: >Send Vim-latex-devel mailing list submissions to > vim...@li... > >To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >or, via email, send a message with subject or body 'help' to > vim...@li... > >You can reach the person managing the list at > vim...@li... > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Vim-latex-devel digest..." >Today's Topics: > > 1. Biblatex (Paul Gesting) > 2. Re: Biblatex (Giovanni Luca Ciampaglia) > 3. [PATCH] Proper python shebang for outline.py (Christian Ebert) > 4. compile bibtex (Rudra Banerjee) > 5. Re: compile bibtex (Alessandro Pezzoni) > 6. Re: compile bibtex (Rudra Banerjee) > 7. Re: Multiple file latex projects, finds correct filename but > doesn't compile in right directory? (Wei Qiu) >-------------------------------------------------------------------------- >---- >This SF.net email is sponsored by Windows: > >Build for Windows Store. > >http://p.sf.net/sfu/windows-dev2dev_______________________________________ >________ >Vim-latex-devel mailing list >Vim...@li... >https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |
From: Wei Q. <we...@qi...> - 2013-06-14 12:25:12
|
Ted Pavlic <ted <at> tedpavlic.com> writes: > > >> Does eclim do much for you while in LaTeX? Perhaps you could setup an > >> autocmd to not load eclim when you're in a .tex file. Sorry for digging out this old thread. But I'm experiencing the same problem. I didn't have eclim installed. |
From: Rudra B. <rud...@ao...> - 2013-06-14 10:55:15
|
Alessandro, Thanks for your reply. I have done this, with TexLet g:Tex_MultipleCompileFormats = 'pdf,bbl' but it seems to compile bib every time, even when bib is not updated. So, what I am looking for a *conditional* behaviour. -----Original Message----- From: Alessandro Pezzoni <ale...@la...> To: Rudra Banerjee <rud...@ao...> Cc: vim...@li... <vim...@li...> Subject: Re: [Vim-latex-devel] compile bibtex Date: Fri, 14 Jun 2013 10:28:09 +0200 On 13 June 2013 23:38, Rudra Banerjee <rud...@ao...> wrote: > Hello friends, > I am using vim-latex for writing an article. \ll is ok for compiling. > but problem is how can I compile the bibtex from vim-latex? > > I am already using > :nnoremap <Leader>lw :up!<cr>:call Tex_RunLaTeX()<cr> > > to save and compile latex together. So, is it possible to compile latex > and conditionally compile bibtex (when updated) using a nnoremap? Theoretically, this should happen already with \ll (see [1]). If you are compiling to a format other than dvi, though, you should add it to the g:Tex_MultipleCompileFormats variable. Hope this helps, Alessandro [1] http://folk.uio.no/haaksk/config-files/.vim/doc/latex-suite.html#compiling-multiple |
From: Alessandro P. <ale...@la...> - 2013-06-14 08:28:17
|
On 13 June 2013 23:38, Rudra Banerjee <rud...@ao...> wrote: > Hello friends, > I am using vim-latex for writing an article. \ll is ok for compiling. > but problem is how can I compile the bibtex from vim-latex? > > I am already using > :nnoremap <Leader>lw :up!<cr>:call Tex_RunLaTeX()<cr> > > to save and compile latex together. So, is it possible to compile latex > and conditionally compile bibtex (when updated) using a nnoremap? Theoretically, this should happen already with \ll (see [1]). If you are compiling to a format other than dvi, though, you should add it to the g:Tex_MultipleCompileFormats variable. Hope this helps, Alessandro [1] http://folk.uio.no/haaksk/config-files/.vim/doc/latex-suite.html#compiling-multiple |
From: Rudra B. <rud...@ao...> - 2013-06-13 22:01:08
|
Hello friends, I am using vim-latex for writing an article. \ll is ok for compiling. but problem is how can I compile the bibtex from vim-latex? I am already using :nnoremap <Leader>lw :up!<cr>:call Tex_RunLaTeX()<cr> to save and compile latex together. So, is it possible to compile latex and conditionally compile bibtex (when updated) using a nnoremap? |
From: Christian E. <bla...@gm...> - 2013-06-13 15:32:48
|
--- ftplugin/latex-suite/outline.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ftplugin/latex-suite/outline.py b/ftplugin/latex-suite/outline.py index d8dc90f..d139ab0 100755 --- a/ftplugin/latex-suite/outline.py +++ b/ftplugin/latex-suite/outline.py @@ -1,4 +1,4 @@ -#!/usr/bin/python +#!/usr/bin/env python # Part of Latex-Suite # -- 1.8.3-rc3 |
From: Giovanni L. C. <jun...@gm...> - 2013-06-08 17:05:11
|
Hi Paul, this does not address your original question, and in fact I would like to see biber supported by vim-latex, but if you are good with using bibtex8 with biblatex then you can just add this line to your .vimrc: autocmd FileType tex let g:Tex_BibtexFlavor='bibtex8 -H' and biblatex will compile. Of course if you need a specific feature of biber this won't help you much, but I thought it might be useful anyway for the other people who want to switch to biblatex. Cheers Giovanni On 06/07/2013 08:28 PM, Paul Gesting wrote: > I would like to be able to use the biblatex package with vim-latex. > Specifically, biblatex uses biber by default as the bibliography > backend (and not bibtex). Biber runs on the .bcf file and not the > .bib. Both bibtex and the .bib file seem to be hard coded in vim-latex > in latex-suite/texrc and latex-suite/compiler. > > Thanks > > > ------------------------------------------------------------------------------ > How ServiceNow helps IT people transform IT departments: > 1. A cloud service to automate IT design, transition and operations > 2. Dashboards that offer high-level views of enterprise services > 3. A single system of record for all IT processes > http://p.sf.net/sfu/servicenow-d2d-j > > > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel -- Giovanni Luca Ciampaglia ? http://www.inf.usi.ch/phd/ciampaglia/ ? (812) 287-3471 ? glc...@gm... |
From: Paul G. <li...@ge...> - 2013-06-08 00:57:09
|
I would like to be able to use the biblatex package with vim-latex. Specifically, biblatex uses biber by default as the bibliography backend (and not bibtex). Biber runs on the .bcf file and not the .bib. Both bibtex and the .bib file seem to be hard coded in vim-latex in latex-suite/texrc and latex-suite/compiler. Thanks |
From: Timothée P. <tim...@uq...> - 2013-05-15 20:08:57
|
Hi, I'm trying to use the vim-latex plugin to write, well, LaTeX documents. I'm unable to get the citations to autocomplete using F9. I'm using 7.3 with patches 1-415 and 417-712, on Fedora 18 (which I keep really up to date). Python support in vim is activated, and my version of Python is 2.7.3. I've tested with a sample document, and a short bib file *in the same folder*, and this works. It also works in all situations when I autocomplete a \ref command, so this is not a key binding issue. When I work on my papers, though, I don't get any response when I press F9 in a \cite command. I use Zotero to manage my references, and I keep a (somewhat large, ~3000 entries) central .bib file in my texmf tree, and I added the path to this file in my .vimrc like so: > let g:Tex_BIBINPUTS = > "/home/tpoisot/texmf/bibtex/bib/local/library.bib" (a copy of my vimrc is attached to this email). I've also tried to give the full path to my library in the \bibliography command; that did not worked. I've read that sometime there are conflicts with grep not passing filenames, so I've also added a line to that effect in my .vimrc The only issue I think will happen is that the bibtex entries are not in the correct format. Here are the first lines of my .bib file: > @article{rall_universal_2012, > title = {Universal temperature and body-mass scaling of feeding rates}, > volume = {367}, > issn = {0962-8436}, > url = {http://rstb.royalsocietypublishing.org/cgi/doi/10.1098/rstb.2012.0242}, > doi = {10.1098/rstb.2012.0242}, > number = {1605}, > journal = {Philosophical Transactions of the Royal Society B: Biological Sciences}, > author = {Rall, B. C. and Brose, U. and Hartvig, M. and Kalinkat, G. and Schwarzmuller, F. and Vucic-Pestic, O. and Petchey, O. L.}, > month = sep, > year = {2012}, > pages = {2923–2934}, > file = {Rall_et_al_2012_Philosophical_Transactions_of_the_Royal_Society_B_Biological_Sciences_Universal_temperature_and_body-mass.pdf:/home/tpoisot/Documents/Zotero/storage/W4ZATPBQ/Rall_et_al_2012_Philosophical_Transactions_of_the_Royal_Society_B_Biological_Sciences_Universal_temperature_and_body-mass.pdf:application/pdf} > }, > > @article{nakazawa_model_2012, As you'll see there is no space between the key and the entry type, which I've also read can block the completion. FYI, the vim-pandoc plugin (which I think uses citeproc) has no trouble autocompleting from this file. Given that the file is quite large, I thought it might be an issue with reading and parsing, but the vim-pandoc autocompletion is instantaneous. After trying a number of things, I'm really unsure about what to do. Does anybody on the list has an idea about what triggers the problem? -- Timothée Poisot, Ph.D. Post-doctoral scientist Université du Québec à Rimouski Theoretical Ecosystem Ecology Website and reprints http://timotheepoisot.fr/ Québec Centre for Biodiversity Sciences http://qcbs.ca/ Intl. Network for Next-Gen. Ecologists http://innge.net/ |
From: hl <hl....@go...> - 2013-05-02 13:20:01
|
I have a nested document in which I \include chapters from different files, and at the end of each document is a bibliography (using the chapterbib package, however this does not seem to be an issue here). I build the document with <leader>ll. The point is that whenever a bibliography is given in a file which is referenced to via \include in the main document, the .aux file from that chapter is not processed by bibtex, and hence the bibliography does not appear (\input works fine, however, to have separate chapterbibs I need to use \include). It also does not matter whether the included document is in a subfolder or directly in the main folder. If I run pdflatex and bibtex from the command line, everything works fine. How can I patch this, or can you provide a fix to run bibtex for all aux files in all subfolders? |
From: Guido M. <gui...@un...> - 2013-04-26 15:09:07
|
On 18/04/2013 18:29, Alessandro Pezzoni wrote: > Could you please tell us if latex-suite working at all for you? > Moreover, which mappings did you try? May I suggest to try: 1. go to command code (ESC) 2. type : (= hit the key featuring *:* ) 3. type "set keymap=greek_utf-8" (not the opening and closing ") You should be ready -- pls be sure you're using utf8. To return to standard Latin keyboard, hit Cntr-Uppercase and the key in the upper right position of keyboard, second on the right after digits. Documentation is in the greek_utf-8.vim file itself. Take some time to read it particularly should you need Classical Greek (so called polytonic). HTH, gm -- Guido Milanese - Professor of Classics Universita' Cattolica del Sacro Cuore, Milano and Brescia, Italy http://docenti.unicatt.it/ita/guido_fabrizio_milanese/ http://www.arsantiqua.org (not updated) |
From: Alessandro P. <ale...@la...> - 2013-04-18 16:29:08
|
> i can't get the greek letter mapping running. I"ve installed vim-latex > using the ubuntu vim-latexsuite package, as for vim. Is there something > missing from those package or a way to debug this ? Hi, Could you please tell us if latex-suite working at all for you? Moreover, which mappings did you try? AP |
From: Pierre-Alain B. <pab...@la...> - 2013-04-18 15:22:02
|
Hi, i can't get the greek letter mapping running. I"ve installed vim-latex using the ubuntu vim-latexsuite package, as for vim. Is there something missing from those package or a way to debug this ? cheers -- Pierre-Alain BOURDIL pab...@la... <mailto:pab...@la...> pie...@fr... <mailto:pie...@fr...> |
From: Gerd W. <ger...@ma...> - 2013-04-08 06:38:56
|
Hi, try something like call IMAP ('()', '(<++>)<++>', '') in your ~/.texrc, see also .vim/ftplugin/latex-suite/main.vim for the other bracket-mappings. On 04/07/2013 02:27 PM, Ivan Diaz wrote: > Hi there! > > I just came across vim-latex recently, and I love it! Thanks for all the > hard work! > > I especially like the way that brackets and paretheses are handled, so much > so that I would like to use this system when writing any type of file, and > not just tex. > > Could you tell me how to turn this one for all filetypes, or if there is a > stand-alone plugin that handles brackets this way? > > Thanks > > > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > > > > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Ivan D. <dub...@gm...> - 2013-04-07 12:27:56
|
Hi there! I just came across vim-latex recently, and I love it! Thanks for all the hard work! I especially like the way that brackets and paretheses are handled, so much so that I would like to use this system when writing any type of file, and not just tex. Could you tell me how to turn this one for all filetypes, or if there is a stand-alone plugin that handles brackets this way? Thanks |