vim-latex-devel Mailing List for Vim-Latex (Page 43)
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: Till M. <ope...@ti...> - 2009-08-16 23:56:53
|
On Sun, Aug 16, 2009 at 06:04:29PM -0400, Raffi Khatchadourian wrote: > On Aug 16, 2009, at 3:17 PM, Till Maas wrote: > >> On Sat, Aug 15, 2009 at 04:44:41PM -0400, Raffi Khatchadourian wrote: >>> Sorry, I should have mentioned that spell was being set in my .vimrc >>> file. I've tried creating the tex.vim file and adding the suggested >>> line setlocal spell. What I just discovered is that the spell >>> underlining works for certain tex files but not others! That's very >>> strange. Any help would be greatly appreciated, thanks! >> >> Someone might help you a lot easier, if you provide an minimal example >> tex file for which the spell checking does not work. > > Well, this was an interesting exercise! It seems that the spell check > only works when certain environments and commands are used. For example, > the spell check works fine when the \begin{document} and \end{document} > commands are present. It also works when the \section{...} and The problem is afaics not vim-latex related, but maybe somehow hidden in the tex syntax rules shipped with vim. This is a workaround that works here on Fedora 10: :syntax spell toplevel References: http://vimdoc.sourceforge.net/htmldoc/syntax.html#:syn-spell :help spell-syntax Nevertheless it would be nice if you could forward this to the tex syntax file maintainer, but I do not know how to get in contact with him. Regards Till |
From: Raffi K. <kha...@cs...> - 2009-08-16 22:05:26
|
On Aug 16, 2009, at 3:17 PM, Till Maas wrote: > On Sat, Aug 15, 2009 at 04:44:41PM -0400, Raffi Khatchadourian wrote: >> Sorry, I should have mentioned that spell was being set in my .vimrc >> file. I've tried creating the tex.vim file and adding the suggested >> line setlocal spell. What I just discovered is that the spell >> underlining works for certain tex files but not others! That's very >> strange. Any help would be greatly appreciated, thanks! > > Someone might help you a lot easier, if you provide an minimal example > tex file for which the spell checking does not work. Well, this was an interesting exercise! It seems that the spell check only works when certain environments and commands are used. For example, the spell check works fine when the \begin{document} and \end{document} commands are present. It also works when the \section{...} and \chapter{...} commands are present. However, it does not work when there is, for example, only \begin{theorem} or \end{theorem} commands present. I use a lot of \include and \input commands in my tex documents, so, naturally, many files will not have \section, \chapter, or \begin{document}...\end{document} commands. I've attached two minimal sample tex files to this email. The first tex file illistrates a situations where the spell check *does not* work. The second illustrates a situation where the spell check *does* work. Any help would be greatly appreciated! |
From: Till M. <ope...@ti...> - 2009-08-16 19:31:19
|
On Wed, Aug 12, 2009 at 03:03:59PM +0200, Alexander Stefanescu wrote: > I've included a patch against vim-latex-1.5-20090804-r1058 that fixes > this problem for me. Thank you, the patch has been applied in revision 1062. Regards Till |
From: Mike R. <ri...@um...> - 2009-08-16 19:26:12
|
> When I compile the file, the cursor doesn't stay where I compiled.It > always jumps to the beginnig of line.. Although it doesn't bother > me, I wonder it happens to you too. This happens to me too. You can always just use `` afterwards to go back to the same spot. Or, you can make a mapping that includes that. This is what I have in my ~/.vim/ftplugin/tex.vim: map <buffer><leader>la :w<cr><leader>ll<c-l>`` It saves, compiles with <leader>ll, clears, and returns the cursor. Mike On Sun, Aug 16, 2009 at 8:21 AM, ahmet nurlu<ahm...@ya...> wrote: > Hi List, > When I compile the file, the cursor doesn't stay where I compiled.It > always jumps to the beginnig of line.. Although it doesn't bother > me, I wonder it happens to you too. > > Regards, > Ahmet > > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Till M. <ope...@ti...> - 2009-08-16 19:18:15
|
On Sat, Aug 15, 2009 at 04:44:41PM -0400, Raffi Khatchadourian wrote: > Sorry, I should have mentioned that spell was being set in my .vimrc > file. I've tried creating the tex.vim file and adding the suggested > line setlocal spell. What I just discovered is that the spell > underlining works for certain tex files but not others! That's very > strange. Any help would be greatly appreciated, thanks! Someone might help you a lot easier, if you provide an minimal example tex file for which the spell checking does not work. Regards Till |
From: Matías G. <ma...@dm...> - 2009-08-16 13:03:46
|
You don't always need that 4-step sequence. It depends on whether your \cite's and \ref's changed from the last time you compiled. When you latex a file, if you need to compile it again, the compiler spits a line telling so. Latex-suite reads the output and compiles when needed. Do you get a _different_ dvi/pdf/ps if you compile again? In this case, this would be a bug. Matías On Sun, Aug 16, 2009 at 01:42:33AM -0500, YueJun Yin wrote: > Hi > When I type \ll at a tex file in GVIM, there is a sentence in the bottom > saying > Running 'bibtex'... > Ran latex 1 time(s) > Press ENTER or type command to continue > > How do I handle such condition? As far as I know, to compile a tex file > (with citation), I should do the four tasks in sequence as > latex,bibtex,latex,latex. How can I do this in vim? > Eugene |
From: ahmet n. <ahm...@ya...> - 2009-08-16 12:21:42
|
Hi List, When I compile the file, the cursor doesn't stay where I compiled.It always jumps to the beginnig of line.. Although it doesn't bother me, I wonder it happens to you too. Regards, Ahmet |
From: YueJun Y. <yj...@gm...> - 2009-08-16 05:41:22
|
Hi When I type \ll at a tex file in GVIM, there is a sentence in the bottom saying Running 'bibtex'... Ran latex 1 time(s) Press ENTER or type command to continue How do I handle such condition? As far as I know, to compile a tex file (with citation), I should do the four tasks in sequence as latex,bibtex,latex,latex. How can I do this in vim? Eugene |
From: Raffi K. <kha...@cs...> - 2009-08-15 20:48:29
|
In fact, its not only the underlining that doesn't work, it doesn't seem to recognize misspelled words even with the ]s keystroke, despite 'spell' being turned on. On Aug 15, 2009, at 4:17 PM, Mike Richman wrote: > Do you have a ~/.vim/ftplugin/tex.vim? I think if you just put > "setlocal spell" in there, you should be ok. > > Mike > > On Sat, Aug 15, 2009 at 2:29 PM, Raffi > Khatchadourian<kha...@cs...> wrote: >> Does anyone have a problem with spell check highlighting not working >> when the filetype is equal to tex? The red underlinings don't show up >> until I switch the file type equal to txt, however, I loose the tex >> syntax highlighting in the process. Thanks! >> >> Raffi >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports >> 2008 30-Day >> trial. Simplify your report design, integration and deployment - >> and focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim...@li... >> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >> |
From: Raffi K. <kha...@cs...> - 2009-08-15 20:45:29
|
Sorry, I should have mentioned that spell was being set in my .vimrc file. I've tried creating the tex.vim file and adding the suggested line setlocal spell. What I just discovered is that the spell underlining works for certain tex files but not others! That's very strange. Any help would be greatly appreciated, thanks! On Aug 15, 2009, at 4:17 PM, Mike Richman wrote: > Do you have a ~/.vim/ftplugin/tex.vim? I think if you just put > "setlocal spell" in there, you should be ok. > > Mike > > On Sat, Aug 15, 2009 at 2:29 PM, Raffi > Khatchadourian<kha...@cs...> wrote: >> Does anyone have a problem with spell check highlighting not working >> when the filetype is equal to tex? The red underlinings don't show up >> until I switch the file type equal to txt, however, I loose the tex >> syntax highlighting in the process. Thanks! >> >> Raffi >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports >> 2008 30-Day >> trial. Simplify your report design, integration and deployment - >> and focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Vim-latex-devel mailing list >> Vim...@li... >> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >> |
From: Mike R. <ri...@um...> - 2009-08-15 20:18:06
|
Do you have a ~/.vim/ftplugin/tex.vim? I think if you just put "setlocal spell" in there, you should be ok. Mike On Sat, Aug 15, 2009 at 2:29 PM, Raffi Khatchadourian<kha...@cs...> wrote: > Does anyone have a problem with spell check highlighting not working > when the filetype is equal to tex? The red underlinings don't show up > until I switch the file type equal to txt, however, I loose the tex > syntax highlighting in the process. Thanks! > > Raffi > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Raffi K. <kha...@cs...> - 2009-08-15 18:52:04
|
Does anyone have a problem with spell check highlighting not working when the filetype is equal to tex? The red underlinings don't show up until I switch the file type equal to txt, however, I loose the tex syntax highlighting in the process. Thanks! Raffi |
From: Mike R. <ri...@um...> - 2009-08-15 17:47:08
|
Eugene, > what I got looks like a regular vim editor: > http://picasaweb.google.com/lh/photo/by-Af3qJXZZ3b3wWRe1slg?feat=directlink In this screenshot, it looks like you've got latex-suite working. To get the menus, you'll need to use gvim, i.e. "gvim foo.tex". Mike On Sat, Aug 15, 2009 at 11:41 AM, YueJun Yin<yj...@gm...> wrote: > Hi all > I am using Fedora 11 and vim 7. Was trying to install latex-suite. I did the > instruction according to: > http://vim-latex.sourceforge.net/index.php?subject=download&title=Download > > No problem for the 1st step. > In the 2nd step, I did not find the file ~/.vimrc. However, there is a vimrc > in /etc/. I am not sure I should edit /etc/vimrc or create ~/.vimrc. I did > the later one. Now I create ~/.vimrc and edit it with the instruction > according to: > http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html > > Similarly, I did not find the file ~/.vim/ftplugin/tex.vim. There were two > files and a folder, where were bib_latexSuite.vim, tex_latexSuite.vim, and > latex-suite, respectively. So I created the file tex.vim and putted it into > ~/.vim/ftplugin/. > > The third step is really confusing. "start vim and do the following: > > helptags ~/.vim/doc" > > Shouldn't there be a colon (:) before helptags? Whatever, I added a colon > before helptags. Then I typed ":help latex-suite.txt". The latex-suite.txt > file popped out. I thought I was done with the installation. > > I tried "vim foo.tex" in bash shell. I did not get the latex-suite GUI as > shown in : > http://vim-latex.sourceforge.net/index.php?subject=screenshots&title=Screenshots > > what I got looks like a regular vim editor: > http://picasaweb.google.com/lh/photo/by-Af3qJXZZ3b3wWRe1slg?feat=directlink > > Please help me with this. Thanks. > > -- > Yue-Jun Yin (Eugene) > PhD Candidate > Civil & Environmental Engineering Dept. > Michigan Tech University > 1400 Townsend Dr. > Houghton, MI 49931 USA > phone:(908)998-2573 > email:yu...@mt... > http://www.cee.mtu.edu/~yuejuny/ > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > |
From: Till M. <ope...@ti...> - 2009-08-13 08:07:06
|
On Thu, Aug 13, 2009 at 07:41:51AM +0100, Daniele Avitabile wrote: > would it be possible to know how to obtain, install, and eventually patch > the new snapshots? Installation and download instructions are available on the website: http://vim-latex.sourceforge.net/index.php?subject=download&title=Download I don't know what you want to patch, but if you have a patch, you can apply it with the patch command: patch -pX < foo.patch X has to be substituted with the number of directories that have to be stripped from the path in the patch file to access the files to be patched, if you are in the directory that contains ftplugin, for a patch with the following header, you need to use 0. If you are already in the directory, where the texproject.vim file is, you need to use 2: --- ftplugin/latex-suite/texproject.vim 2009-08-12 02:05:56 +0200 Regards Till |
From: Daniele A. <d.a...@gm...> - 2009-08-13 06:42:05
|
Hi all, would it be possible to know how to obtain, install, and eventually patch the new snapshots? Best. Daniele On Wed, Aug 12, 2009 at 10:43 PM, Till Maas <ope...@ti...> wrote: > On Wed, Aug 12, 2009 at 03:00:38PM +0200, Alexander Stefanescu wrote: > > > I've tracked the problem down to an apparent bug in the .latexmain > > searching & sourcing code in texproject.vim. I propose the attached > > trivial patch against vim-latex-1.5-20090804-r1058, which fixes the > > issue for me. > > Thanks for your patch, it has been applied in r1059 together with the > actual fnameescape changes for texproject.vim. I will look at the other > patch tomorrow. The snapshot I created was faulty, because I accidently > included uncommited changes like the fnameesacpe stuff from > texproject.main instead of the real HEAD of the repository. This is > fixed now in the Makefile and a new tarball with the actual results will > be published soon. > > Regards > Till > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > |
From: Till M. <ope...@ti...> - 2009-08-12 21:43:53
|
On Wed, Aug 12, 2009 at 03:00:38PM +0200, Alexander Stefanescu wrote: > I've tracked the problem down to an apparent bug in the .latexmain > searching & sourcing code in texproject.vim. I propose the attached > trivial patch against vim-latex-1.5-20090804-r1058, which fixes the > issue for me. Thanks for your patch, it has been applied in r1059 together with the actual fnameescape changes for texproject.vim. I will look at the other patch tomorrow. The snapshot I created was faulty, because I accidently included uncommited changes like the fnameesacpe stuff from texproject.main instead of the real HEAD of the repository. This is fixed now in the Makefile and a new tarball with the actual results will be published soon. Regards Till |
From: Alexander S. <as...@ph...> - 2009-08-12 13:04:57
|
On 2009-04-21 19:07, Till Maas wrote > 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). I also had this problem with vim-latexsuite 20060325-4.1. Moving to the current vim-latex-1.5-20090804-r1058 tarball release downloaded from sourceforge fixed it for me. >> 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). Beware, I did have problems upgrading from 20060325-4.1 to vim-latex-1.5-20090804-r1058. Like you, I had loads of customizations in the code, but recent clean-ups apparently also introduced a number of small bugs. See my other mails for patches. Back to the <F5> bug: Before trying vim-latex-1.5-20090804-r1058, I digged into this problem as well. What I found is a bit worrying, as it might indicate a bug in vim that needs to be reported upstream. When calling vim's input() function with a string that contains newlines, $BAD_THINGS can happen much later. In this example, the following occurred: Tex_DoEnvironment() | \-calls PromptForEnvironment() | | | \-calls Tex_InputChooseFromPrompt() | | | \-calls input("a \n long \n string \n with \n newlines") | \-calls Tex_PutEnvironment() | \-calls IMAP_PutTextWithMovement() | \-uses expression register (c_CTRL-R_=) to enter movement string The string entered into the document by IMAP_PutTextWithMovement with the expression register is quite complicated, containing some function calls to set position and the likes. When entering the string into the expression register by hand, it works okay. It also works okay in IMAP_PutTextWithMovement() with _most_ strings. Apparently, only some special characters like \[ (escape?) cause problems. The problems go away if you change the prompt-string used in input() to not contain newlines. Also, the problems go away if you use inputdisplay() in a gui. To me it looks a bit like vim's implementation of input() has some buffer overflow that causes problems *much* later. Bad, _bad_ thing. > 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 This log message says: > Bug: In vim7, 'exe pos' doesn't seem to always work. Sometimes it leads to > a spurious double-quote being inserted into the text. I have no idea > why this happens. However, using vim's native setpos() when available > seems to not have this problem. While using setpos() instead of exe pos obviously doesn't trigger the problem any more, this might turn up any time again, as vim-latex uses input() with \n constantly. Therefore I wouldn't consider this bug fixed yet, even if it's working at the moment. This should probably be investigated by a more experienced vim-latex developer, and if it's indeed a bug in input(), it needs to be fixed upstream. I'll leave the upstream reporting in the capable hands of the aforementioned experienced vim-latex developer ;) Cheers, Alex |
From: Alexander S. <as...@ph...> - 2009-08-12 13:04:12
|
Hi list, there have been a couple of reports on the F9-completion not working properly in \cite{} recently. Since I have been bitten myself, I've taken a look at the problem. Seems at one point the recent fnameescape-patch overlooked to expand a string before escaping, and on two occasions the same cd-related bug that I've reported in my other email hit in the completion code. I have tested this with vim-latex-1.5-20090804-r1058 and vim 7.1.138 and vim 7.2.22. The error message was something like: Error detected while processing function Tex_Complete: line 9: E15: Invalid expression: %:p:h) E116: Invalid arguments for function fnameescape(%:p:h) E15: Invalid expression: 'cd '.fnameescape(%:p:h) line 74: E344: Can't find directory "s:origdir" in cdpath E472: Command failed I've included a patch against vim-latex-1.5-20090804-r1058 that fixes this problem for me. Cheers, Alex |
From: Alexander S. <as...@ph...> - 2009-08-12 13:01:14
|
Hi list, I've recently noticed the following unexpected behaviour. I have tested this with vim-latex-1.5-20090804-r1058 and vim 7.1.138 and vim 7.2.22. When opening a file e.g. with :e or gf, the cwd changes to the directory of that file. While in most scenarios you won't notice, in mine it does have an impact. I have a big document organised in lots of smaller files, that reside in a subdirectory together with images etc: main.tex intro/intro.tex chap1/chap1.tex .../... Since I'd like images to be generated automatically (plus a number of other niceties), I compile with a combination of make and rubber. This fails after opening one file in a subdir, as make can't find a Makefile in the subdirectory. With vim-latex 20060325-4.1 this worked flawlessly. I've tracked the problem down to an apparent bug in the .latexmain searching & sourcing code in texproject.vim. I propose the attached trivial patch against vim-latex-1.5-20090804-r1058, which fixes the issue for me. Cheers, Alex PS: My apologies to the maintainers for receiving this twice. I didn't think of the mailing list before contacting them directly. |
From: Erik H. <eri...@gm...> - 2009-08-07 10:43:44
|
Hi, I'm trying to use Latex Suite. However, when I try to compile with <leader>ll , I get this output: Error detected while processing function Tex_RunLaTeX: line 7: E121: Undefined variable: s:target E15: Invalid expression: s:target line 10: E121: Undefined variable: s:target E116: Invalid arguments for function Tex_Debug line 12: E121: Undefined variable: s:target E116: Invalid arguments for function Tex_GetVarValue('Tex_FormatDependency_'.s:t arget) != '' E15: Invalid expression: Tex_GetVarValue('Tex_FormatDependency_'.s:target) != '' line 21: E121: Undefined variable: dependency E116: Invalid arguments for function Tex_Debug line 25: E121: Undefined variable: dependency E116: Invalid arguments for function Tex_Strntok(dependency, ',', i) != '' E15: Invalid expression: Tex_Strntok(dependency, ',', i) != '' line 51: E121: Undefined variable: initTarget E15: Invalid expression: initTarget The possible solutions I found at <http://ubuntuforums.org/showthread.php?t=577217> don't apply since this is a Windows PC. runtimepath is "~/vimfiles,C:\Programme\Vim/vimfiles,C:\Programme\vim\vim72,C:\Programmme\Vim/vimfiles/after,~/vimfiles/after,D:\vimfiles (D:\vimfiles being the directory where latex suite is installed) My .vimrc is here: http://github.com/ehahn/dotfiles/blob/e31bfc154b5f7e64b4b55862e4bb9c59b2052550/.vimrc I hope you can help me with this problem. -Erik |
From: Till M. <ope...@ti...> - 2009-07-31 08:49:31
|
On Fri July 17 2009, Daniele Avitabile wrote: > I am using MacVim and LaTeX suite. I noticed the following bad > behaviours: > Have you noticed similar behaviour? If you provide a minimal example latex file/project that triggers the bad beheaviour, I might look into it. Please also always mention which version of vim-latex you use. Regards Till |
From: Andreas W. <awi...@ze...> - 2009-07-19 22:12:44
|
Hi, at least for the second point I encountered the same behaviour (also LaTeX suite and MacVim) and didn't find a solution yet. But I would love to hear a fix for this issue, if anyone knows about it. Andreas On Jul. 17, 2009, at 9:38 , Daniele Avitabile wrote: > Hi all, > I am using MacVim and LaTeX suite. I noticed the following bad > behaviours: > > 1) When using F9 to complete \cite{} commands, the completion goes > fine, but when using F9 on \eqref or \ref commands, the completion > doesn't quite work: I can see the usual _OUTLINE_ window, displaying > approriate choices for the reference labels, but when I press Enter I > am prompted back to the document, and the command is not completed. It > actually gets a closing bracket say \eqref{} but it doesn't seem to > have selected my choice. > > 2) When the latex compiler gives an error, a proper Quickfix list > appears, showing the right error. When I press Enter, the correct > behaviour should be to bring me back to the document, with the cursor > next to my error. In my case, I am stuck to the Quickfix window, and I > am unable to go back to the document, unless I type :q. This closes > the Quickfix window, but doesn't bring my cursor on the error. > > Have you noticed similar behaviour? > > Best. > > Daniele > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited > time, > vendors submitting new applications to BlackBerry App World(TM) will > have > the opportunity to enter the BlackBerry Developer Challenge. See > full prize > details at: http://p.sf.net/sfu/Challenge_______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |
From: Daniele A. <d.a...@gm...> - 2009-07-17 07:38:12
|
Hi all, I am using MacVim and LaTeX suite. I noticed the following bad behaviours: 1) When using F9 to complete \cite{} commands, the completion goes fine, but when using F9 on \eqref or \ref commands, the completion doesn't quite work: I can see the usual _OUTLINE_ window, displaying approriate choices for the reference labels, but when I press Enter I am prompted back to the document, and the command is not completed. It actually gets a closing bracket say \eqref{} but it doesn't seem to have selected my choice. 2) When the latex compiler gives an error, a proper Quickfix list appears, showing the right error. When I press Enter, the correct behaviour should be to bring me back to the document, with the cursor next to my error. In my case, I am stuck to the Quickfix window, and I am unable to go back to the document, unless I type :q. This closes the Quickfix window, but doesn't bring my cursor on the error. Have you noticed similar behaviour? Best. Daniele |
From: Tine S. <tin...@st...> - 2009-07-16 15:44:16
|
Hi, I'm using the latex-suite on windows. I don't have vim installed in a directory with spaces. I have installed python and ref seemd to work..I get the label in the other window, but when I try to select one i get this: Error detected while processing function Tex_FinishOutlineCompletion..Tex_CompleteWord: line 1: line 4: line 7: E21: Cannot make changes, 'modifiable' is off I don't know how to solve this. \cite doesnt' even works, I get: No bibkey, label or word beggining with "" Can someone help me with this problems.. Thank you Regards, Tine Šukljan |
From: Bodo G. <ma...@bo...> - 2009-07-06 18:56:42
|
Hi, I wanted to map some unicode-chars to the representing latex code, but it doesn't seem to work. All other 'normal' mappings work but something like call IMAP('…', '\dots', 'tex') just doesn't show any result. Can you tell me if it is possible at all? I am using latexsuite-1.5.20060325 from Gentoo. tnx Bodo |