vim-latex-devel Mailing List for Vim-Latex (Page 58)
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: Qiuye W. <qi...@gm...> - 2007-11-05 14:02:05
|
Hi, thanks for the response,now everything is clear. On Mon, Nov 05, 2007 at 02:39:45PM +0200, Vaidotas Zemlys wrote: >Hi, > >Qiuye Wang a =E9crit : >> hello list, >>=20 >> during using the vim-latexsuite, i've found two things are weird: >>=20 >> 1st, when i input ETB, i'll get the code as follow: >> \begin{thebibliography} >> \item[<+biblabel+>]{<+bibkey+>} <++> >> <++> >> \end{thebibliography}<++> >>=20 >> i'm wondering why would \item but not \bibitem be automatic inserted >> in the environment ``thebibliography''. i am not very familiar with >> the grammar of latex, but does the env thebibliography with \item make >> any sense? >> i have replaced the line TexLet g:Tex_ItemStyle_thebibliography =3D >> '\item[<+biblabel+>]{<+bibkey+>} <++>' in >> $VIM/ftplugin/latex-suite/envmacros.vim with bibitem, so if i press >> Alt-I, i will get /bibitem. But i dont know how could i changed the >> thebibliography env, and make it with the \bibitem as default. >Find the Tex_thebibliography function in file=20 >ftplugin/latex-suite/envmacros.vim and change the item to bibitem. > >>=20 >> 2nd, the Alt-key bindings dont work in console but in gvim. =20 >> i dont understand why do the bindings work in gvim but not in console >> vim. If i press Alt-I in vim in console, then i get the cursor move >> to the head of the line. >>=20 >Alt-key bindings are screwed in VIM. Try reading the manual of setting=20 >map-alt-keys (just type :help map-alt-keys). I think it is possible to=20 >solve the console problem. Still you should now, that VIM sets 8bit=20 >when Alt is pressed, so for example on my system ALT-i provides =E9 (e=20 >with accute accent), and pressing =E9 invokes ALT-i mapping. So if you=20 >use accented letters there is a big chance, that you will have problems. > >Vaidotas Zemlys > >------------------------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. >Still grepping through log files to find problems? Stop. >Now Search log events and configuration files using AJAX and a browser. >Download your FREE copy of Splunk now >> http://get.splunk.com/ >_______________________________________________ >Vim-latex-devel mailing list >Vim...@li... >https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > QY |
From: Vaidotas Z. <ze...@gm...> - 2007-11-05 12:39:49
|
Hi, Qiuye Wang a écrit : > hello list, > > during using the vim-latexsuite, i've found two things are weird: > > 1st, when i input ETB, i'll get the code as follow: > \begin{thebibliography} > \item[<+biblabel+>]{<+bibkey+>} <++> > <++> > \end{thebibliography}<++> > > i'm wondering why would \item but not \bibitem be automatic inserted > in the environment ``thebibliography''. i am not very familiar with > the grammar of latex, but does the env thebibliography with \item make > any sense? > i have replaced the line TexLet g:Tex_ItemStyle_thebibliography = > '\item[<+biblabel+>]{<+bibkey+>} <++>' in > $VIM/ftplugin/latex-suite/envmacros.vim with bibitem, so if i press > Alt-I, i will get /bibitem. But i dont know how could i changed the > thebibliography env, and make it with the \bibitem as default. Find the Tex_thebibliography function in file ftplugin/latex-suite/envmacros.vim and change the item to bibitem. > > 2nd, the Alt-key bindings dont work in console but in gvim. > i dont understand why do the bindings work in gvim but not in console > vim. If i press Alt-I in vim in console, then i get the cursor move > to the head of the line. > Alt-key bindings are screwed in VIM. Try reading the manual of setting map-alt-keys (just type :help map-alt-keys). I think it is possible to solve the console problem. Still you should now, that VIM sets 8bit when Alt is pressed, so for example on my system ALT-i provides é (e with accute accent), and pressing é invokes ALT-i mapping. So if you use accented letters there is a big chance, that you will have problems. Vaidotas Zemlys |
From: ahmet n. <ahm...@ya...> - 2007-11-05 12:00:34
|
Hi, I have been getting this recent error with a vim7.1. It is not happening with vim6.4. The problem is that \cite{} command doesn't search through \begin{thebibliography} environment.(It is strange that when I type "\cite" , its color becomes blue.) My tex file(try.tex) is something like: -------------------------------------> \documentclass{article} \usepackage{color} \usepackage{listings} \begin{document} try try try \cite{}<++> \begin{thebibliography}{99} \bibitem{goossens93} Michel Goossens, The Latex Book \end{thebibliography} \end{document} ---------------------------------------------< when the cursor positions itself into the \cite{}, pressing F9 brings no action. This problem doesn't arise if I prepare a bib file(trybib.bib) and put my bibliography index into it. For example, my_Directory/ try.tex trybib.bib -------------------------------------------------> \documentclass{article} \usepackage{color} \usepackage{listings} \begin{document} try try try \cite{}<++> \bibliographystyle{plain} \bibliography{trybib} \end{document} I am using vim-latexsuite(debian/unstable). Any suggestions? Regards, Ahmet __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: smallnow <sma...@gm...> - 2007-11-04 00:40:43
|
I spent a while searching for how to do this without luck, and then found the documentation right after I sent my last message. Sorry. - Ian Kelling |
From: smallnow <sma...@gm...> - 2007-11-04 00:35:46
|
I'm trying to figure out how to open my compiled output file and have it show whatever location my vim cursor was at. If anyone knows the whole story on this that would be nice, but I would at least like to know what possible variables are there to pass in the vim-latex view command that could be interpreted by a viewing program. Or if there is some other way to accomplish this, please lead me in the right direction. Thank you. - Ian Kelling |
From: Qiuye W. <qi...@gm...> - 2007-10-24 17:44:08
|
hello list, during using the vim-latexsuite, i've found two things are weird: 1st, when i input ETB, i'll get the code as follow: \begin{thebibliography} \item[<+biblabel+>]{<+bibkey+>} <++> <++> \end{thebibliography}<++> i'm wondering why would \item but not \bibitem be automatic inserted in the environment ``thebibliography''. i am not very familiar with the grammar of latex, but does the env thebibliography with \item make any sense? i have replaced the line TexLet g:Tex_ItemStyle_thebibliography = '\item[<+biblabel+>]{<+bibkey+>} <++>' in $VIM/ftplugin/latex-suite/envmacros.vim with bibitem, so if i press Alt-I, i will get /bibitem. But i dont know how could i changed the thebibliography env, and make it with the \bibitem as default. 2nd, the Alt-key bindings dont work in console but in gvim. i dont understand why do the bindings work in gvim but not in console vim. If i press Alt-I in vim in console, then i get the cursor move to the head of the line. any tip would be appreciated qiuye |
From: corentin b. <cor...@gm...> - 2007-10-10 13:25:12
|
Hello, I'm using latex-suite for a while and I thank you a lot for this great piec= e of software. I usually use multi-files document and I would like latex-suite to open all .tex document even if doesn't contain \documentclass or \begin{end}. I search in the code to understand why It doesn't open my .tex files but I didn't found where to make this adjustment. Faithfully, Corentin --=20 ___________________ Corentin Barbu http://corentin.barbu.free.fr/ 91 avenue Gabriel P=E9ri 95200 Sarcelles France +33679284434 |
From: Javier R. <jer...@gm...> - 2007-09-26 02:54:56
|
On Tue, Sep 25, 2007 at 01:13:24PM -0600, Ning Tang wrote: > The problem is that when typing "," and "." in the tex files. The > insertion point will be moved in front of those symbols, which is a bit > annoying. For example if I type "123,456" in a tex file, it would become > "123456," it is not happening on my setup (vim 7.1.2, latest vimlatex). It must be something else in your config. Try installing vimlatex from source to a new OS user and checking it again. It might be as well some system-wide config. file for vim; that will depend on your distro. HTH --=20 Javier Rojas GPG Key ID: 0xA1C57061 |
From: Ning T. <ta...@uc...> - 2007-09-25 19:13:27
|
Hi there, I am pretty new to this latex package and I apologize if this problem has been addressed before. However, I wasn't able to find the solution anywhere.. The problem is that when typing "," and "." in the tex files. The insertion point will be moved in front of those symbols, which is a bit annoying. For example if I type "123,456" in a tex file, it would become "123456," Justing wondering if anyone knows how to turn this feature off and that will really be great! Any respond would be appreciated! Thanks! Ning |
From: Erwin G. <erw...@un...> - 2007-09-19 07:55:32
|
Sorry This message got to the wrong address Just ignore it |
From: Erwin G. <erw...@un...> - 2007-09-19 07:44:27
|
Hi Thanks, that was the solution. I think you should definitely put this info also on your kbib site. But now I face the problem that it does not take the doi as valid Example-DOI (from Science magazine) " CrossRef did not return valid XML. This could be due to invalid DOI or the DOI is not known to crossref.org. The DOI was 10.1126/science.317.5844.1495b. " How could that happen? Thanks for your response and your great efforts for simple reference gathering. Greetings from Vienna Gaubitzer Erwin |
From: SourceForge.net <no...@so...> - 2007-09-12 20:21:35
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4515334 By: bhav2007 I believe the install involved unpacking an archive into the /usr/share/vim/vim62 directory. I don't think that I will be able to manually undo the changes to all of the involved files. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=173627 |
From: SourceForge.net <no...@so...> - 2007-09-12 08:24:34
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4513992 By: bastl oops, sorry, I thought of another project ... ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=173627 |
From: SourceForge.net <no...@so...> - 2007-09-12 08:22:47
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4513987 By: bastl Simply delete the vimplugin folder/zipfile from the plugins-folder of your eclipse-installation. Then restart eclipse. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=173627 |
From: SourceForge.net <no...@so...> - 2007-09-12 08:06:05
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4513964 By: bcelary Well how did you installed it in the first place? Have a look in the directories where Vim stores its enhancements... ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=173627 |
From: SourceForge.net <no...@so...> - 2007-09-12 03:52:28
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4513716 By: bhav2007 How can I uninstall vim-latex? I've been searching the project website for hours with no success. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=173627 |
From: ahmet n. <ahm...@ya...> - 2007-09-01 20:34:17
|
Hi, In the latest version of vim-latex(latexSuite20060325.zip from http://vim-latex.sourceforge.net/), some patches has not been applied yet, such as "F5" completion problem. Some of these problems have been fixed in debian version of vim-latex. I wonder somebody could apply these patches proposed by Franz Pletz into 20060325. thanks, Ahmet ____________________________________________________________________________________ Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC |
From: ahmet n. <ahm...@ya...> - 2007-08-31 11:43:21
|
It looks that gvim version 7.1.56 causes problems preventing latexing a multiple file project. I compiled gvim version 6.4 from source today and have no problem using it for a multiple file project. It looks that vim-latex suite doesn't keep up pace with newer version of vims. Regards, Ahmet ____________________________________________________________________________________ Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/ |
From: ahmet n. <ahm...@ya...> - 2007-08-30 18:15:22
|
Hello Again, I have no problem latexing "main.latex" inside the "thesis" directory. I paste the "main.log" file. -----------------------------------------> This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) (format=latex 2007.8.4) 30 AUG 2007 21:04 entering extended mode %&-line parsing enabled. **main.tex (./main.tex LaTeX2e <2005/12/01> Babel <v3.8h> and hyphenation patterns for english, usenglishmax, dumylang, noh yphenation, croatian, bulgarian, russian, ukrainian, czech, slovak, danish, dut ch, finnish, finnish, french, basque, french, german, ngerman, german, ngerman, greek, monogreek, ancientgreek, ibycus, hungarian, hungarian, italian, italian , latin, latin, mongolian, mongolian, norsk, norsk, coptic, esperanto, estonian , icelandic, indonesian, interlingua, romanian, serbian, slovenian, turkish, up persorbian, welsh, polish, polish, portuguese, portuguese, spanish, catalan, ga lician, spanish, catalan, galician, swedish, swedish, ukenglish, ukenglish, loa ded. (/usr/share/texmf-texlive/tex/latex/base/book.cls Document Class: book 2005/09/16 v1.4f Standard LaTeX document class (/usr/share/texmf-texlive/tex/latex/base/bk10.clo File: bk10.clo 2005/09/16 v1.4f Standard LaTeX file (size option) ) \c@part=\count79 \c@chapter=\count80 \c@section=\count81 \c@subsection=\count82 \c@subsubsection=\count83 \c@paragraph=\count84 \c@subparagraph=\count85 \c@figure=\count86 \c@table=\count87 \abovecaptionskip=\skip41 \belowcaptionskip=\skip42 \bibindent=\dimen102 ) (./main.aux) \openout1 = `main.aux'. LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 2. LaTeX Font Info: ... okay on input line 2. LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 2. LaTeX Font Info: ... okay on input line 2. LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 2. LaTeX Font Info: ... okay on input line 2. LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 2. LaTeX Font Info: ... okay on input line 2. LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 2. LaTeX Font Info: ... okay on input line 2. LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 2. LaTeX Font Info: ... okay on input line 2. (./intro/intro.tex Chapter 1. ) [1 ] (./main.aux) ) Here is how much of TeX's memory you used: 233 strings out of 93924 2441 string characters out of 1161648 48030 words of memory out of 1500000 3593 multiletter control sequences out of 10000+50000 4553 words of font info for 17 fonts, out of 1200000 for 2000 759 hyphenation exceptions out of 8191 23i,4n,17p,134b,123s stack positions out of 5000i,500n,6000p,200000b,5000s Output written on main.dvi (1 page, 356 bytes). --------------------------------------------------< My directory structure as the following: \home\ahmet\thesis\ main.tex main.tex.latexmain \home\ahmet\thesis\intro intro.tex The strange thing is that when I move "intro.tex" into the "thesis directory" in which "main.tex" and "main.tex.latexmain" resides, I can compile "intro.tex" by using "ll" command. "intro.tex" has no diffuculty to find "main.tex.latexmain" if they share the same directory. But the problem arises when I move "intro.tex" into "intro" directory(one level below from "thesis" directory. --- Aditya Mahajan <ad...@um...> wrote: > On Thu, 30 Aug 2007, ahmet nurlu wrote: > > > Hi, > > > > "main.tex.mainlatex" was just a typo. The correct > of > > it is "main.tex.latexmain". > > > > I post the texput.log file below: > > > > ---------------------------------------------> > > > > This is pdfTeXk, Version 3.141592-1.40.3 (Web2C > 7.5.6) > > (format=latex 2007.8.4) 30 AUG 2007 17:20 > > entering extended mode > > Source specials enabled. > > %&-line parsing enabled. > > **main.tex > > > > ! Emergency stop. > > <*> main.tex > > > > > > *** (job aborted, file error in nonstop mode) > > > > > > Here is how much of TeX's memory you used: > > 3 strings out of 93924 > > 111 string characters out of 1161648 > > 47725 words of memory out of 1500000 > > 3384 multiletter control sequences out of > 10000+50000 > > 3640 words of font info for 14 fonts, out of > 1200000 > > for 2000 > > 759 hyphenation exceptions out of 8191 > > 0i,0n,0p,1b,6s stack positions out of > > 5000i,500n,6000p,200000b,5000s > > No pages of output. > > > You see, the error message itself contains no line > numbers, so there > is no way for vim-latex to take you to the correct > line number. But > something goes wrong in the file very early, no > documentclass or > packages are loaded. What happens when you compile > main.tex on the > command line. Can you post the contents of main.tex > (either here, or > maybe offlist). > > > > ---------------------------------------------< > > It looks that When I compile "intro.tex" file, > latex > > compiles "main.tex" but somehow the job is > aborted. > > main.tex is compiled because of main.tex.latexmain. > > > > > The output of ":cl" gives: > > E42:No Errors > > This is because emergency stop is not captured by > the errorformat. > Maybe it can be added to it. > > > Aditya > > > > --- Aditya Mahajan <ad...@um...> wrote: > > > >> On Wed, 29 Aug 2007, ahmet nurlu wrote: > >> > >>> I recently have a problem with multiple file > latex > >>> projects. It was not happening before and has > >> appeared > >>> suddenly. My directory layout such as the > >> following: > >>> ------------------------------------ > >>> thesis/ > >>> main.tex > >>> main.tex.mainlatex > >> ^^^^^^^^^^^ > >> > >> This should be main.tex.latexmain > >> > >>> intro/ > >>> intro.tex > >>> --------------------------------- > >>> and my main.tex look like: > >>> > >>> documentclass{book} > >>> \begin{document} > >>> \input{intro/intro.tex} > >>> \end{document} > >>> > >>> When I go to the directory "intro"and I open > >>> intro.tex. > >>> My intro.tex file looks like: > >>> --------------------> > >>> \chapter{try} > >>> this a try > >>> ----------------------< > >>> > >>> When I compile it(\ll), I get some errors as > the > >>> following: > >>> -----------------------------> > >>> Error detected while processing function > >>> Tex_RunLaTeX..Tex_SetupErrorWindow..Tex > >>> _GotoErrorLocation: > >>> line 5: > >>> E42: No Errors > >>> ------------------------------< > >> > >> What is the output of :cl > >> > >> What does the log file (main.log or intro.log) > say? > >> > >> Aditya > >> > >> > > > ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Splunk Inc. > >> Still grepping through log files to find > problems? > >> Stop. > >> Now Search log events and configuration files > using > >> AJAX and a browser. > >> Download your FREE copy of Splunk now >> > >> http://get.splunk.com/ > >> _______________________________________________ > >> Vim-latex-devel mailing list > >> Vim...@li... > >> > > > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > >> > > > > > > > > > ____________________________________________________________________________________ > > Choose the right car based on your needs. Check > out Yahoo! Autos new Car Finder tool. > > http://autos.yahoo.com/carfinder/ > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? > Stop. > > Now Search log events and configuration files > using AJAX and a browser. > > Download your FREE copy of Splunk now >> > http://get.splunk.com/ > > _______________________________________________ > > Vim-latex-devel mailing list > > Vim...@li... > > > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > > > > > > > -- > Aditya Mahajan | EECS Systems, University of > Michigan > http://www.eecs.umich.edu/~adityam | Ph: > 734.262.4008 > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? > Stop. > Now Search log events and configuration files using > AJAX and a browser. > Download your FREE copy of Splunk now >> > http://get.splunk.com/ > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > ____________________________________________________________________________________ Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC |
From: Aditya M. <ad...@um...> - 2007-08-30 15:42:33
|
On Thu, 30 Aug 2007, ahmet nurlu wrote: > Hi, > > "main.tex.mainlatex" was just a typo. The correct of > it is "main.tex.latexmain". > > I post the texput.log file below: > > ---------------------------------------------> > > This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) > (format=latex 2007.8.4) 30 AUG 2007 17:20 > entering extended mode > Source specials enabled. > %&-line parsing enabled. > **main.tex > > ! Emergency stop. > <*> main.tex > > > *** (job aborted, file error in nonstop mode) > > > Here is how much of TeX's memory you used: > 3 strings out of 93924 > 111 string characters out of 1161648 > 47725 words of memory out of 1500000 > 3384 multiletter control sequences out of 10000+50000 > 3640 words of font info for 14 fonts, out of 1200000 > for 2000 > 759 hyphenation exceptions out of 8191 > 0i,0n,0p,1b,6s stack positions out of > 5000i,500n,6000p,200000b,5000s > No pages of output. You see, the error message itself contains no line numbers, so there is no way for vim-latex to take you to the correct line number. But something goes wrong in the file very early, no documentclass or packages are loaded. What happens when you compile main.tex on the command line. Can you post the contents of main.tex (either here, or maybe offlist). > ---------------------------------------------< > It looks that When I compile "intro.tex" file, latex > compiles "main.tex" but somehow the job is aborted. main.tex is compiled because of main.tex.latexmain. > > The output of ":cl" gives: > E42:No Errors This is because emergency stop is not captured by the errorformat. Maybe it can be added to it. Aditya > --- Aditya Mahajan <ad...@um...> wrote: > >> On Wed, 29 Aug 2007, ahmet nurlu wrote: >> >>> I recently have a problem with multiple file latex >>> projects. It was not happening before and has >> appeared >>> suddenly. My directory layout such as the >> following: >>> ------------------------------------ >>> thesis/ >>> main.tex >>> main.tex.mainlatex >> ^^^^^^^^^^^ >> >> This should be main.tex.latexmain >> >>> intro/ >>> intro.tex >>> --------------------------------- >>> and my main.tex look like: >>> >>> documentclass{book} >>> \begin{document} >>> \input{intro/intro.tex} >>> \end{document} >>> >>> When I go to the directory "intro"and I open >>> intro.tex. >>> My intro.tex file looks like: >>> --------------------> >>> \chapter{try} >>> this a try >>> ----------------------< >>> >>> When I compile it(\ll), I get some errors as the >>> following: >>> -----------------------------> >>> Error detected while processing function >>> Tex_RunLaTeX..Tex_SetupErrorWindow..Tex >>> _GotoErrorLocation: >>> line 5: >>> E42: No Errors >>> ------------------------------< >> >> What is the output of :cl >> >> What does the log file (main.log or intro.log) say? >> >> Aditya >> >> > ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? >> Stop. >> Now Search log events and configuration files using >> AJAX and a browser. >> Download your FREE copy of Splunk now >> >> http://get.splunk.com/ >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim...@li... >> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >> > > > > ____________________________________________________________________________________ > Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. > http://autos.yahoo.com/carfinder/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > > -- Aditya Mahajan | EECS Systems, University of Michigan http://www.eecs.umich.edu/~adityam | Ph: 734.262.4008 |
From: ahmet n. <ahm...@ya...> - 2007-08-30 14:44:38
|
Hi, "main.tex.mainlatex" was just a typo. The correct of it is "main.tex.latexmain". I post the texput.log file below: ---------------------------------------------> This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) (format=latex 2007.8.4) 30 AUG 2007 17:20 entering extended mode Source specials enabled. %&-line parsing enabled. **main.tex ! Emergency stop. <*> main.tex *** (job aborted, file error in nonstop mode) Here is how much of TeX's memory you used: 3 strings out of 93924 111 string characters out of 1161648 47725 words of memory out of 1500000 3384 multiletter control sequences out of 10000+50000 3640 words of font info for 14 fonts, out of 1200000 for 2000 759 hyphenation exceptions out of 8191 0i,0n,0p,1b,6s stack positions out of 5000i,500n,6000p,200000b,5000s No pages of output. ---------------------------------------------< It looks that When I compile "intro.tex" file, latex compiles "main.tex" but somehow the job is aborted. The output of ":cl" gives: E42:No Errors Regards, Ahmet --- Aditya Mahajan <ad...@um...> wrote: > On Wed, 29 Aug 2007, ahmet nurlu wrote: > > > I recently have a problem with multiple file latex > > projects. It was not happening before and has > appeared > > suddenly. My directory layout such as the > following: > > ------------------------------------ > > thesis/ > > main.tex > > main.tex.mainlatex > ^^^^^^^^^^^ > > This should be main.tex.latexmain > > > intro/ > > intro.tex > > --------------------------------- > > and my main.tex look like: > > > > documentclass{book} > > \begin{document} > > \input{intro/intro.tex} > > \end{document} > > > > When I go to the directory "intro"and I open > > intro.tex. > > My intro.tex file looks like: > > --------------------> > > \chapter{try} > > this a try > > ----------------------< > > > > When I compile it(\ll), I get some errors as the > > following: > > -----------------------------> > > Error detected while processing function > > Tex_RunLaTeX..Tex_SetupErrorWindow..Tex > > _GotoErrorLocation: > > line 5: > > E42: No Errors > > ------------------------------< > > What is the output of :cl > > What does the log file (main.log or intro.log) say? > > Aditya > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? > Stop. > Now Search log events and configuration files using > AJAX and a browser. > Download your FREE copy of Splunk now >> > http://get.splunk.com/ > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > ____________________________________________________________________________________ Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. http://autos.yahoo.com/carfinder/ |
From: Aditya M. <ad...@um...> - 2007-08-29 15:47:34
|
On Wed, 29 Aug 2007, ahmet nurlu wrote: > I recently have a problem with multiple file latex > projects. It was not happening before and has appeared > suddenly. My directory layout such as the following: > ------------------------------------ > thesis/ > main.tex > main.tex.mainlatex ^^^^^^^^^^^ This should be main.tex.latexmain > intro/ > intro.tex > --------------------------------- > and my main.tex look like: > > documentclass{book} > \begin{document} > \input{intro/intro.tex} > \end{document} > > When I go to the directory "intro"and I open > intro.tex. > My intro.tex file looks like: > --------------------> > \chapter{try} > this a try > ----------------------< > > When I compile it(\ll), I get some errors as the > following: > -----------------------------> > Error detected while processing function > Tex_RunLaTeX..Tex_SetupErrorWindow..Tex > _GotoErrorLocation: > line 5: > E42: No Errors > ------------------------------< What is the output of :cl What does the log file (main.log or intro.log) say? Aditya |
From: ahmet n. <ahm...@ya...> - 2007-08-29 13:36:13
|
I recently have a problem with multiple file latex projects. It was not happening before and has appeared suddenly. My directory layout such as the following: ------------------------------------ thesis/ main.tex main.tex.mainlatex intro/ intro.tex --------------------------------- and my main.tex look like: documentclass{book} \begin{document} \input{intro/intro.tex} \end{document} When I go to the directory "intro"and I open intro.tex. My intro.tex file looks like: --------------------> \chapter{try} this a try ----------------------< When I compile it(\ll), I get some errors as the following: -----------------------------> Error detected while processing function Tex_RunLaTeX..Tex_SetupErrorWindow..Tex _GotoErrorLocation: line 5: E42: No Errors ------------------------------< I am using recent version TexLive and vim7.1.56 in Debian/testing. Any idea? thanks, Ahmet ____________________________________________________________________________________ Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. http://tv.yahoo.com/collections/222 |
From: Martin S. <fo...@un...> - 2007-08-29 12:59:47
|
Hey. I'm glad that somebody read my mail. On Wed, Aug 29, 2007 at 01:06:59AM -0400, Jushan Bai wrote: > I notice that you proposed a solution to the "jump to error" problem. > But I'm a novice about the latexsuite setups and environment variables > etc. I'm using vim78.0 + miktex 2.5 + windows xp. Note that I only tested my suggestion with Ubuntu Linux and tetex, so it might not work with miktex at all. Maybe you should consider reading the miktex documentation if their latex command supports the -file-line-error flag. If you get it to work in windows please let the vim-latex mailinglist know about it so that others can profit, too. > In which latexsuite script I should make the suggested changes? For testing purposes, you can just do a :let g:Tex_CompileRule_dvi='latex -interaction=nonstopmode -file-line-error $*' in vim. If it all works, you can add that statement without the : in your vimrc, or somewhere else, e.g. ~/.vim/after/ftplugin/tex.vim, thats where I have put it. (Your path might be different, I don't know about windows. The vim documentation about paths should be a good place to start reading about it, also :help compiler-rules is not a bad idea) > and where do I add or change or delete the following statement? I > have no idea what they mean at all: The statement that you meant: ----------- 8< ----------------- --- /usr/share/vim/addons/compiler/tex.vim 2007-01-29 13:39:58.000000000 +0100 +++ /home/lennox/.vim/compiler/tex.vim 2007-06-14 23:33:33.000000000 +0200 @@ -202,6 +202,7 @@ function! <SID>SetLatexEfm() setlocal efm+=%E!\ LaTeX\ %trror:\ %m setlocal efm+=%E!\ %m + setlocal efm+=%E%f:%l:\ %m setlocal efm+=%+WLaTeX\ %.%#Warning:\ %.%#line\ %l%.%# setlocal efm+=%+W%.%#\ at\ lines\ %l--%*\\d ------------ >8 ---------------- Is a patch made with the command diff -u /usr/share/vim/addons/compiler/tex.vim ~/.vim/compiler/tex.vim It shows the difference between the official /usr/share/vim/addons/compiler/tex.vim and the one that I changed and put in my home directory (~/.vim/compiler/tex.vim), with some context to improve readability. so lines with blanks in the first column mean unchanged lines (context), lines with "+" have to be added, lines with "-" have to be erased. See [1]. On any *nix you could use the "patch" [2] command to make these changes, but as its just one line you can just add it with your favourite text editor (I'd suggest vim, but as you use windows you may be a masochist and want to use notepad instead ;-)...). It basically just means that you have to add the line that begins with the "+" in the shown context (btw. the 202 is a line number, so :202 will get you there in vim). If you have installed the latex-suite like described here: http://vim-latex.sourceforge.net/index.php?subject=download&title=Download the file that you have to edit should be: vimfiles\compiler\tex.vim > Thanks for your help. You're welcome. I hope you can understand my lengthy description. If you want to know what it all means look for documentation on -file-line-error in miktex, and maybe do a :help efm in vim. Cheers Martin [1] http://en.wikipedia.org/wiki/Diff#Context_format [2] http://en.wikipedia.org/wiki/Patch_%28Unix%29 |
From: Franco S. <sa...@gm...> - 2007-08-26 14:53:27
|
On 8/26/07, Jushan Bai <jus...@ny...> wrote: > Thanks for the quick reply. Quickfix recognizes the errors and is able to detect the location of errors, it sounds odd that it cannot deduce the file name that is being compiled? LaTeX-suite uses the errorformat variable to define how vim processes the latex output. Although the command is set within the latexsuite files, it is based on the example in the help files. :help errorformat-LaTeX Here is what happens. Vim scans the latex output looking for a filename, then keeps scanning for errors within that filename. It switches filenames when a new filename is found or when it finds something that indicates it is no longer processing the current file. For example, when vim encounters a line of the form (filename.tex it adds filename.tex to its stack of directories, and certain conditions trigger vim to remove the last file from a stack of directories. For example, whenever a line with a solitary ) is processed. In the following excerpt from a logfile sent to me by Jushan offlist, ivnote.tex is added to the directory stack on line 1 and it is removed on the last line. But it should not be. (ivnote.tex LaTeX2e <2005/12/01> Babel <v3.8g> and hyph ... rman, ngerman, french, loaded. ("F:\Program Files\MiKTeX 2.5\tex\latex\base\article.cls" Document Class: article 2005/09/16 v1.4f Standard LaTeX document class ("F:\Program Files\MiKTeX 2.5\tex\latex\base\size12.clo" File: size12.clo 2005/09/16 v1.4f Standard LaTeX file (size option) ) >From what I can tell, it's not easy to detect when I file is no longer being processed, so there are errors in constructing the appropriate directory stack. One way to fix this would be to fix latex so that its output is standardized. Maybe a script to post-process the logfile into something that vim's errorformat can deal with. Any suggestions? Franco -- |