vim-latex-devel Mailing List for Vim-Latex (Page 45)
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: Matías G. <ma...@dm...> - 2009-04-29 12:46:32
|
On Sun, Apr 26, 2009 at 01:55:08AM +0100, Thomas Ibbotson wrote: > Hi, > > Here's another patch to texviewer.vim against the current SVN version. This > now matches bibitems with labels i.e. \bibitem[foo]{bar} when using a > \thebibliography environment. > > I also noticed that \cite completion did not work for a file with a > \thebibliography environment unless I put the following line in my .vimrc: > > let g:Tex_UseCiteCompletionVer2 = 0 > > Is this just unfinished? I have had a look, and haven't thought of an easy > way to fix this, but I'm happy to come up with something if this isn't > already being currently worked on. > > Thanks, > > Tom Hi; yet another patch, working over Thomas' one. The previous patch identified lines with \bibitem[...]{...} for completion, but the completion worked oddly. This one works fine, at least in the cases I tested it with. Also, I added some spaces to the regexps, since something like \bibitem [A] {a} is understood by latex, so it should be understood by vim-latex. I did not add possible newlines in the middle: latex understands \bibitem [A] {a} and the current patch doesn't. Also: I missed the completion for cites for quite a long time, until Thomas suggested to set the variable g:Tex_UseCiteCompletionVer2. Thanks! Besides this, as he says, it is not a good thing having to set this variable. Is it part of an unfinished work? Best, Matías |
From: Till M. <ope...@ti...> - 2009-04-26 19:31:38
|
On Fr April 24 2009, Thomas Ibbotson wrote: > Peter Lewis wrote: > > Excellent, yes I can confirm that it works with that patch. > > Great! There may be other things that don't work properly with spaces in > the path to a .tex file. If you come across any let me know and I'll > have a go at fixing those too. I am preparing a big patch to fix the filename-escaping everywhere in vim- latex, maybe you can review / test it, before I commit it. I hope to finish it tomorrow, but there are a lot of places to change it. It will then use fnameescape(), which will also escape other special characters. I somehow managed to find the function more or less by accident. I will take a look at the other patch with the windows shellescape afterwards. Regards Till |
From: Till M. <ope...@ti...> - 2009-04-26 17:57:33
|
On So April 26 2009, Thomas Ibbotson wrote: > This is caused by a simple typo in compiler.vim. The attached patch > against svn rev 1048 fixes it for me. Thanks, the patch has been applied in changeset 1049. Regards Till |
From: John B. <jb...@gm...> - 2009-04-26 04:30:20
|
Dear Ted: I appreciate you very much for your kindly help. However it is regretful that it did not work for me. But I just found an alternative way for this issue. I state it out so that maybe some other help can benefit from it. Put the following line :map \ld :execute '!LC_ALL=C xdvi -s 4 -sourceposition ' . line(".") . expand("%") . " " . expand(Tex_GetMainFileName(':r')) . ".dvi &"<CR><CR> into .vimrc file. So that we can use \ld instead of \ls I guess this is basically the vim-latex did for \ls.... I learned this from http://vim.wikia.com/wiki/Vim_can_interact_with_xdvi by which one can also defines the inverse search( which I never succeeded...) Thank you Ted ;-) Thank you. Have a nice weekend. On Sun, Apr 26, 2009 at 2:32 AM, Ted Pavlic <te...@te...> wrote: >> yes I tried, it really works, however... by such configuration I >> cannot get the forward search.... > > If I recall correctly, forward search passes the line number to xdvi via > parameters. The line I suggested... > >>> let g:Tex_ViewRule_dvi = 'bash -c "LC_ALL=C xdvi \$1" xdvi ' > > Only deals with one parameter. Try replacing the \$1 with \$* or \$@ > (with some quoting to deal with spaces). > > --Ted > > >>> >>> You might have to play around with the quoting, but in principle I think >>> it would work...<?> >>> >>> --Ted >>> >>> >>> -- >>> Ted Pavlic<te...@te...> >>> >>> Please visit my ALS association page: >>> http://web.alsa.org/goto/tedpavlic >>> My family appreciates your support in the fight to defeat ALS. >>> >>> ------------------------------------------------------------------------------ >>> Crystal Reports- New Free Runtime and 30 Day Trial >>> Check out the new simplified licensign option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> _______________________________________________ >>> Vim-latex-devel mailing list >>> Vim...@li... >>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >>> >> > > -- > Ted Pavlic <te...@te...> > > Please visit my ALS association page: > http://web.alsa.org/goto/tedpavlic > My family appreciates your support in the fight to defeat ALS. > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Ted P. <te...@te...> - 2009-04-26 02:32:44
|
> yes I tried, it really works, however... by such configuration I > cannot get the forward search.... If I recall correctly, forward search passes the line number to xdvi via parameters. The line I suggested... >> let g:Tex_ViewRule_dvi = 'bash -c "LC_ALL=C xdvi \$1" xdvi ' Only deals with one parameter. Try replacing the \$1 with \$* or \$@ (with some quoting to deal with spaces). --Ted >> >> You might have to play around with the quoting, but in principle I think >> it would work...<?> >> >> --Ted >> >> >> -- >> Ted Pavlic<te...@te...> >> >> Please visit my ALS association page: >> http://web.alsa.org/goto/tedpavlic >> My family appreciates your support in the fight to defeat ALS. >> >> ------------------------------------------------------------------------------ >> Crystal Reports- New Free Runtime and 30 Day Trial >> Check out the new simplified licensign option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim...@li... >> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >> > -- Ted Pavlic <te...@te...> Please visit my ALS association page: http://web.alsa.org/goto/tedpavlic My family appreciates your support in the fight to defeat ALS. |
From: John B. <jb...@gm...> - 2009-04-26 01:07:38
|
Dear Ted: yes I tried, it really works, however... by such configuration I cannot get the forward search.... :( Thank you very much for spending time on my question. Peng On Sun, Apr 26, 2009 at 12:46 AM, Ted Pavlic <te...@te...> wrote: >> let g:Tex_ViewRule_dvi = 'LC_ALL=C xdvi ' > > Have you tried something like... > > bash -c 'LC_ALL=C xdvi' > > ? That is, > > let g:Tex_ViewRule_dvi = 'bash -c "LC_ALL=C xdvi \$1" xdvi ' > > You might have to play around with the quoting, but in principle I think > it would work... <?> > > --Ted > > > -- > Ted Pavlic <te...@te...> > > Please visit my ALS association page: > http://web.alsa.org/goto/tedpavlic > My family appreciates your support in the fight to defeat ALS. > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Thomas I. <tho...@gm...> - 2009-04-26 00:55:35
|
Hi, Here's another patch to texviewer.vim against the current SVN version. This now matches bibitems with labels i.e. \bibitem[foo]{bar} when using a \thebibliography environment. I also noticed that \cite completion did not work for a file with a \thebibliography environment unless I put the following line in my .vimrc: let g:Tex_UseCiteCompletionVer2 = 0 Is this just unfinished? I have had a look, and haven't thought of an easy way to fix this, but I'm happy to come up with something if this isn't already being currently worked on. Thanks, Tom |
From: Ted P. <te...@te...> - 2009-04-26 00:46:40
|
> let g:Tex_ViewRule_dvi = 'LC_ALL=C xdvi ' Have you tried something like... bash -c 'LC_ALL=C xdvi' ? That is, let g:Tex_ViewRule_dvi = 'bash -c "LC_ALL=C xdvi \$1" xdvi ' You might have to play around with the quoting, but in principle I think it would work... <?> --Ted -- Ted Pavlic <te...@te...> Please visit my ALS association page: http://web.alsa.org/goto/tedpavlic My family appreciates your support in the fight to defeat ALS. |
From: John B. <jb...@gm...> - 2009-04-26 00:31:06
|
Hi guys I recently installed the latest svn version of vim-latex and I am using texlive 2008. It is a great software. However I personally have a weird problem stopping me from enjoying it: It is about my xdvi in texlive2008. Every time I open it in a terminal I have to wait for quite a bit long time, and receive the folloing warning message: Warning: Missing charsets in String to FontSet conversion So I add an alias alias xdvi = "LC_ALL=C xdvi " in my .bashrc. LC_ALL=C helps me to launch xdvi in terminal instaneously. While for enjoying vim-latex, especially its forward search I have to make some modification to launch xdvi by pressing \ls. However, I found that if I write let g:Tex_ViewRule_dvi = 'LC_ALL=C xdvi ' in my .vimrc and pressing \ls I got thousands of error messages on the screen. I could not paste the messages out since everytime when I tried to select them and copy them, they disappered. I guess the problem is the updated compiler.vim, since I did not met this problem in the older version of vim-latex. So I tried to replace all words xdvi in .vim/ftplugin/latex-suite/compiler.vim by LC_ALL=C xdvi. but it does not work.:( So, could anybody kindly help me on this issue? If anyone can explain why xdvi spends so long time to launch, it would be the best. Thank you :-) John |
From: peng s. <sha...@gm...> - 2009-04-25 22:22:31
|
Dear Tom: Thank you very much :-) Peng Shao On Sat, Apr 25, 2009 at 10:00 PM, Thomas Ibbotson <tho...@gm...> wrote: > peng shao wrote: >> >> hi dear all, sorry for bothering but I met another problem with the >> current svn version. I am using VIM 7.2. >> >> The first time I tried the svn version, I remember everything works >> very well and I was quite happy with it. However, after some time >> (I cannot remember what happend), >> it was not working well anymore. So I delete the whole .vim folder >> and re-download the svn version and re-installed it. But the problem >> remains: when I press \ls I got some error message on screen as >> in the attachment. >> >> The strange thing is that, after I replaced the updated compiler.vim file >> in >> .vim/ftplugin/latex-suite/ with the old compile.vim file in 20060325 >> version, >> everything woks fine again. >> >> The following is the contents in my .vimrc file >> filetype plugin on >> filetype indent on >> set shellslash >> set number >> set textwidth=90 >> set mouse=a >> syntax on >> set grepprg=grep\ -nH\ $* >> let g:tex_flavor = "latex" >> let g:Tex_CompileRule_dvi="latex -src-specials -interaction=nonstopmode >> $*" >> let g:Tex_ViewRule_dvi = 'xdvi' >> >> >> Could anyone help me on this problem?:( Thank you. >> > > This is caused by a simple typo in compiler.vim. The attached patch against > svn rev 1048 fixes it for me. > > Tom > |
From: Thomas I. <tho...@gm...> - 2009-04-25 22:01:15
|
peng shao wrote: > hi dear all, sorry for bothering but I met another problem with the > current svn version. I am using VIM 7.2. > > The first time I tried the svn version, I remember everything works > very well and I was quite happy with it. However, after some time > (I cannot remember what happend), > it was not working well anymore. So I delete the whole .vim folder > and re-download the svn version and re-installed it. But the problem > remains: when I press \ls I got some error message on screen as > in the attachment. > > The strange thing is that, after I replaced the updated compiler.vim file in > .vim/ftplugin/latex-suite/ with the old compile.vim file in 20060325 version, > everything woks fine again. > > The following is the contents in my .vimrc file > filetype plugin on > filetype indent on > set shellslash > set number > set textwidth=90 > set mouse=a > syntax on > set grepprg=grep\ -nH\ $* > let g:tex_flavor = "latex" > let g:Tex_CompileRule_dvi="latex -src-specials -interaction=nonstopmode $*" > let g:Tex_ViewRule_dvi = 'xdvi' > > > Could anyone help me on this problem?:( Thank you. > This is caused by a simple typo in compiler.vim. The attached patch against svn rev 1048 fixes it for me. Tom |
From: peng s. <sha...@gm...> - 2009-04-25 19:58:08
|
hi dear all, sorry for bothering but I met another problem with the current svn version. I am using VIM 7.2. The first time I tried the svn version, I remember everything works very well and I was quite happy with it. However, after some time (I cannot remember what happend), it was not working well anymore. So I delete the whole .vim folder and re-download the svn version and re-installed it. But the problem remains: when I press \ls I got some error message on screen as in the attachment. The strange thing is that, after I replaced the updated compiler.vim file in .vim/ftplugin/latex-suite/ with the old compile.vim file in 20060325 version, everything woks fine again. The following is the contents in my .vimrc file filetype plugin on filetype indent on set shellslash set number set textwidth=90 set mouse=a syntax on set grepprg=grep\ -nH\ $* let g:tex_flavor = "latex" let g:Tex_CompileRule_dvi="latex -src-specials -interaction=nonstopmode $*" let g:Tex_ViewRule_dvi = 'xdvi' Could anyone help me on this problem?:( Thank you. |
From: Thomas I. <tho...@gm...> - 2009-04-24 15:09:28
|
Peter Lewis wrote: > Excellent, yes I can confirm that it works with that patch. > Great! There may be other things that don't work properly with spaces in the path to a .tex file. If you come across any let me know and I'll have a go at fixing those too. > Thanks again! > No worries. Back to real work.... Tom |
From: Peter L. <pr...@le...> - 2009-04-24 14:59:55
|
On Friday 24 Apr 2009 15:42:02 Thomas Ibbotson wrote: > No problem :) This is much more fun than what I'm supposed to be doing > at the moment.... heh heh, I know the feeling ;-) > Ok, so I've found the problem. The function Tex_StartOutlineCompletion() > sets some mappings which include the directory, but this is not properly > escaped. I have attached an amended patch which deals with this issue > against the current SVN version (i.e. this patch also includes the > changes from the patch I originally sent out fixing the problems in > windows). This could do with a bit more testing as there may be other > things that need escaping for other situations, but for now this should > fix your problem. Excellent, yes I can confirm that it works with that patch. Thanks again! Pete. |
From: Thomas I. <tho...@gm...> - 2009-04-24 14:43:05
|
Peter Lewis wrote: > Hi Tom, > > Thanks for all your help trying to sort this out :-) > > No problem :) This is much more fun than what I'm supposed to be doing at the moment.... Ok, so I've found the problem. The function Tex_StartOutlineCompletion() sets some mappings which include the directory, but this is not properly escaped. I have attached an amended patch which deals with this issue against the current SVN version (i.e. this patch also includes the changes from the patch I originally sent out fixing the problems in windows). This could do with a bit more testing as there may be other things that need escaping for other situations, but for now this should fix your problem. Tom |
From: Peter L. <pr...@le...> - 2009-04-24 14:16:33
|
Hi Tom, Thanks for all your help trying to sort this out :-) On Friday 24 Apr 2009 15:01:26 Thomas Ibbotson wrote: > Does your version of Vim have python compiled in it? You can find this > out easily by doing ':echo has('python')'. If that returns 1 Yes, it did. > , can you do > ':let Tex_UsePython = 0' (or add that line to your .vimrc) and try > again? No change, I'm afraid. > If this then works then there is a problem in the way in which it > is calling the internal python. Otherwise I don't know what's wrong, and > I'd need to find a way of reproducing it. I should point out that everything works find so long as there is no space in the path of the .tex file I'm editing. I can reproduce the problem quite easily here (in Linux), by doing the following: 1. Create a directory with a space and cd into it as follows: % mkdir test\ folder % cd test\ folder Create a new .tex file here, or copy an old one into it. Make sure the .tex file has a \label somewhere which you can \ref. Type \ref{ and then try to complete using F9 (actually, I should point out that I have "imap <buffer> <S-tab> <Plug>Tex_Completion" in my .vimrc, but I wouldn't have thought that would be the problem, since it works with no spaces in the path). The __OUTLINE__ box opens, and I can browse to the label I created. Move the cursor onto it and hit enter. I get "E172: Only one file name allowed" in the bottom of the terminal. Does this not produce the same behaviour for you? Thanks again, Pete. |
From: Thomas I. <tho...@gm...> - 2009-04-24 14:02:39
|
Peter Lewis wrote: > On Friday 24 Apr 2009 12:43:09 Thomas Ibbotson wrote: > >> I recently sent a patch to this mailing list fixing a problem in >> texviewer.vim with it's way of calling outline.py. I didn't think at the >> time about spaces in the filename as well. So I have created a new patch >> which fixes the problem on windows. This patch is against the current >> SVN version, it includes a workaround for a problem in vim with the >> default shellxquote on windows (see See >> http://groups.google.com/group/vim_dev/browse_thread/thread/3d1cc6cb0c09od27b3). >> >> Peter, this may also fix your problem, could you test it for me on your >> system? >> > > Thanks Tom - I tested it and didn't get any noticeable changes I'm afraid. Incidentally, in doing so I also tested the current SVN version and that gives me the same behaviour as I originally reported. > > Thanks. > > Pete. > Hi Pete, Does your version of Vim have python compiled in it? You can find this out easily by doing ':echo has('python')'. If that returns 1, can you do ':let Tex_UsePython = 0' (or add that line to your .vimrc) and try again? If this then works then there is a problem in the way in which it is calling the internal python. Otherwise I don't know what's wrong, and I'd need to find a way of reproducing it. Thanks, Tom |
From: Peter L. <pr...@le...> - 2009-04-24 13:54:12
|
On Friday 24 Apr 2009 12:43:09 Thomas Ibbotson wrote: > I recently sent a patch to this mailing list fixing a problem in > texviewer.vim with it's way of calling outline.py. I didn't think at the > time about spaces in the filename as well. So I have created a new patch > which fixes the problem on windows. This patch is against the current > SVN version, it includes a workaround for a problem in vim with the > default shellxquote on windows (see See > http://groups.google.com/group/vim_dev/browse_thread/thread/3d1cc6cb0c0d27b3). > > Peter, this may also fix your problem, could you test it for me on your > system? Thanks Tom - I tested it and didn't get any noticeable changes I'm afraid. Incidentally, in doing so I also tested the current SVN version and that gives me the same behaviour as I originally reported. Thanks. Pete. |
From: Thomas I. <tho...@gm...> - 2009-04-24 11:43:21
|
I recently sent a patch to this mailing list fixing a problem in texviewer.vim with it's way of calling outline.py. I didn't think at the time about spaces in the filename as well. So I have created a new patch which fixes the problem on windows. This patch is against the current SVN version, it includes a workaround for a problem in vim with the default shellxquote on windows (see See http://groups.google.com/group/vim_dev/browse_thread/thread/3d1cc6cb0c0d27b3). Peter, this may also fix your problem, could you test it for me on your system? Thanks, Tom |
From: Peter L. <pr...@le...> - 2009-04-24 09:44:52
|
Hi Tom, Thanks for the speedy reply. I wrote: > > Completion of \ref tags isn't working for me when the .tex document I'm editing is in a directory which has spaces in the path. It shows the list of labels to choose from, but when I press enter, I get the following error: > > > > E172: Only one file name allowed. > > > > Which I guess means that the space is making the completion script think that it's multiple arguments (files). > > > > Is there a way to fix this behaviour? I'm using vim 7.2, python 2.6.1 and latex-suite 20060325. On Friday 24 Apr 2009 00:27:07 Thomas Ibbotson wrote: > I can't reproduce this bug on ubuntu linux, what operating system are > you using? Sorry, I should have said - I'm using Arch Linux. > I've just tested this on windows as well, and I get a different error to > you. I get a python error from outline.py: > > Traceback (most recent call last): > File "C:\Program Files\Vim\vimfiles\ftplugin\latex-suite\outline.py", > line 183, in <module> > print main(sys.argv[1], prefix) > File "C:\Program Files\Vim\vimfiles\ftplugin\latex-suite\outline.py", > line 170, in main > contents = getFileContents(root, ext) > File "C:\Program Files\Vim\vimfiles\ftplugin\latex-suite\outline.py", > line 23, in getFileContents > contents = '\n'.join(open(fname).read().splitlines()) > IOError: [Errno 2] No such file or directory: 'paper' Interesting.. I don't have a Windows box to test it on here. > This might have been fixed in SVN but I'm going to bed now, I'll check > tomorrow. Okay, thanks. I haven't checked the SVN version of latex-suite, since there isn't a package for it on ArchLinux, but I guess it should be trivial for me to do so. Will check and get back to you. Thanks again, Pete. |
From: Thomas I. <tho...@gm...> - 2009-04-23 23:27:19
|
Peter Lewis wrote: > Hi there, > > Completion of \ref tags isn't working for me when the .tex document I'm editing is in a directory which has spaces in the path. It shows the list of labels to choose from, but when I press enter, I get the following error: > > E172: Only one file name allowed. > > Which I guess means that the space is making the completion script think that it's multiple arguments (files). > > Is there a way to fix this behaviour? I'm using vim 7.2, python 2.6.1 and latex-suite 20060325. > > Thanks! > > Pete. > > I've just tested this on windows as well, and I get a different error to you. I get a python error from outline.py: Traceback (most recent call last): File "C:\Program Files\Vim\vimfiles\ftplugin\latex-suite\outline.py", line 183, in <module> print main(sys.argv[1], prefix) File "C:\Program Files\Vim\vimfiles\ftplugin\latex-suite\outline.py", line 170, in main contents = getFileContents(root, ext) File "C:\Program Files\Vim\vimfiles\ftplugin\latex-suite\outline.py", line 23, in getFileContents contents = '\n'.join(open(fname).read().splitlines()) IOError: [Errno 2] No such file or directory: 'paper' This might have been fixed in SVN but I'm going to bed now, I'll check tomorrow. Tom |
From: Thomas I. <tho...@gm...> - 2009-04-23 23:20:50
|
Peter Lewis wrote: > Hi there, > > Completion of \ref tags isn't working for me when the .tex document I'm editing is in a directory which has spaces in the path. It shows the list of labels to choose from, but when I press enter, I get the following error: > > E172: Only one file name allowed. > > Which I guess means that the space is making the completion script think that it's multiple arguments (files). > > Is there a way to fix this behaviour? I'm using vim 7.2, python 2.6.1 and latex-suite 20060325. > > Thanks! > > Pete. > Hi Pete, I can't reproduce this bug on ubuntu linux, what operating system are you using? Thanks, Tom |
From: Peter L. <pr...@le...> - 2009-04-23 09:46:10
|
Hi there, Completion of \ref tags isn't working for me when the .tex document I'm editing is in a directory which has spaces in the path. It shows the list of labels to choose from, but when I press enter, I get the following error: E172: Only one file name allowed. Which I guess means that the space is making the completion script think that it's multiple arguments (files). Is there a way to fix this behaviour? I'm using vim 7.2, python 2.6.1 and latex-suite 20060325. Thanks! Pete. |
From: Till M. <ope...@ti...> - 2009-04-21 19:07:55
|
On Di April 21 2009, Stefanie Fauconnier wrote: > I have the same problem. When I hit <F5> in insert mode and choose an > environment (doesn't matter which one) there is a redundant " before the > cursor. I'm using vim-latexsuite 20060325-4.1 on Ubuntu Hardy (installed > from the Ubuntu repos). Is there a big difference between this version and > the current svn version? I don't know if I'd better upgrade or not, I made > quite a few customizations so I don't know if it would matter that much > anyway (I replaced most math functionalities with shortcuts and combo's for > linguists). Where can I find the subversion repository? Here you can find the instructions for the vim-latex svn repository: https://sourceforge.net/scm/?type=svn&group_id=52322 There seems to be a fix in svn for your problem according to the log message: http://vim-latex.svn.sourceforge.net/viewvc/vim-latex?view=rev&revision=1013 I am not sure, whether an update is worth it for you, but some bugs have been fixed in svn, that were present in the latest tarball release. Regards, Till |
From: Kay S. <kay...@ma...> - 2009-04-21 15:36:50
|
Hey, I use the latest svn trunk version. If I leave the > TexLet g:Tex_ImageDir = '' in texrc the <F9>-completion of \includegraphics{ aborts without any message. Setting it to > Tex_ImageDir = '.' brings the completion back to life. So this could be a better default value. But the inserted path way too long, e.g. ..//home/.../tex/file Changing the param value for the root dir for Tex_SetupFileCompletion to '' solves this problem for me. I have attached a tiny patch... maybe someone can use it sometime. Kind regards, Kay |