vim-latex-devel Mailing List for Vim-Latex (Page 39)
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: Simon Q. <sim...@gm...> - 2010-02-02 11:29:20
|
I don't experience any errors anymore with this patch applied. Thanks a lot, Simon On 2010/02/01 16:51,Till Maas <ope...@ti...> wrote: > On Mon, Feb 01, 2010 at 01:34:12PM +0100, Simon Quittek wrote: > >> Similar to the last posting about blanks in the directory this time, >> \ref does produce an error. >> If I am not mistaken this bug was accidentally introduced with one >> of the last changes. > > Yes, can you please test this patch? > http://till.fedorapeople.org/tmp/vim-latex-outline.py-proper-filename-escaping.patch > > Btw. does someone recommend some automatic test environment for vim > scripts, like there are unit tests for object oriented languages? > >> Use :messages to see the cause and please find a tarball holding a >> minimal working example in the attachments. > > Thank you, this was very helpful. > > Regards > Till > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > > > ------------------------------------------------------------------------ > > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel |
From: Till M. <ope...@ti...> - 2010-02-01 16:33:57
|
On Sun, Jan 31, 2010 at 07:47:11PM -0500, Srinath Avadhanula wrote: > What about the following? I basically search for a pattern > > "not backslash" + (even number of backslashes) + % + rest > > Probably, removing \verb|| etc is not worth the trouble till users > face a problem... Thanks, these look good. I am not sure about how much it is worth to handle special cases, but as soon as someone would want to write a latex document about latex, he would run into problems, I guess. Regards Till |
From: Till M. <ope...@ti...> - 2010-02-01 16:28:22
|
On Mon, Feb 01, 2010 at 09:17:46AM +0000, Jan Larres wrote: > I don't know about the performance, but what about using synIDattr() for > that? It already does all the work to figure out what is a comment and > what isn't. Thanks, using the existing syntax knowledge sounds like a good idea. Regards Till |
From: Till M. <ope...@ti...> - 2010-02-01 15:51:53
|
On Mon, Feb 01, 2010 at 01:34:12PM +0100, Simon Quittek wrote: > Similar to the last posting about blanks in the directory this time, > \ref does produce an error. > If I am not mistaken this bug was accidentally introduced with one > of the last changes. Yes, can you please test this patch? http://till.fedorapeople.org/tmp/vim-latex-outline.py-proper-filename-escaping.patch Btw. does someone recommend some automatic test environment for vim scripts, like there are unit tests for object oriented languages? > Use :messages to see the cause and please find a tarball holding a > minimal working example in the attachments. Thank you, this was very helpful. Regards Till |
From: Simon Q. <sim...@gm...> - 2010-02-01 13:01:17
|
Hello Mailing List! Similar to the last posting about blanks in the directory this time, \ref does produce an error. If I am not mistaken this bug was accidentally introduced with one of the last changes. Use :messages to see the cause and please find a tarball holding a minimal working example in the attachments. Thanks in advance Simon |
From: Jan L. <ja...@ma...> - 2010-02-01 09:18:24
|
Till Maas <ope...@ti...>: > On Sun, Jan 31, 2010 at 07:03:05AM +0000, Jan Larres wrote: >> I recently found another small bug with the BibTeX completion. If there >> is a commented out \bibliography{} command before the actual one, >> latex-suite erroneously tries to use the commented out one. In my case >> this led to completion not working because the commented out command >> referred to a non-existing file. > > Yes, I can reproduce this. Does someone maybe new a good way to always > strip "%"-style comments from a line in a tex file? Currently there are > afaics several different approaches with regexes in vim-latex, therefore > I would like to have one way I can use everywhere. It is not just > everything since a %-sign to the end of the line, as you can see in > these examples: > > %comment > this is \%not a comment > this is \\%again a comment > this is \\\%not a comment anymore I don't know about the performance, but what about using synIDattr() for that? It already does all the work to figure out what is a comment and what isn't. Cheers, Jan -- OpenPGP Key-ID: 00A0FD5F |
From: Srinath A. <sri...@gm...> - 2010-02-01 00:55:00
|
Hi Till, What about the following? I basically search for a pattern "not backslash" + (even number of backslashes) + % + rest Probably, removing \verb|| etc is not worth the trouble till users face a problem... Srinath ============ vim solution ==================== " StripComments: {{{ " Description: function! StripComments(str) return substitute(a:str, '\\\@<!\(\\\\\)*\zs%.*', '', 'g') endfunction " }}} echo StripComments('This is a %comment') echo StripComments('This is not a \%comment') echo StripComments('This is a \\%comment') echo StripComments('This is not a \\\%comment') echo StripComments('This is a \\\\%comment') =========== python solution ================= import re re_comment = re.compile(r'(?<!\\)((\\\\)*)%.*') def strip_comments(instr): print re.sub(re_comment, r'\1', instr) strip_comments(r'This is a %comment') strip_comments(r'This is not a \%comment') strip_comments(r'This is a \\%comment') strip_comments(r'This is not a \\\%comment') strip_comments(r'This is \a %comment') ======================================= On Sun, Jan 31, 2010 at 11:23 AM, Till Maas <ope...@ti...> wrote: > On Sun, Jan 31, 2010 at 07:03:05AM +0000, Jan Larres wrote: > >> I recently found another small bug with the BibTeX completion. If there >> is a commented out \bibliography{} command before the actual one, >> latex-suite erroneously tries to use the commented out one. In my case >> this led to completion not working because the commented out command >> referred to a non-existing file. >> >> Since there was a BibTeX example posted recently, you can just reuse >> that and insert a line like >> >> %\bibliography{doesnotexist} >> >> before the existing \bibliography{} command. > > Yes, I can reproduce this. Does someone maybe new a good way to always > strip "%"-style comments from a line in a tex file? Currently there are > afaics several different approaches with regexes in vim-latex, therefore > I would like to have one way I can use everywhere. It is not just > everything since a %-sign to the end of the line, as you can see in > these examples: > > %comment > this is \%not a comment > this is \\%again a comment > this is \\\%not a comment anymore > > Also I am not sure about verbatim-environments and the \verb command, > but maybe there will always be some cases, where it does not work. > > Regards > Till > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Vim-latex-devel mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel > > |
From: Till M. <ope...@ti...> - 2010-01-31 16:23:48
|
On Sun, Jan 31, 2010 at 07:03:05AM +0000, Jan Larres wrote: > I recently found another small bug with the BibTeX completion. If there > is a commented out \bibliography{} command before the actual one, > latex-suite erroneously tries to use the commented out one. In my case > this led to completion not working because the commented out command > referred to a non-existing file. > > Since there was a BibTeX example posted recently, you can just reuse > that and insert a line like > > %\bibliography{doesnotexist} > > before the existing \bibliography{} command. Yes, I can reproduce this. Does someone maybe new a good way to always strip "%"-style comments from a line in a tex file? Currently there are afaics several different approaches with regexes in vim-latex, therefore I would like to have one way I can use everywhere. It is not just everything since a %-sign to the end of the line, as you can see in these examples: %comment this is \%not a comment this is \\%again a comment this is \\\%not a comment anymore Also I am not sure about verbatim-environments and the \verb command, but maybe there will always be some cases, where it does not work. Regards Till |
From: Jan L. <ja...@ma...> - 2010-01-31 07:30:24
|
Hi, I recently found another small bug with the BibTeX completion. If there is a commented out \bibliography{} command before the actual one, latex-suite erroneously tries to use the commented out one. In my case this led to completion not working because the commented out command referred to a non-existing file. Since there was a BibTeX example posted recently, you can just reuse that and insert a line like %\bibliography{doesnotexist} before the existing \bibliography{} command. Cheers, Jan -- OpenPGP Key-ID: 00A0FD5F |
From: SourceForge.net <no...@so...> - 2010-01-29 13:57:22
|
Patches item #2860944, was opened at 2009-09-17 22:50 Message generated for change (Settings changed) made by tmaas You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=466458&aid=2860944&group_id=52322 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Accepted Priority: 5 Private: No Submitted By: johfel (johfel) Assigned to: Nobody/Anonymous (nobody) Summary: Preserve primary paste buffer Initial Comment: Description: Primary paste buffer should not be overwritten with the contents of the file which the .latexmain file corresponds to. Author: Johann Felix Soden <jo...@gm...> Bug: http://sourceforge.net/tracker/index.php?func=detail&aid=1103347&group_id=52322&atid=466456 Bug-Debian: http://bugs.debian.org/280793 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=466458&aid=2860944&group_id=52322 |
From: Jens M. <jen...@gm...> - 2010-01-29 08:09:56
|
> > I found a little problem when viewing dvi files using \ls. You only run > > into this problem if your tex file starts with a digit. > > Please explain next time the problem you have, if you have one. > > > >From the xdvi manpage (under -sourceposition): > > "The space before filename is only needed if the filename starts with > > a digit. When the space is used, the argument needs to be encosed in > > quotes to prevent the shell from misinterpreting the space as argument > > separator." > > > > That's why I think we should change > > -sourceposition '.line('.').expand("%").' ' > > to > > -sourceposition "'.line('.').' '.expand("%").'" ' > > in ftplugin/latex-suite/compiler.vim > > I could not really parse this with my eyes, please provide a unified > diff next time. It can be created with: diff -u old_file changed_file > > Nevertheless, I expect the bug to be fixed in revision 1102. Thanks. I'll provide some diff the next time. Probably I was too much into so the problem forgetting to properly explain it. Regards, Jens |
From: Till M. <ope...@ti...> - 2010-01-28 23:52:04
|
On Sat, Jan 16, 2010 at 12:24:18PM +0100, Jens Mueller wrote: > I found a little problem when viewing dvi files using \ls. You only run > into this problem if your tex file starts with a digit. Please explain next time the problem you have, if you have one. > >From the xdvi manpage (under -sourceposition): > "The space before filename is only needed if the filename starts with > a digit. When the space is used, the argument needs to be encosed in > quotes to prevent the shell from misinterpreting the space as argument > separator." > > That's why I think we should change > -sourceposition '.line('.').expand("%").' ' > to > -sourceposition "'.line('.').' '.expand("%").'" ' > in ftplugin/latex-suite/compiler.vim I could not really parse this with my eyes, please provide a unified diff next time. It can be created with: diff -u old_file changed_file Nevertheless, I expect the bug to be fixed in revision 1102. Regards Till |
From: Till M. <ope...@ti...> - 2010-01-28 23:33:21
|
On Wed, Jan 27, 2010 at 11:16:19AM +0100, Richard Müller wrote: > I am using MacVim (latest version from port) with VIM-Latex (latest > version vim-latex-1.8.23-20091230-r1079) and experience a problem with > the alt key macro <Alt+I>. > In order to use the alt key macros under Mac OS X 10.6 I remapped them with > > imap <C-b> <Plug>Tex_MathBF > imap <C-c> <Plug>Tex_MathCal > imap <C-l> <Plug>Tex_LeftRight > imap <C-i> <Plug>Tex_InsertItem > > in the ~/.vimrc file. The first three macros work perfectly, but I get > strange behaviour using the last one. > Whenever I use <C-i> in for example an enumerate environment, a small > "m" appears for one second and then turns into "Tex_InsertItem". > The same strange behaviour is described in this old bug report: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=256704 > How can this be fixed? The documentation was wrong, you need to use "<Plug>Tex_InsertItemOnThisLine". Also The <Alt+I> macro was never defined, but this is fixed in revision 1101. Regards Till |
From: Till M. <ope...@ti...> - 2010-01-28 14:53:45
|
On Thu, Jan 28, 2010 at 03:00:36PM +0100, Simon Quittek wrote: > Alright, here is a tarball... > There are files in it without blanks in the path, and a directory with a > blank, as well as a link to it without blanks (which is expanded by vim, i > think...) Thank you very much, it should be fixed in Revision 1098. Regards Till |
From: Simon Q. <sim...@gm...> - 2010-01-28 14:00:50
|
Alright, here is a tarball... There are files in it without blanks in the path, and a directory with a blank, as well as a link to it without blanks (which is expanded by vim, i think...) Sry bout the fuzz... Simon On 2010/01/28 12:59,Till Maas <ope...@ti...> wrote: > On Thu, Jan 28, 2010 at 12:38:04PM +0100, Simon Quittek wrote: > >> How to reproduce: >> create a file >> ~/foo\ bla/testfile.tex >> or >> ~/foobla/test\ file.tex >> and any bibtex file with some content, which is linked in the testfile. >> >> Type \cite{<F9> and observe the bug. > >> I hope you can reproduce this error... > > Please attach the file, it makes it a lot easier to reproduce the bug, > because then I only need to save it and open it in vim. I do not use > bibtex that lot and even if I did, there is no need to duplicate work, > so that everyone needs to strip down one of his files and then maybe > also notice, that there are some small differences. > > Regards > Till |
From: Till M. <ope...@ti...> - 2010-01-28 11:59:20
|
On Thu, Jan 28, 2010 at 12:38:04PM +0100, Simon Quittek wrote: > How to reproduce: > create a file > ~/foo\ bla/testfile.tex > or > ~/foobla/test\ file.tex > and any bibtex file with some content, which is linked in the testfile. > > Type \cite{<F9> and observe the bug. > I hope you can reproduce this error... Please attach the file, it makes it a lot easier to reproduce the bug, because then I only need to save it and open it in vim. I do not use bibtex that lot and even if I did, there is no need to duplicate work, so that everyone needs to strip down one of his files and then maybe also notice, that there are some small differences. Regards Till |
From: Simon Q. <sim...@gm...> - 2010-01-28 11:38:14
|
Till, thank you for being persistent! When I created a simple file, the bug did not appear and successively I was able to encircle the cause. If anywhere in the file path or file name there is a blank space, typing \cite{<F9> results in vim jumping back to esc mode and the cursor blinking above {. How to reproduce: create a file ~/foo\ bla/testfile.tex or ~/foobla/test\ file.tex and any bibtex file with some content, which is linked in the testfile. Type \cite{<F9> and observe the bug. This bug even appears when a directory with blanks is linked: Somethink like ln -s ~/foo\ bla/ ~/blarg cd blarg/ vi testfile.tex results in the same behaviour. I hope you can reproduce this error... Simon On 2010/01/27 20:01,Till Maas <ope...@ti...> wrote: > On Wed, Jan 27, 2010 at 06:40:14PM +0100, Simon Quittek wrote: >> I got the fresh files and (after a backup using rsync to retain symlinks) >> copied them to ~/.vim/ >> Looks well, same files in same dirs, but the problem still persists. >> >> Any ideas? >> Can I provide any additional information ? > > A minimal example file, that allows to reproduce it, often helps a lot. > > Regards > Till |
From: Till M. <ope...@ti...> - 2010-01-27 19:30:13
|
On Wed, Jan 27, 2010 at 08:20:08PM +0100, Simon Quittek wrote: > Well, it's not something you can reproduce in a file, I just can explain > what happens. > It just does nothing but revert to esc-mode when typing "\cite{<F9>" with > cursor blinking above "{". > No _OUTLINE__ window opening or anything... A .tex file that is open in vim is needed to reproduce this, please provide one with just enough content to demonstrate the problem, e.g. contains a one item bibliography. Regards Till |
From: Simon Q. <sim...@gm...> - 2010-01-27 19:21:19
|
Well, it's not something you can reproduce in a file, I just can explain what happens. It just does nothing but revert to esc-mode when typing "\cite{<F9>" with cursor blinking above "{". No _OUTLINE__ window opening or anything... Cheers Simon On 2010/01/27 20:01,Till Maas <ope...@ti...> wrote: > On Wed, Jan 27, 2010 at 06:40:14PM +0100, Simon Quittek wrote: >> I got the fresh files and (after a backup using rsync to retain symlinks) >> copied them to ~/.vim/ >> Looks well, same files in same dirs, but the problem still persists. >> >> Any ideas? >> Can I provide any additional information ? > > A minimal example file, that allows to reproduce it, often helps a lot. > > Regards > Till |
From: Simon Q. <sim...@gm...> - 2010-01-27 17:40:27
|
I got the fresh files and (after a backup using rsync to retain symlinks) copied them to ~/.vim/ Looks well, same files in same dirs, but the problem still persists. Any ideas? Can I provide any additional information ? Thanks, Simon On 2010/01/27 16:57,Thomas Ibbotson <tho...@gm...> wrote: > 2010/1/27 Simon Quittek <sim...@gm...>: >> The latexsuite package seems to be an old version, is there a PPA in ubuntu >> which provides more recent versions via apt? >> >> Thank in advance! >> Simon > I don't know of a PPA version I'm afraid, but installing the latest > svn version is fairly straightforward. The following two commands run > in a terminal will install subversion on your system and then download > the latest development version of vim-latex to a folder of the same > name: > > sudo apt-get install subversion > > svn co https://vim-latex.svn.sourceforge.net/svnroot/vim-latex/trunk vim-latex > > Then copy the contents of the 'vimfiles' folder to your ~/.vim folder. > > If you still have the same problem after doing this let us know and we > can look into it. > > Thanks, > Tom |
From: Till M. <ope...@ti...> - 2010-01-27 16:43:06
|
On Wed, Jan 27, 2010 at 04:40:18PM +0100, Simon Quittek wrote: > Package: vim-latexsuite > Version: 20060325-5 > > The latexsuite package seems to be an old version, is there a PPA in ubuntu > which provides more recent versions via apt? I don't know, but it is very easy to install a new version in your home folder: http://vim-latex.sourceforge.net/index.php?subject=download&title=Download There have been several changes that might fix your issue. Regards Till |
From: Simon Q. <sim...@gm...> - 2010-01-27 15:40:31
|
Hello Mailing List! \cite completions seems not to work on my current configuration. I tried \bibliography and \begin{thebibliography}. The .bib file is provided in the same directory as the .tex file (symbolic link and actual file, both don't work). Strangely, \ref and \includegraphics completion _does_ work. I don't know if this is somehow connected to an incompatibility with python, which is installed and working, of course. I am using the following software: Package: vim Version: 2:7.2.245-2ubuntu2 Package: vim-gnome Version: 2:7.2.245-2ubuntu2 Provides: editor, gvim, vim, vim-perl, vim-python, vim-ruby, vim-tcl Package: vim-latexsuite Version: 20060325-5 The latexsuite package seems to be an old version, is there a PPA in ubuntu which provides more recent versions via apt? Thank in advance! Simon |
From: Richard M. <ric...@in...> - 2010-01-27 13:50:40
|
Hi, thx, but I dont't use vim in a terminal, I use MacVim (which is a GUI version of vim for Mac OS X). Nevertheless I followed your proposal and mapped the alt key macro <Alt+I> to <C-b>, unfortunately I still get that strange behaviour. Regard, Richard Am 1/27/10 11:25 AM, schrieb Martin Sander: > Hey, > Just in case you are using vim in a terminal: > ctrl-i is a special escape sequence that sends a tab character (at > least where I have tried). > > I suggest remapping to something different to rule that out. |
From: Richard M. <ric...@in...> - 2010-01-27 10:17:16
|
Hi, I am using MacVim (latest version from port) with VIM-Latex (latest version vim-latex-1.8.23-20091230-r1079) and experience a problem with the alt key macro <Alt+I>. In order to use the alt key macros under Mac OS X 10.6 I remapped them with imap <C-b> <Plug>Tex_MathBF imap <C-c> <Plug>Tex_MathCal imap <C-l> <Plug>Tex_LeftRight imap <C-i> <Plug>Tex_InsertItem in the ~/.vimrc file. The first three macros work perfectly, but I get strange behaviour using the last one. Whenever I use <C-i> in for example an enumerate environment, a small "m" appears for one second and then turns into "Tex_InsertItem". The same strange behaviour is described in this old bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=256704 How can this be fixed? Kind regards, Richard Mueller |
From: Till M. <ope...@ti...> - 2010-01-24 21:07:35
|
On Sat, Jan 16, 2010 at 11:17:21AM +0100, Laurent George wrote: > so the patch is adding this after line 81 of indent/tex.vim : > while lnum > 0 && getline(lnum) =~ '^\s*%' > let lnum = prevnonblank(lnum-1) > endwhile Can you please send or provide a pointer to your modified tex.vim file? > it's extracted from tex.vim by charles campbell: > " if the current line doesn't begin with a '%', use its indent > " (ie. skip over preceding comment lines) Where can this file be found? > NB: the form here : > http://vim-latex.sourceforge.net/index.php?subject=contact&title=Contactdoesn't > seems to work anymore.. (with google-chrome it doesn't works..) Thanks, I added this to my vim-latex TODO list. Regards Till |