Thread: [Vim-latex-devel] Invalid arguments for function substitute, etc
Brought to you by:
srinathava,
tmaas
From: Gregor B. <gre...@gm...> - 2006-01-31 06:33:24
|
Dear all, I have just installed the latex suite for vim, following the steps on the homepage. The help works like a charm, but the file plugin prints a lot of error messages like the one in the subject. I am using vim 6.4. Thanks for your help. Best, Gregor -- Gregor Berginc, Ph.D. Student University of Ljubljana, Faculty of CIS Trzaska 25, SI-1001 Ljubljana, Slovenia tel: +386 1 4776630, fax: +386 1 4264647 www: http://vicos.fri.uni-lj.si/gregor |
From: Srinath A. <sri...@gm...> - 2006-01-31 18:14:20
|
Hi, Unfortunately, I will need more information to help you because I cannot reproduce this. At the very least, I would like to know which file and line number is causing this error. This information is provided when vim gives the error messages. To properly capture the errors, do something like this 1. open a tex file. You are going to see some errors. 2. issue the following command: :redir @a | messages | redir END 3. Open a new empty buffer and paste the contents of register @a. (use "ap) This file should hopefully elaborate on where the error occured etc. If you can email that to me, I should be able to help you further. Srinath On 1/30/06, Gregor Berginc <gre...@gm...> wrote: > Dear all, > > I have just installed the latex suite for vim, following the steps on > the homepage. The help works like a charm, but the file plugin prints > a lot of error messages like the one in the subject. I am using vim > 6.4. > > Thanks for your help. > > Best, > Gregor > > -- > Gregor Berginc, Ph.D. Student > University of Ljubljana, Faculty of CIS > Trzaska 25, SI-1001 Ljubljana, Slovenia > tel: +386 1 4776630, fax: +386 1 4264647 > www: http://vicos.fri.uni-lj.si/gregor > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmdlnk&kid=103432&bid#0486&dat=121642 > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > |
From: Gregor B. <gre...@gm...> - 2006-02-01 05:44:19
Attachments:
vim.err
|
Dear Srinath, Thanks for your reply. > 1. open a tex file. You are going to see some errors. > 2. issue the following command: > :redir @a | messages | redir END > 3. Open a new empty buffer and paste the contents of register @a. (use "a= p) I attached the file, produced by the above procedure. Hopefully, it will help you see what the problem might be. Best, Gregor -- Gregor Berginc, Ph.D. Student University of Ljubljana, Faculty of CIS Trzaska 25, SI-1001 Ljubljana, Slovenia tel: +386 1 4776630, fax: +386 1 4264647 www: http://vicos.fri.uni-lj.si/gregor |
From: Srinath A. <sri...@gm...> - 2006-02-01 09:13:00
|
On 1/31/06, Gregor Berginc <gre...@gm...> wrote: > Dear Srinath, > > I attached the file, produced by the above procedure. Hopefully, it > will help you see what the problem might be. > Interesting... Can you do a quick check... Run the command :echo substitute("12a\nb\<CR>c d", '\([^[:alnum:]]\)', '\=3D"_".char2nr(submatch(1))."_"', 'g') and see if you get any errors. You should get the string: 12a_10_b_13_c_32_d If this is not causing errors, it might be some tricky i18n issue... If this is causing errors, it might be that vim is not compiled with expression support or something similar. Srinath |
From: Gregor B. <gre...@gm...> - 2006-02-01 09:42:47
|
> Interesting... Can you do a quick check... Run the command > > :echo substitute("12a\nb\<CR>c d", '\([^[:alnum:]]\)', > '\=3D"_".char2nr(submatch(1))."_"', 'g') > > and see if you get any errors. You should get the string: > > 12a_10_b_13_c_32_d I get this string. I looked in the IMAP function and found out what the problem is. In file plugin/imaps.vim, line 181 you start a command: =09exe 'inoremap <silent>' =09=09=09=09\ escape(lastLHSChar, '|') =09=09=09=09\ '<C-r>=3D<SID>LookupCharacter("' . =09=09=09=09\ escape(lastLHSChar, '\|"') . =09=09=09=09\ '")<CR>' The problem is that my vim does not "understand" this as one command. If I join this lines and remove back-slashes, the IMAP executes correctly. I also get all the menus in gvim. The only problem is that many other files contain such commands. Do you have any idea why multi-line commands causes problems to my vim? Gregor > If this is not causing errors, it might be some tricky i18n issue... > If this is causing errors, it might be that vim is not compiled with > expression support or something similar. |
From: Gregor B. <gre...@gm...> - 2006-02-01 10:02:17
|
> many other files contain such commands. Do you have any idea why > multi-line commands causes problems to my vim? The worst thing is that if I copy the IMAP function in my .gvimrc it WORKS?! No problem with back-slashes... But, as soon as I put the IMAP function in my ~/.vim/plugin/ directory I get the same errors. Any clues? Gregor |
From: Gregor B. <gre...@gm...> - 2006-02-01 18:29:15
|
Problem solved. Since I did not have .vimrc in my home, Vi compatible mode was used during plugin sourcing (.gvimrc is consulted much later than plugins). A simple 'touch ~/.vimrc' did the job. Once again, thanks for yor help. Best, Gregor On 2/1/06, Gregor Berginc <gre...@gm...> wrote: > > many other files contain such commands. Do you have any idea why > > multi-line commands causes problems to my vim? > > The worst thing is that if I copy the IMAP function in my .gvimrc it > WORKS?! No problem with back-slashes... But, as soon as I put the IMAP > function in my ~/.vim/plugin/ directory I get the same errors. Any > clues? > > Gregor > -- Gregor Berginc, Ph.D. Student University of Ljubljana, Faculty of CIS Trzaska 25, SI-1001 Ljubljana, Slovenia tel: +386 1 4776630, fax: +386 1 4264647 www: http://vicos.fri.uni-lj.si/gregor |
From: Srinath A. <sri...@gm...> - 2006-02-01 23:32:05
|
Excellent! On 2/1/06, Gregor Berginc <gre...@gm...> wrote: > Problem solved. > > Since I did not have .vimrc in my home, Vi compatible mode was used > during plugin sourcing (.gvimrc is consulted much later than plugins). > > A simple 'touch ~/.vimrc' did the job. > I had forgotten the mandatory set cpo&vim at the beginning of plugin/imaps.vim. This reminds me to check all the files in the distribution fo this. Srinath |