vim-latex-devel Mailing List for Vim-Latex (Page 63)
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: Bill W. <bil...@ya...> - 2006-09-08 14:04:20
|
Hello! I upgraded to Vim 7 over the summer. This is the first time I am using bibtex in Vim 7. I followed the instructions posted on vim-latex-devel for identifying the problem. It seems that there are errors in the compilation In the debug output I have this: Tex_CompileMultipleTimes: errors = [ 1: (paper.aux)] and later... Tex_RunLaTeX: errlist = [ 1: (paper.aux) 2: ] How do I find out what that error is, or why it's happening? Thanks! --Bill --------------------------------- Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail. |
From: SourceForge.net <no...@so...> - 2006-09-06 12:38:55
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3901509 By: m_ravn Hello, I just discovered that vim-latex works in gvim, but it is still not working in vim - is it supposed to be that way? If that is the case, then please excuse the noise. Regards, Mads ______________________________________________________________________ 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...> - 2006-09-05 14:54:20
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3900154 By: m_ravn Hello, I'm having some trouble getting any of the vim-latex bindings to work. I've downloaded http://vim-latex.sourceforge.net/download/latexSuite20060325.zip and unzipped it in ~/.vim modified my .vimrc to contain only the following filetype plugin on set grepprg=grep\ -nH\ $* filetype indent on But I still can not get any macros to work. For example pressing <F5> in normal-mode does nothing. The output of :scriptnames is 1: /etc/vimrc 2: /usr/share/vim/syntax/syntax.vim 3: /usr/share/vim/syntax/synload.vim 4: /usr/share/vim/syntax/syncolor.vim 5: /usr/share/vim/filetype.vim 6: /usr/share/vim/ftplugin.vim 7: /usr/share/vim/indent.vim 8: /home/mpr/.vimrc 9: /home/mpr/.vim/plugin/SyntaxFolds.vim 10: /home/mpr/.vim/plugin/filebrowser.vim 11: /home/mpr/.vim/plugin/imaps.vim 12: /home/mpr/.vim/plugin/libList.vim 13: /home/mpr/.vim/plugin/remoteOpen.vim 14: /usr/share/vim/plugin/getscript.vim 15: /usr/share/vim/plugin/gzip.vim 16: /usr/share/vim/plugin/matchparen.vim 17: /usr/share/vim/plugin/netrwPlugin.vim 18: /usr/share/vim/plugin/rrhelper.vim 19: /usr/share/vim/plugin/spellfile.vim 20: /usr/share/vim/plugin/tarPlugin.vim 21: /usr/share/vim/plugin/tohtml.vim 22: /usr/share/vim/plugin/vimballPlugin.vim 23: /usr/share/vim/plugin/zipPlugin.vim which I suppose means that the mode has not been loaded. Any help would be much appreciated. Regards, Mads PS. I'm using the following vim version: VIM - Vi IMproved 7.0 (2006 May 7, compiled Aug 26 2006 20:28:14) Included patches: 1-66. ______________________________________________________________________ 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: Tobias W. <to...@gm...> - 2006-09-01 13:08:57
|
Am Donnerstag, den 31.08.2006, 18:30 +0200 schrieb Andre Massing: > Tobias, have you made any progress so far? Until now I haven't had any time to > dig into the very details for that behaviour... :-( Hi Andre, to be honest, I’m not a regex wizard; not to speak of Vim’s errorformat syntax which adds some level of abstraction. I don’t understand why we need continuation lines ( +C ) for example. My initial idea was to use non-greedy matching of parens exec 'setlocal efm+=%-Q%.%\\{-})%r' exec 'setlocal efm+=%-P%.%\\{-}(%f%r' but it doesn’t work well. I just don’t get how these rules are processed. What is done with the rest %r? Is it fed in from the beginning or is it passed on to the next rule in the sequence? Anyway, the pushes and pops of the filename stack are never balanced, no matter what I tried. It seems that once you use more than bare-bones LaTeX and add more packages that have their own output things get messy. Still, if there’s stuff like "(SPQR)" it shouldn’t matter because it will not be on the stack for long. How do, e.g., WinEdt or other editors do it? I hope someone more knowledgeable will weigh in on this. --Tobias |
From: Andre M. <ma...@gm...> - 2006-08-31 16:27:59
|
ahmet nurlu wrote: > Hi Tobias, > > I am pasting the content of the quickfix window below. > > -------------->--------------------------------- > || (./thesis.aux) > || (./chapter1.tex > || (./appendix.tex [7] > |54 error| Missing $ inserted. $ matris(B_ > {ij}=B_{ji})$ ve > || (./thesis.bbl [11]) [12 > || > --------------<--------------------------------- As Tobias described some weeks earlier ("issues with quickfixing..." 07/14/06 07/20/06) , I guess this is a common bug in latexsuite concerning errorformat, since efm sometimes does not extract the corresponding filename from the lengthy error messages issued by latex. BTW, to lately reply to Tobias's email, yes I have the same problem here with almost every latex-file I work on. Either there is *no* file name or a *wrong* name (the latter occurs rather seldom). It is a very annoying bug since it prevents me from effectively using quickfix. I guess it was not intended for *manually* opening the corresponding faulty code line :-) Tobias, have you made any progress so far? Until now I haven't had any time to dig into the very details for that behaviour... :-( Cheers, Andre |
From: coupled c. <cou...@gm...> - 2006-08-20 01:23:41
|
Hi List, I have upgraded my TeX implementation to MikTeX 2.5 and I have problems when I use \lv to view the DVI file. The compilation finishes without any error, but when I press \lv, instead of my own file (which has the name main.dvi), YAP opens a file which has the same name, but it is located deep in the TeX tree. This seems to be a problem only with Vim-LaTeX, because I compiled my file with WinEdt and it opens my DVI without any problem. Has anybody experienced such a problem? I guess it should be easy to try. Just create a tex file with the name main.tex and try to compile it and then view it. Is it your file?? Any comments and suggestion are welcome. Regards, Hooman |
From: Bernhard W. <ber...@gm...> - 2006-08-10 13:55:12
|
Hello, following example: - :set hlsearch - search a pattern -> highlighted - turn off until next search is performed -> :nohl - execute a vim-latex command such as 'EIT' -> highlighting activated again Could this 'automatic highlighting' turned off? Regards, Bernhard -- "Wir sollten den Kosmos nicht mit den Augen des Rationalisierungsfachmanns betrachten. Verschwenderische Fülle gehört seit jeher zum Wesen der Natur." -- Wernher von Braun |
From: Aditya M. <ad...@um...> - 2006-08-08 01:21:52
|
On Tue, 8 Aug 2006, Christian Ebert wrote: > * Aditya Mahajan on Monday, August 07, 2006 at 18:18:19 -0400: >> On Mon, 7 Aug 2006, Christian Ebert wrote: >>> * Manu Hack on Monday, August 07, 2006 at 15:17:33 -0400: >>>> After I updated to Vim 7, I cannot use the <F5> command because if I add the >>>> usepackage line, it appeared like >>>> >>>> <++>]{amsmath}``usepackage[X >>> >>> I can confirm this. Exept I get double quotes " instead of `` -- >>> perhaps because I have Tex_SmartKeyQuote = 0 ... No, that's not >>> the cause I just toggled the setting to test. >> >> I also get this. I can not fully understand why this is happening, but >> here is a quick fix. >> >> Open .vim/ftplugin/latex-suite/env-macros.tex and comment line 700 >> >> " return Tex_pack_one(pack) >> >> and add >> >> let a=Tex_pack_one(pack) >> return a >> >> AFAIK, both these statements should be equivalent, but the second one >> gets rid of the problem. > > Good for you. Here both statements indeed *are* equivalent, as > the second one does not get rid of the problem ;) Yes it does not. I was later testing with some other packages, and they work fine. The problem is still there when I try amsmath. Whenever a package has Tex_package_option_packname set I get the same error as you. Sorry for the noise. Aditya |
From: Christian E. <bla...@gm...> - 2006-08-08 00:02:34
|
* Aditya Mahajan on Monday, August 07, 2006 at 18:18:19 -0400: > On Mon, 7 Aug 2006, Christian Ebert wrote: >> * Manu Hack on Monday, August 07, 2006 at 15:17:33 -0400: >>> After I updated to Vim 7, I cannot use the <F5> command because if I add the >>> usepackage line, it appeared like >>> >>> <++>]{amsmath}``usepackage[X >> >> I can confirm this. Exept I get double quotes " instead of `` -- >> perhaps because I have Tex_SmartKeyQuote = 0 ... No, that's not >> the cause I just toggled the setting to test. > > I also get this. I can not fully understand why this is happening, but > here is a quick fix. > > Open .vim/ftplugin/latex-suite/env-macros.tex and comment line 700 > > " return Tex_pack_one(pack) > > and add > > let a=Tex_pack_one(pack) > return a > > AFAIK, both these statements should be equivalent, but the second one > gets rid of the problem. Good for you. Here both statements indeed *are* equivalent, as the second one does not get rid of the problem ;) c -- _B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html> |
From: Aditya M. <ad...@ii...> - 2006-08-07 22:18:32
|
On Mon, 7 Aug 2006, Christian Ebert wrote: > * Manu Hack on Monday, August 07, 2006 at 15:17:33 -0400: >> After I updated to Vim 7, I cannot use the <F5> command because if I add the >> usepackage line, it appeared like >> >> <++>]{amsmath}``usepackage[X > > I can confirm this. Exept I get double quotes " instead of `` -- > perhaps because I have Tex_SmartKeyQuote = 0 ... No, that's not > the cause I just toggled the setting to test. I also get this. I can not fully understand why this is happening, but here is a quick fix. Open .vim/ftplugin/latex-suite/env-macros.tex and comment line 700 " return Tex_pack_one(pack) and add let a=Tex_pack_one(pack) return a AFAIK, both these statements should be equivalent, but the second one gets rid of the problem. >> If I add an environment, it looked like >> >> \begin{eqnarray*} >> " >> \end{eqnarray*}<++> > > Not here. enviornment inserts work fine here also. Aditya |
From: Christian E. <bla...@gm...> - 2006-08-07 20:03:47
|
* Manu Hack on Monday, August 07, 2006 at 15:17:33 -0400: > After I updated to Vim 7, I cannot use the <F5> command because if I add the > usepackage line, it appeared like > > <++>]{amsmath}``usepackage[X I can confirm this. Exept I get double quotes " instead of `` -- perhaps because I have Tex_SmartKeyQuote = 0 ... No, that's not the cause I just toggled the setting to test. > If I add an environment, it looked like > > \begin{eqnarray*} > " > \end{eqnarray*}<++> Not here. c -- _B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html> |
From: Manu H. <man...@gm...> - 2006-08-07 19:24:09
|
Hi, After I updated to Vim 7, I cannot use the <F5> command because if I add the usepackage line, it appeared like <++>]{amsmath}``usepackage[X If I add an environment, it looked like \begin{eqnarray*} " \end{eqnarray*}<++> There is " there and needed to delete it before starting to type. |
From: coupled c. <cou...@gm...> - 2006-08-03 02:43:08
|
Yes that's the file that you are looking for. In Win XP it is called _vimrc and in Unix it is called .vimrc. Hooman On 7/27/06, Diego Acosta <daa...@ya...> wrote: > > Dear developers, > > I am trying to install and use VIM-Latex on a Win XP laptop per these > instructions: > > http://vim-latex.sourceforge.net/index.php?subject=download&title=Download > > Step 1 of 4 was completed very well and the files were extracted > correctly. The second step is what's causing me grief I can't find a > file named .vimrc anywhere but I do find a file called _vimrc which has: > > set nocompatible > source $VIMRUNTIME/vimrc_example.vim > source $VIMRUNTIME/mswin.vim > behave mswin > > set diffexpr=MyDiff() > function MyDiff() > let opt = '-a --binary ' > if &diffopt =~ 'icase' | let opt = opt . '-i ' | endif > if &diffopt =~ 'iwhite' | let opt = opt . '-b ' | endif > let arg1 = v:fname_in > if arg1 =~ ' ' | let arg1 = '"' . arg1 . '"' | endif > let arg2 = v:fname_new > if arg2 =~ ' ' | let arg2 = '"' . arg2 . '"' | endif > let arg3 = v:fname_out > if arg3 =~ ' ' | let arg3 = '"' . arg3 . '"' | endif > let eq = '' > if $VIMRUNTIME =~ ' ' > if &sh =~ '\<cmd' > let cmd = '""' . $VIMRUNTIME . '\diff"' > let eq = '"' > else > let cmd = substitute($VIMRUNTIME, ' ', '" ', '') . '\diff"' > endif > else > let cmd = $VIMRUNTIME . '\diff' > endif > silent execute '!' . cmd . ' ' . opt . arg1 . ' ' . arg2 . ' > ' . arg3 > . eq > endfunction > > Is that the file that you are referring to or should I write a .vimrc file > with the following? > > filetype plugin on > set shellslash > set grepprg=grep\ -nH\ $* > filetype indent on > > Please help me > > Regards, > > > > Diego Acosta > > ------------------------------ > Yahoo! Music Unlimited - Access over 1 million songs. Try it free.<http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=36035/*http://music.yahoo.com/unlimited/+%0A> > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > > |
From: <gar...@gm...> - 2006-08-02 12:22:05
|
On 8/1/06, Aditya Mahajan <ad...@ii...> wrote: > On Tue, 1 Aug 2006, Gast=F3n Aragu=E1s wrote: > > > Hello > > > > how can i do to put the *.log and *.aux *.toc in the same directory > > where i'm compiling but under tmp/? > > > > what i'm doing now is (my ~/.vim/ftplugin/tex.vim) > > > > let g:Tex_DefaultTargetFormat =3D 'pdf' > > let g:Tex_FormatDependency_pdf =3D 'dvi,pdf' > > let g:Tex_CompileRule_dvi =3D 'latex -interaction=3Dnonstopmode $*' > > let g:Tex_CompileRule_pdf =3D 'dvipdf $*.dvi;mv *.log *.aux *.dvi *.toc > > *.backup tmp' > > Miktex (in Windows) has a command line option -output-directory and > -aux-directory to specify where temp files should go. I do not know > which OS and latex distribution you are using and whether it has these > options. You can check the output of latex --help. > > Aditya > thank you for your reply. Sorry I forgot to say, I'm using latex 3.5.4 in linux Gast=F3n --=20 ------------------------------------------------- Gast=F3n Aragu=E1s Centro de Investigaci=F3n en Inform=E1tica para la Ingenier=EDa (CIII) Univ. Tecnol=F3gica Nacional Facultad Regional C=F3rdoba. Argentina |
From: Aditya M. <ad...@ii...> - 2006-08-01 23:20:48
|
On Tue, 1 Aug 2006, Gast=F3n Aragu=E1s wrote: > Hello > > how can i do to put the *.log and *.aux *.toc in the same directory > where i'm compiling but under tmp/? > > what i'm doing now is (my ~/.vim/ftplugin/tex.vim) > > let g:Tex_DefaultTargetFormat =3D 'pdf' > let g:Tex_FormatDependency_pdf =3D 'dvi,pdf' > let g:Tex_CompileRule_dvi =3D 'latex -interaction=3Dnonstopmode $*' > let g:Tex_CompileRule_pdf =3D 'dvipdf $*.dvi;mv *.log *.aux *.dvi *.toc > *.backup tmp' Miktex (in Windows) has a command line option -output-directory and=20 -aux-directory to specify where temp files should go. I do not know=20 which OS and latex distribution you are using and whether it has these=20 options. You can check the output of latex --help. Aditya |
From: <gar...@gm...> - 2006-08-01 20:22:34
|
Hello how can i do to put the *.log and *.aux *.toc in the same directory where i'm compiling but under tmp/? what i'm doing now is (my ~/.vim/ftplugin/tex.vim) let g:Tex_DefaultTargetFormat =3D 'pdf' let g:Tex_FormatDependency_pdf =3D 'dvi,pdf' let g:Tex_CompileRule_dvi =3D 'latex -interaction=3Dnonstopmode $*' let g:Tex_CompileRule_pdf =3D 'dvipdf $*.dvi;mv *.log *.aux *.dvi *.toc *.backup tmp' but I suppous it could be done in a better way... Thanks in advance Gaston --=20 ------------------------------------------------- Gast=F3n Aragu=E1s Centro de Investigaci=F3n en Inform=E1tica para la Ingenier=EDa (CIII) Univ. Tecnol=F3gica Nacional Facultad Regional C=F3rdoba. Argentina |
From: ahmet n. <ahm...@ya...> - 2006-08-01 18:00:45
|
Hi, I posted email earlier about quickfix window behaving strangely. I found the culprit. The problem was the line inside the ".vim/ftpplugin/tex.vim" which I put in order to refresh xdvi automatically. This tip was given in the list by Sebestian which is: ---------------->--------------------- TexLet g:Tex_CompileRule_dvi = 'latex -src-specials -interaction=nonstopmode $*; kill -SIGUSR1 `pgrep xdvi.bin`' -----------------<---------------------- I removed it and now everything became okey(it is only problematic for a multiple file latex project). But I miss this feature. Is there an another way to do automatic refreshing of xdvi everytime I latex it by \ll ? Regards, Ahmet __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: marc <gm...@au...> - 2006-07-31 13:43:46
|
coupled cores said... > On 7/25/06, marc <gm...@au...> wrote: > > I've googled, but haven't found a solution. > > > > I'm using gvim v7 on Windows XP and LaTeX Suite mostly works - it > > defaults to PDF output and Adobe Reader for vieweing. > > > > When I F9 in a \ref{}, a new vim window opens, named __OUTLINE__ then > > the following error message appears: > > > > 'C:/Program' is not recognized as an internal or external command, > > operable program or batch file. > > > > This would indicate that the space in the file name is causing grief. > > But there is no indication what the script is trying to call. > > > > I have installed GNU grep and this works from a command prompt at all > > locations (i.e. it's in the $PATH). This version supports -H, as > > confirmed by grep --help. > > > > I've also set > > > > set grepprg=grep\ -nH\ $* > > > > as recommended. Is this correct for Windows? > > > > Any suggestions what to do or where to look? > > Hi Marc, > > I had exactly the same problem and it took me a long time to fix it. > Turned out that after I installed Python on my windows XP machine, > everything worked fine. That outline is a python code in LaTeX-Suite. > I wasn't sure about this, but as soon as I installed Python my f9 > started to work nice. > > Give it a try. Another problem could be the path names which have > spaces in them. But first try the Python. You can download it for > free. Ah! Thanks for that - it looks like you saved *me* a lot of time. That's a shame, it looks like the suite is not really ready for Windows' use - unless one is prepared to turn it into a pseudo-'nix box with Cygwin. This simply isn't viable here, though. I'd move to my Linux box, but Vim 7 is not available on Ubuntu, which is what I'm using for the laptops and desktops. (The backport has also been rejected.) I guess that I'll just have to stick with WinEdt on Windows for writing, since I use \label and \ref constantly. Thanks again for the heads up. Much appreciated. -- Best, Marc |
From: ahmet n. <ahm...@ya...> - 2006-07-30 22:47:30
|
Hi Tobias, I am pasting the content of the quickfix window below. -------------->--------------------------------- || (./thesis.aux) || (./chapter1.tex || (./appendix.tex [7] |54 error| Missing $ inserted. $ matris(B_ {ij}=B_{ji})$ ve || (./thesis.bbl [11]) [12 || --------------<--------------------------------- Let say I made a mistake in the "appendix.tex" file. I latex it by a "\ll" command. The cursor lands on the quickfix window(It looks another bug for multiple file LaTeX projects). I press <enter> key on the mistake line in the quickfix window, nothing happens(It should move to the error line in "appendix.tex" file). I go to error line manually. These bugs don't prevent me using vim-latex suite. I like it very much and thank to all the developers and mainteners of vim-latex suite. Regards, Ahmet --- Tobias Wolf <to...@gm...> wrote: > On Sa, 2006-07-29 at 23:35 -0700, ahmet nurlu wrote: > > > For example, I opened the file "/intro/intro.tex" > , > > I latexed it. If there is a mistake in that file, > the > > quickfix window opens itself and shows the > mistake. > > When you press <enter> on any line in quickfix > window, > > ,as you normally expect, the cursor jump to the > > location of the error. But it doesn't behave like > > this. > > The cursor stays in the quickfix window. You need > to > > go the line of the error manually. > > > > I wonder what causes this problem. I am using > Vim7.0. > > Salve Ahmet, > > did you see my earlier mail about the quickfix cycle > on the list? > > I would like to see how the quickfix window looks > like exactly. > Could you please copy the content of the window and > send it to the list? > I surmise that the errorformat, which parses the > LaTeX output, doesn not > work as it should. > > -Tobias > > > > Regards, > > Ahmet > > > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of > IT > > Join SourceForge.net's Techsay panel and you'll > get the chance to share your > > opinions on IT & business topics through brief > surveys -- and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Vim-latex-devel mailing list > > Vim...@li... > > > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Tobias W. <to...@gm...> - 2006-07-30 07:22:58
|
On Sa, 2006-07-29 at 23:35 -0700, ahmet nurlu wrote: > For example, I opened the file "/intro/intro.tex" , > I latexed it. If there is a mistake in that file, the > quickfix window opens itself and shows the mistake. > When you press <enter> on any line in quickfix window, > ,as you normally expect, the cursor jump to the > location of the error. But it doesn't behave like > this. > The cursor stays in the quickfix window. You need to > go the line of the error manually. > > I wonder what causes this problem. I am using Vim7.0. Salve Ahmet, did you see my earlier mail about the quickfix cycle on the list? I would like to see how the quickfix window looks like exactly. Could you please copy the content of the window and send it to the list? I surmise that the errorformat, which parses the LaTeX output, doesn not work as it should. -Tobias > Regards, > Ahmet > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |
From: ahmet n. <ahm...@ya...> - 2006-07-30 06:35:47
|
Hi, I am writing my thesis and have splitted it to multiple files. The directory structure is like as the following: ------------------->------------------------ thesis/ thesis.tex thesis.tex.latex abstract.tex intro/ intro.tex figures/ fig1.eps fig2.eps chapter1/ chap1.tex figures/ fig1.eps conclusion/ conclusion.tex figures/ ---------------->------------------ And thesis.tex looks like this: ------------------------>------------ \documentclass{report} \begin{document} \include{abstract.tex} \include{intro/intro.tex} \include{chapter1/chap1.tex} \include{conclusion/conclusion.tex} \end{document} --------------------<-------------------- For example, I opened the file "/intro/intro.tex" , I latexed it. If there is a mistake in that file, the quickfix window opens itself and shows the mistake. When you press <enter> on any line in quickfix window, ,as you normally expect, the cursor jump to the location of the error. But it doesn't behave like this. The cursor stays in the quickfix window. You need to go the line of the error manually. I wonder what causes this problem. I am using Vim7.0. Regards, Ahmet __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: ahmet n. <ahm...@ya...> - 2006-07-30 06:16:14
|
Hi, I am writing my thesis and have splitted it to multiple files. The directory structure is like as the following: thesis/ main.tex abstract.tex intro/ intro.tex figures/ fig1.eps fig2.eps chapter1/ chap1.tex figures/ fig1.eps conclusion/ conclusion.tex figures/ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: coupled c. <cou...@gm...> - 2006-07-29 16:33:59
|
Hi Marc, I had exactly the same problem and it took me a long time to fix it. Turned out that after I installed Python on my windows XP machine, everything worked fine. That outline is a python code in LaTeX-Suite. I wasn't sure about this, but as soon as I installed Python my f9 started to work nice. Give it a try. Another problem could be the path names which have spaces in them. But first try the Python. You can download it for free. Regards, Hooman On 7/25/06, marc <gm...@au...> wrote: > I've googled, but haven't found a solution. > > I'm using gvim v7 on Windows XP and LaTeX Suite mostly works - it > defaults to PDF output and Adobe Reader for vieweing. > > When I F9 in a \ref{}, a new vim window opens, named __OUTLINE__ then > the following error message appears: > > 'C:/Program' is not recognized as an internal or external command, > operable program or batch file. > > This would indicate that the space in the file name is causing grief. > But there is no indication what the script is trying to call. > > I have installed GNU grep and this works from a command prompt at all > locations (i.e. it's in the $PATH). This version supports -H, as > confirmed by grep --help. > > I've also set > > set grepprg=grep\ -nH\ $* > > as recommended. Is this correct for Windows? > > Any suggestions what to do or where to look? > > -- > Best, > Marc > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: marc <gm...@au...> - 2006-07-28 16:50:51
|
I've googled, but haven't found a solution. I'm using gvim v7 on Windows XP and LaTeX Suite mostly works - it defaults to PDF output and Adobe Reader for vieweing. When I F9 in a \ref{}, a new vim window opens, named __OUTLINE__ then the following error message appears: 'C:/Program' is not recognized as an internal or external command, operable program or batch file. This would indicate that the space in the file name is causing grief. But there is no indication what the script is trying to call. I have installed GNU grep and this works from a command prompt at all locations (i.e. it's in the $PATH). This version supports -H, as confirmed by grep --help. I've also set set grepprg=grep\ -nH\ $* as recommended. Is this correct for Windows? Any suggestions what to do or where to look? -- Best, Marc |
From: marc <gm...@au...> - 2006-07-28 15:57:00
|
When running pdflatex, if the resulting document is already open in Adobe Reader, then the compilation stops. This is a known problem with Adobe Reader which locks .pdf files for writing. Producing a hack to close Adobe Reader is easy enough, but it's no use to me, because I always have multiple documents open. This problem was solved years ago by WinEdt, albeit via DDE, so I'm surprised to see it with the latex suite. Is there a known fix? Thanks. -- Best, Marc |