vim-latex-devel Mailing List for Vim-Latex (Page 41)
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: Hao W. <wen...@gm...> - 2009-11-26 17:24:16
|
Hi there: I am trying to compile *.bib file in latex-suite. The normal procedure in latex is: latex filename -> bibtex filename -> latex filename -> latex filename I know I can use \ll for the "latex filename" operation, but what is it for the "bibtex filename" ? Thanks! |
From: Gary J. <gar...@sp...> - 2009-11-16 17:53:02
|
On 2009-11-15, Hugo Gagnon <lat...@li...> wrote: > Hello, I just got a new fresh vim-latex install but whenever I try to > edit an existing .tex file I get this error message: > "Invalid expression: 'so > '.fnameescape(expand('<sfile>:p:h').'/latex-suite/main.vim')" > What is going on? Perhaps your version of vim doesn't have the fnameescape() function. What version of vim are you using and what does :echo exists("*fnameescape") show? Regards, Gary |
From: Simon Q. <sim...@gm...> - 2009-11-16 11:06:06
|
Thanks William, this does the trick indeed. My guess was that the custom options would be read in at last, for that they are not overwritten by other (standard) option. But now it works, so it'll be fine. Simon On 2009/11/16 9:17,William (B.J.) Snow Orvis <aet...@gm...> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Simon, > > On Sun, Nov 15, 2009 at 12:32:31PM +0100, Simon Quittek wrote: >> Hello mailing list! >> I put the lines >> >> let g:Tex_IgnoredWarnings.="\nhas changed" >> let g:Tex_IgnoreLevel+=1 >> >> in the >> $VIM/ftplugin/tex.vim >> file to suppress some errors connected with certain files I am compiling. >> >> When opening a *.tex file these lines result in error messages in vim: >> "C2.4_Moessbauer.tex" 126L, 3472C >> Error detected while processing ~/.vim/ftplugin/tex.vim: >> line 17: >> E121: Undefined variable: g:Tex_IgnoredWarnings >> line 18: >> E121: Undefined variable: g:Tex_IgnoreLevel >> >> Do you know any way to avoid typing the commands each time when opening a >> *.tex file? >> >> Thanks in advance! >> Simon > > I explicitly set both of those variables in my ~/.vim/ftplugin/tex.vim, > and it works fine: > > let g:Tex_IgnoredWarnings = > \'Underfull'."\n". > \'Overfull'."\n". > \'specifier changed to'."\n". > \'You have requested'."\n". > \'Missing number, treated as zero.'."\n". > \'There were undefined references'."\n". > \'Citation %.%# undefined'."\n". > \'LaTeX Font Warning' > let g:Tex_IgnoreLevel = 8 > > Maybe tex.vim gets read before latex-suite, so those variables are not > yet defined when your .= and += operators get called. > > Hope this helps, > William > > - -- > ...................................................................... > William (B.J.) Snow Orvis PGP Fingerprint: > aet...@gm... E6DC E687 EBB7 E99C 1BCE > http://www.aedifice.org D04F 057B 0CD0 8A49 3E98 > > -----BEGIN PGP SIGNATURE----- > > iEYEARECAAYFAksBCqwACgkQBXsM0IpJPphDZQCgztdSAxP8i2T9GPlh4l3ziUH4 > 2VQAnj1nlNveqv/6gMslEM9+YS9d14V8 > =Aajm > -----END PGP SIGNATURE----- |
From: William (B.J.) S. O. <aet...@gm...> - 2009-11-16 08:17:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Simon, On Sun, Nov 15, 2009 at 12:32:31PM +0100, Simon Quittek wrote: > Hello mailing list! > I put the lines > > let g:Tex_IgnoredWarnings.="\nhas changed" > let g:Tex_IgnoreLevel+=1 > > in the > $VIM/ftplugin/tex.vim > file to suppress some errors connected with certain files I am compiling. > > When opening a *.tex file these lines result in error messages in vim: > "C2.4_Moessbauer.tex" 126L, 3472C > Error detected while processing ~/.vim/ftplugin/tex.vim: > line 17: > E121: Undefined variable: g:Tex_IgnoredWarnings > line 18: > E121: Undefined variable: g:Tex_IgnoreLevel > > Do you know any way to avoid typing the commands each time when opening a > *.tex file? > > Thanks in advance! > Simon I explicitly set both of those variables in my ~/.vim/ftplugin/tex.vim, and it works fine: let g:Tex_IgnoredWarnings = \'Underfull'."\n". \'Overfull'."\n". \'specifier changed to'."\n". \'You have requested'."\n". \'Missing number, treated as zero.'."\n". \'There were undefined references'."\n". \'Citation %.%# undefined'."\n". \'LaTeX Font Warning' let g:Tex_IgnoreLevel = 8 Maybe tex.vim gets read before latex-suite, so those variables are not yet defined when your .= and += operators get called. Hope this helps, William - -- ...................................................................... William (B.J.) Snow Orvis PGP Fingerprint: aet...@gm... E6DC E687 EBB7 E99C 1BCE http://www.aedifice.org D04F 057B 0CD0 8A49 3E98 -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAksBCqwACgkQBXsM0IpJPphDZQCgztdSAxP8i2T9GPlh4l3ziUH4 2VQAnj1nlNveqv/6gMslEM9+YS9d14V8 =Aajm -----END PGP SIGNATURE----- |
From: Hugo G. <lat...@li...> - 2009-11-15 15:28:33
|
Hello, I just got a new fresh vim-latex install but whenever I try to edit an existing .tex file I get this error message: "Invalid expression: 'so '.fnameescape(expand('<sfile>:p:h').'/latex-suite/main.vim')" What is going on? -- Hugo Gagnon -- Hugo Gagnon |
From: Simon Q. <sim...@gm...> - 2009-11-15 11:32:50
|
Hello mailing list! I put the lines let g:Tex_IgnoredWarnings.="\nhas changed" let g:Tex_IgnoreLevel+=1 in the $VIM/ftplugin/tex.vim file to suppress some errors connected with certain files I am compiling. When opening a *.tex file these lines result in error messages in vim: "C2.4_Moessbauer.tex" 126L, 3472C Error detected while processing ~/.vim/ftplugin/tex.vim: line 17: E121: Undefined variable: g:Tex_IgnoredWarnings line 18: E121: Undefined variable: g:Tex_IgnoreLevel Do you know any way to avoid typing the commands each time when opening a *.tex file? Thanks in advance! Simon |
From: peng s. <sha...@gm...> - 2009-11-10 22:40:35
|
On Tue, Nov 10, 2009 at 5:19 PM, peng shao <sha...@gm...> wrote: > Hi guys. I am using VIM 7.2.264 and vim-latex-1.5-20091002. The > following are my .vimrc > > let g:tex_flavor = "latex" > let g:Tex_CompileRule_dvi="latex -src-specials -interaction=nonstopmode $*" > let g:Tex_DefaultTargetFormat='pdf' > let g:Tex_MultipleCompileFormats='pdf' > let g:Tex_CompileRule_pdf = 'pdflatex -interaction=nonstopmode $*' > let g:Tex_GotoError = 1 > > > But I found when I press \ll to do a compile I could not jump to the > error location. Instead my cursor is set to the location of error > list, or in other words I have my vim window like > > > tex file contents > ~~~~~~~~~~~~~~~~~~ > error list (cursor here) > ~~~~~~~~~~~~~~~~~~ > Quickfix list( this part is empty unless I press j or k to move my > cursor in the error list) > Sorry I made a little mistake here, the windows are actually like tex file contents ~~~~~~~~~~~~~ Quickfix(cursor at the first line) But the issue "fail to jump to error if I press enter" remains. Sorry for my previous understanding to the windows label. Peng |
From: peng s. <sha...@gm...> - 2009-11-10 22:19:22
|
Hi guys. I am using VIM 7.2.264 and vim-latex-1.5-20091002. The following are my .vimrc let g:tex_flavor = "latex" let g:Tex_CompileRule_dvi="latex -src-specials -interaction=nonstopmode $*" let g:Tex_DefaultTargetFormat='pdf' let g:Tex_MultipleCompileFormats='pdf' let g:Tex_CompileRule_pdf = 'pdflatex -interaction=nonstopmode $*' let g:Tex_GotoError = 1 But I found when I press \ll to do a compile I could not jump to the error location. Instead my cursor is set to the location of error list, or in other words I have my vim window like tex file contents ~~~~~~~~~~~~~~~~~~ error list (cursor here) ~~~~~~~~~~~~~~~~~~ Quickfix list( this part is empty unless I press j or k to move my cursor in the error list) I read from the documentation that I should press 'enter' at any line to jump to the corresponding error, but I tried and I failed. No matter where I press the enter I could not jump out of the error list to text file contents. :( Anyone could help me on this issue? Thank you :) Peng Shao |
From: Gerd W. <ger...@ma...> - 2009-11-05 09:37:24
|
Hello everybody, I'm using the LaTeX-Suite since one year and it's very usefull! I personalized it a little bit, and now I think I've found a bug ;) Line 716 in envmacros.vim should read let env_line = searchpair('\$\$\|\\\[\|begin{', '', '\$\$\|\\\]\|end{', "bn") instead of let env_line = searchpair('$$\|\\[\|begin{', '', '$$\|\\]\|end{', "bn") So I think, the backslashs and the dollars should be escaped as well. Regards Gerd |
From: Thomas M. <tom...@gm...> - 2009-11-04 14:11:40
|
I tried deleting my .viminfo file and the behavior stopped. Not sure what was going on, but it is fixed now. I would still like an explanation if anyone has one, but if not...no big deal. ~tom On Nov 3, 2009, at 9:34 AM, Thomas Moyer wrote: > Every time I press ctrl-j to jump to the next place holder, VIM > highlights the end of every single line in my document. I'm not sure > why this is happening, but I would like it to stop. I've looked > through the Vim 7 docs and also the vim-latex docs but don't see > anything anywhere that would cause this behavior. Can someone tell > me how to stop it, or at least where to look to figure out why it is > happening to try and stop it? > > ~tom |
From: Erik H. <eri...@gm...> - 2009-11-03 21:00:12
|
Hi, For a project I use a main.tex file (with the main.tex.texmain file) and some \inputted files. With \usepackage{german} in main.tex, the '"' key produces the commands for the German quotation marks ("` and "'). In the included files, however, the regular `` and '' are produced. Is there any way to fix this? Thanks. |
From: Thomas M. <tom...@gm...> - 2009-11-03 14:34:19
|
Every time I press ctrl-j to jump to the next place holder, VIM highlights the end of every single line in my document. I'm not sure why this is happening, but I would like it to stop. I've looked through the Vim 7 docs and also the vim-latex docs but don't see anything anywhere that would cause this behavior. Can someone tell me how to stop it, or at least where to look to figure out why it is happening to try and stop it? ~tom |
From: Vijay K. <vij...@gm...> - 2009-11-01 21:03:27
|
On 1 Nov 2009, at 16:13 , YueJun Yin wrote: > On 11/01/2009 01:29 PM, peng shao wrote: >> On Sun, Nov 1, 2009 at 12:41 PM, YueJun Yin<yj...@gm...> >> wrote: >> >>> Hi >>> I am composing my thesis using vim-latex suite. Every time I use >>> compile >>> function, it only runs 1 time. I have a main file and several other >>> files that are \include in the main file. I typed `ll' on the main >>> file, >>> it only runs 1 time. Could anybody help me on this issue? Thanks. >> >> Hi Yue-Jun: >> >> I never tried this, but maybe you would like to look into >> http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project.html >> if it were any helpful. :) > > peng > Thanks. I read that part but did not find any helpful information. I > have no idea how to write a *.tex.mainlatex file. There is not even an > example. I believe all that is necessary is for the main.tex.latexmain (Note: *not* ".mainlatex") file to exist in the same directory as its main.tex counterpart. The *.latexmain file can be an empty file; its contents are not ever read. It only serves as a flag to latex-suite, letting it know where and what the "master file" is for the project. The idea is, when you open a TeX file, latex-suite wants to know if it is a "stand-alone" file or part of a larger document. It looks in the current directory and in all parent directories until it finds a *.latexmain file. Say you've created a file named "sample.tex.latexmain" in the parent directory, it then concludes that "sample.tex" is the master file for that document and, when you press \ll in an included file, pdflatex (or whatever TeX command you've setup) will be run on "sample.tex" instead. Of course, if no .latexmain file is found, it considers the document to be self-contained, and it will run pdflatex on the document you are editing. On the other hand, I don't know if using this protocol will cause latex-suite to run pdflatex enough times, but it should save you from having to keep the main file open, allowing you to simply type \ll on the \included file you're working in. |
From: YueJun Y. <yj...@gm...> - 2009-11-01 20:15:41
|
peng Thanks. I read that part but did not find any helpful information. I have no idea how to write a *.tex.mainlatex file. There is not even an example. On 11/01/2009 01:29 PM, peng shao wrote: > Hi Yue-Jun: > > I never tried this, but maybe you would like to look into > http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project.html > if it were any helpful. :) > > Peng > > On Sun, Nov 1, 2009 at 12:41 PM, YueJun Yin<yj...@gm...> wrote: > >> Hi >> I am composing my thesis using vim-latex suite. Every time I use compile >> function, it only runs 1 time. I have a main file and several other >> files that are \include in the main file. I typed `ll' on the main file, >> it only runs 1 time. Could anybody help me on this issue? Thanks. >> >> -- >> Yue-Jun Yin (Eugene) >> PhD Candidate >> Civil& Environmental Engineering Dept. >> Michigan Tech University >> 1400 Townsend Dr. >> Houghton, MI 49931 USA >> phone:(908)998-2573 >> email:yu...@mt... >> http://www.cee.mtu.edu/~yuejuny/ >> >> >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9 - 12, 2009. Register now! >> http://p.sf.net/sfu/devconference >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim...@li... >> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >> >> -- Yue-Jun Yin (Eugene) PhD Candidate Civil& Environmental Engineering Dept. Michigan Tech University 1400 Townsend Dr. Houghton, MI 49931 USA phone:(908)998-2573 email:yu...@mt... http://www.cee.mtu.edu/~yuejuny/ |
From: YueJun Y. <yj...@gm...> - 2009-11-01 19:31:09
|
I attached three tex files that I am trying to full around. When I 'll' on the main file, foo.tex. I got warnings as follows: || (./foo.aux (./c1.tex.aux) |15 warning| LaTeX Warning: Reference `fig:StLouisSA' on page 1 undefined on input line 15. || (./c1.tex.aux) (./sc2.aux)) | the figure is defined in c1.tex. Obviously this is because the files were not appropriately compiled. But I have no idea how to deal with this issue. Thanks a lot. On 11/01/2009 11:55 AM, Peter Bjørn Jørgensen wrote: > YueJun Yin wrote: >> Hi >> I am composing my thesis using vim-latex suite. Every time I use >> compile function, it only runs 1 time. I have a main file and several >> other files that are \include in the main file. I typed `ll' on the >> main file, it only runs 1 time. Could anybody help me on this issue? >> Thanks. >> > If you are using pdflatex for compilation you need to put: > let g:Tex_MultipleCompileFormats='pdf' > in your vimrc. -- Yue-Jun Yin (Eugene) PhD Candidate Civil& Environmental Engineering Dept. Michigan Tech University 1400 Townsend Dr. Houghton, MI 49931 USA phone:(908)998-2573 email:yu...@mt... http://www.cee.mtu.edu/~yuejuny/ |
From: YueJun Y. <yj...@gm...> - 2009-11-01 17:17:08
|
Hi I am composing my thesis using vim-latex suite. Every time I use compile function, it only runs 1 time. I have a main file and several other files that are \include in the main file. I typed `ll' on the main file, it only runs 1 time. Could anybody help me on this issue? Thanks. -- Yue-Jun Yin (Eugene) PhD Candidate Civil& Environmental Engineering Dept. Michigan Tech University 1400 Townsend Dr. Houghton, MI 49931 USA phone:(908)998-2573 email:yu...@mt... http://www.cee.mtu.edu/~yuejuny/ |
From: Boris F. <bo...@fe...> - 2009-10-30 15:56:54
|
Hi, I'm using the "contextual menu" key to compose characters like à é è... with my qwerty US keyboard. All the characters seem to work, excepted the "é". When I type "compose" + ' + e, the vim cursor goes 1 char back. When the buffer is empty I get the following message : Erreur détectée en traitant function Tex_InsertItem..Tex_GetCurrentEnv : ligne 7 : E749: tampon vide (Error detected while processing the function.... Line 7 E749: Buffer empty ) I read the documentation but I found nothing about a mapping which includes ' + e . Do you know how I can solve this conflict between compose and vim-latex ? Thanks in advance, Boris -- 42 |
From: Peter B. J. <pet...@gm...> - 2009-10-21 19:02:06
|
Hey. I got two questions about vim latex-suite that I can't find in the docs. Is there supposed to be c-n completion for commands like \leftarrow in mathmode?. If there is, it does not work for me.in Vim 7.2 on archlinux. The second question is.. Where can I set the character used as Tex_Leader for the AUCTex bindings.. The ` sign is hard to reach on a danish keyboard. I've tried "let Tex_Leader = '½' " but it doesn't work. Thank you for a nice plugin ;-) |
From: Mike R. <ri...@um...> - 2009-10-14 00:02:34
|
On Tue, Oct 13, 2009 at 4:04 PM, Eric Potash <eri...@gm...> wrote: > I have no idea why its referencing xy.sty, but the line number is the > correct one for the tex file that i am editing. Unfortuntely vim-latex > jumps to xy.sty and to that line number for debugging. > > I've temporarily used g:Tex_GoToError = 0 to avoid this. Is there some > way to change the compiler command, output, or how vim-latex interprets it > to fix this? This is no fix, but whenever vim-latex (or anything else) takes you to the wrong place, you can go back where you were quickly with <ctrl-o>. This way you can leave GoToError on for the cases when it is useful. Mike On Tue, Oct 13, 2009 at 4:04 PM, Eric Potash <eri...@gm...> wrote: > Great package! Thanks. I have two queries. > > > 1. I'm trying to complete various math commands and it seems like > vim-latex is recognizing some and not all of them. For example if i type > > $\big > > and then hit ctrl+n i see no completion options, even though there should > be several (bigcup, bigoplus, etc.). These are even available in the > tex-math menu (under BigOp). How can I get these and the rest of the ams > symbols to come up under autocompletion? > > 2. Whenever I use the xypic package and have any error (like a missing $ > or }) the latex compiler gives something like: > > /usr/share/texmf-texlive/tex/generic/xypic/xy.sty|142 error| Missing $ > inserted. > > I have no idea why its referencing xy.sty, but the line number is the > correct one for the tex file that i am editing. Unfortuntely vim-latex > jumps to xy.sty and to that line number for debugging. > > I've temporarily used g:Tex_GoToError = 0 to avoid this. Is there some > way to change the compiler command, output, or how vim-latex interprets it > to fix this? > > Thanks, > Eric > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Eric P. <eri...@gm...> - 2009-10-13 20:04:46
|
Great package! Thanks. I have two queries. 1. I'm trying to complete various math commands and it seems like vim-latex is recognizing some and not all of them. For example if i type $\big and then hit ctrl+n i see no completion options, even though there should be several (bigcup, bigoplus, etc.). These are even available in the tex-math menu (under BigOp). How can I get these and the rest of the ams symbols to come up under autocompletion? 2. Whenever I use the xypic package and have any error (like a missing $ or }) the latex compiler gives something like: /usr/share/texmf-texlive/tex/generic/xypic/xy.sty|142 error| Missing $ inserted. I have no idea why its referencing xy.sty, but the line number is the correct one for the tex file that i am editing. Unfortuntely vim-latex jumps to xy.sty and to that line number for debugging. I've temporarily used g:Tex_GoToError = 0 to avoid this. Is there some way to change the compiler command, output, or how vim-latex interprets it to fix this? Thanks, Eric |
From: peng s. <sha...@gm...> - 2009-10-09 14:13:32
|
Hi everybody. I am using vim+latex-suite to do tex editing. Especially I use the following way to do inverse search: in .bashrc vimtex='vim --servername vimtex' and in .vimrc :map \ld :execute 'xdvi -editor "vim --servername 'v:servername' --remote +\%l \%f" -sourceposition ' . line(".") . expand("%") . " " . expand(Tex_GetMainFileName(':r')) . ".dvi &"<CR><CR> let g:Tex_ViewRule_dvi = 'xdvi -editor "vim --servername vimtex --remote +\%l \%f"' and by pressing ctrl and double clicking the mouse in xdvi, the cursor of vim jumps to somewhere I want, it works perfectly and I am happy with it but my little problem is that, after double click the mouse while pressing the ctrl, I would still stay in the window of xdvi, in other words the window of vim did not get the focus so I have to use alt+tab to switch to vim's window, it is a little inconvenient. Is there anyway to let the windows of vim to obtain the focus automatically? I am using gnome... Thanks :) Peng |
From: Ted P. <te...@te...> - 2009-10-04 19:02:16
|
> I am also skeptical about the use of $$ ... $$. This is not a Vim-LaTeX > problem, but a LaTeX one. The use of $$ has been replaced long time ago by > \[ ... \]. Using double dollars is obsolete, and it would be better to > change this habit rather than Vim-LaTeX. And, as described in my last contribution to this thread, even \[...\] is going the way of deprecation. Shortcuts should be implemented within each editor (e.g., with vim-latex "EEQ" and such). There's no need to use short-form displaymode environments (they're deceiving anyway). To add to that, the improvements made by mathtools (and even amsmath) have trouble trickling down through $$...$$ and \[...\] (if I recall from the docs correctly). -- Ted Pavlic <te...@te...> |
From: Ted P. <te...@te...> - 2009-10-04 18:59:25
|
> It seems to me, that this behaviour can only be changed easily for all > environments and not especially for equation*. I am currently not sure, > if this makes sense for every environment. Are there more opinions on > this? There are lots of environments (e.g., ones that live inside math environments, like aligned and bmatrix) that are probably best left alone. >> Since sometimes I just like to use $$ $$ for convenience... I think this usage is deprecated. I believe that some of the improvements made by mathtools (and even amsmath) have difficulty being implemented with the old style displaymode delimiters. Especially because Vim has macros that make the environments as easy to use as the short forms, I don't think much effort should go into making vim-latex support $$...$$. --Ted -- Ted Pavlic <te...@te...> |
From: Daniele A. <d.a...@gm...> - 2009-10-03 08:48:18
|
The two options \begin{equation*} cursor here \end{equation*}<++> and \begin{equation*} cursor here \end{equation*} <++> are only one button away from each other, and I don't see why is hard to stick to option 1, press Ctrl-J to the placeholder, and then Enter to go to new line. I am also skeptical about the use of $$ ... $$. This is not a Vim-LaTeX problem, but a LaTeX one. The use of $$ has been replaced long time ago by \[ ... \]. Using double dollars is obsolete, and it would be better to change this habit rather than Vim-LaTeX. Best. Daniele On Fri, Oct 2, 2009 at 10:02 PM, Till Maas <ope...@ti...> wrote: > On Thu, Sep 24, 2009 at 05:58:21AM -0400, xitong chen wrote: > > > Hello dear maintainers. I was very happy with vim-latex in the past > years. However I have two modifications > > which I would like you can take into consideration. For example if I > press F5 when I was in insert mode I can choose equation*, and the output is > > > > \begin{equation*} > > cursor here > > \end{equation*}<++> > > > > What I wish you could reconsider is the position of <++>. Many latex > users, if my guess is correct, prefer typing latex file like > > > > we have the follow equation > > \begin{equation*} > > > > my equation > > > > \end{equation*} > > then by this equation we know... > > > > So I really wish you could put <++> as > > > > \begin{equation*} > > > > cursor here > > > > \end{equation*} > > <++> > > It seems to me, that this behaviour can only be changed easily for all > environments and not especially for equation*. I am currently not sure, > if this makes sense for every environment. Are there more opinions on > this? > > > Ok the next modification is about > > > > $cursor here$my equation$$ > > > > Since sometimes I just like to use $$ $$ for convenience. And of course > you know vim-latex cannot recognize $$$$ well. It means if I press four $ > continuously I got > > > > $$<++>$<++>$<++> > > > > and instead what I really want is > > > > $$ cursor here $$ > > > > So could you please add an auto-recognition for latex-suite that if I > press two $ then of course as normal it gives out $cursor here$<++> and if I > press an extra $ consequently then it > > recognize I want to have a $$ $$<++> > > I believe this would require a major change, too, because the $$ mapping > will always be evaluated before you can type the third dollar sign. > > Regards > Till > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > |
From: Till M. <ope...@ti...> - 2009-10-02 21:03:14
|
On Thu, Sep 24, 2009 at 05:58:21AM -0400, xitong chen wrote: > Hello dear maintainers. I was very happy with vim-latex in the past years. However I have two modifications > which I would like you can take into consideration. For example if I press F5 when I was in insert mode I can choose equation*, and the output is > > \begin{equation*} > cursor here > \end{equation*}<++> > > What I wish you could reconsider is the position of <++>. Many latex users, if my guess is correct, prefer typing latex file like > > we have the follow equation > \begin{equation*} > > my equation > > \end{equation*} > then by this equation we know... > > So I really wish you could put <++> as > > \begin{equation*} > > cursor here > > \end{equation*} > <++> It seems to me, that this behaviour can only be changed easily for all environments and not especially for equation*. I am currently not sure, if this makes sense for every environment. Are there more opinions on this? > Ok the next modification is about > > $cursor here$my equation$$ > > Since sometimes I just like to use $$ $$ for convenience. And of course you know vim-latex cannot recognize $$$$ well. It means if I press four $ continuously I got > > $$<++>$<++>$<++> > > and instead what I really want is > > $$ cursor here $$ > > So could you please add an auto-recognition for latex-suite that if I press two $ then of course as normal it gives out $cursor here$<++> and if I press an extra $ consequently then it > recognize I want to have a $$ $$<++> I believe this would require a major change, too, because the $$ mapping will always be evaluated before you can type the third dollar sign. Regards Till |