vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project

[Vim-latex-devel] problem with periods and commas

[Robert B. <rb...@ne...>]

I have been having a bizarre problem while editing LaTeX files: the cursor 
does not move after entering a '.' or a ','. This is with
Vim 7.0.122
teTeX 3.0-23
latexSuite20060325
on Debian/testing and the 2.6.17 Linux kernel.

I fixed it by commenting some lines in the main.vim file as indicated in 
this diff:
73c73
< "	call IMAP (g:Tex_Leader.'.', '\cdot', "tex")
---
> 	call IMAP (g:Tex_Leader.'.', '\cdot', "tex")
84c84
< "	call IMAP (g:Tex_Leader.',', '\nonumber', "tex")
---
> 	call IMAP (g:Tex_Leader.',', '\nonumber', "tex")
153c153
< "	call s:ProtectLetters(32, 127)
---
> 	call s:ProtectLetters(32, 127)
857,861c857,861
< "augroup LatexSuite
< "	au LatexSuite User LatexSuiteFileType 
< "		\ call Tex_Debug('main.vim: Catching LatexSuiteFileType event', 'main') | 
< "		\ call <SID>SetTeXOptions()
< "augroup END
---
> augroup LatexSuite
> 	au LatexSuite User LatexSuiteFileType
> 		\ call Tex_Debug('main.vim: Catching LatexSuiteFileType event', 'main') |
> 		\ call <SID>SetTeXOptions()
> augroup END

I haven't noticed anyone else with this problem so I suspect that it is a 
result of peculiarity with my machine. Is there a better fix?

----
Robert Burrows, PhD
New England Biometrics
rb...@ne...

Re: [Vim-latex-devel] WinManager and F9 Command Completion

[coupled c. <cou...@gm...>]

Hi Guido,

My problem was that I had a tex.vim file, which was loading WinManager
everytime I opened a tex file. What I did , was just removing that
command from the vim.tex file. I am not a Vim expert, but I guess to
remove a plugin, you just remove it from $Vimhome/Vimfiles/ftplugin.

Hope this helps.

Cheers,

Hooman

On 10/23/06, Guido Milanese <gui...@un...> wrote:
> On Saturday 21 October 2006 08:23, coupled cores wrote:
> > Dear All,
> >
> > After days of having lots of problems with command completion in
> > directories which their folders have spaces in their names, I
> > discovered that the cause of the problem is the WinManager module. I
> > can't figure out whether bufexplorer causes it, or the WinManager, but
> > when I removed WinManger,
>
> very interesting, thank you for sharing this with us. Can you kindly telle me
> how to remove the WinManager module?
>
> Thanks again!
> g
>
> --
> Guido Milanese
> Vocal Ensemble Ars Antiqua, Genova (Genoa), Italy
> http://www.arsantiqua.org
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] WinManager and F9 Command Completion

[Guido M. <gui...@un...>]

On Saturday 21 October 2006 08:23, coupled cores wrote:
> Dear All,
>
> After days of having lots of problems with command completion in
> directories which their folders have spaces in their names, I
> discovered that the cause of the problem is the WinManager module. I
> can't figure out whether bufexplorer causes it, or the WinManager, but
> when I removed WinManger, 

very interesting, thank you for sharing this with us. Can you kindly telle me 
how to remove the WinManager module?

Thanks again!
g

-- 
Guido Milanese
Vocal Ensemble Ars Antiqua, Genova (Genoa), Italy
http://www.arsantiqua.org

[Vim-latex-devel] WinManager and F9 Command Completion

[coupled c. <cou...@gm...>]

Dear All,

After days of having lots of problems with command completion in
directories which their folders have spaces in their names, I
discovered that the cause of the problem is the WinManager module. I
can't figure out whether bufexplorer causes it, or the WinManager, but
when I removed WinManger, magically all the problems are solved and I
can do F9 in any directory on any tex file.

Just wanted to let everybody know.

Cheers,

Hooman

[Vim-latex-devel] Run \ll in silent mode

[coupled c. <cou...@gm...>]

Hi,

When I compile a file using \ll, for each run of latex a command
window pops up and then closes. Is there a way to run latex silently
and suppress those command windows from poppin up?

Regards,

Hooman

[Vim-latex-devel] F9 completion again

[coupled c. <cou...@gm...>]

Regarding the second scenario that I sent in my previous email, I
found what was causing it. It was basically the fact that the file
simplication.tex wasn't in that directory.

Now, I am sure that what causes the problem is the spaces in the
directory names. I had this problem once before, but I thought that
after I installed python the problem was resolved. Apparently lack of
python wasn't the problem. Now, I have all those but still F9 can't
generate the outline when the file resides in a directory which has
spaces in its name.

Any ideas that can solve this?? Could it be because of grep? I have
this line in my _vimrc file (according to installation guide)

set grepprg=grep\ -nH\ $*

I appreciate any help or comment in this regard.

Best,
Hooman

[Vim-latex-devel] F9 completion again

[coupled c. <cou...@gm...>]

Hello,

I know that the F9 issue has been discussed couple of times in the
list, but unfortunately nobody has given a decisive reply to resolve
the problem.

I had to re-format my computer and I lost all my settings. Now, I have
installed gVim, Vim-LaTeX, python 2.5 and grep 2.51a on my Win XP
machine. I can run both grep and python from command prompt and grep
supports -H switch.

When I try to insert a \ref using F9 there are two different scenarios:

1. The tex file is multi-file project in a folder that has spaces in
its name: In this case pressing F9 gives me the following results in
the ___OUTLINE___ window:

Traceback (most recent call last):
  File "E:\Vim\vimfiles\ftplugin\latex-suite\outline.py", line 183, in <module>
    print main(sys.argv[1], prefix)
  File "E:\Vim\vimfiles\ftplugin\latex-suite\outline.py", line 170, in main
    contents = getFileContents(root, ext)
  File "E:\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: 'Documents'

2. When I have run the same multi-file project from a location which
doesn't have any spaces in its name, I still get an error message and
the __OUTLINE__ can't be generated. The messages are:

Traceback (most recent call last):
  File "E:\Vim\vimfiles\ftplugin\latex-suite\outline.py", line 183, in <module>
    print main(sys.argv[1], prefix)
  File "E:\Vim\vimfiles\ftplugin\latex-suite\outline.py", line 170, in main
    contents = getFileContents(root, ext)
  File "E:\Vim\vimfiles\ftplugin\latex-suite\outline.py", line 27, in
getFileContents
    contents = re.sub(pat, lambda input: getFileContents(input, ext), contents)
  File "E:\Python25\lib\re.py", line 142, in sub
    return _compile(pattern, 0).sub(repl, string, count)
  File "E:\Vim\vimfiles\ftplugin\latex-suite\outline.py", line 27, in <lambda>
    contents = re.sub(pat, lambda input: getFileContents(input, ext), contents)
  File "E:\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:
'appendices/simplification/simplification.tex'

It seems that the error is caused by the outline.py script. I don't
know any python, so I can't understand what that script has inside.
Python experts and developers, please help. I use \ref and \cite very
often in my documents and this F9 is really useful.

Best Regards,

Hooman

[Vim-latex-devel] vim + vim-latex (running on an xterm): Garbage after compiling

[<jor...@ya...>]

Hi,
This is not a serious issue, but given the frequency with which it
occurs (after every \ll), it is at least annoying.
It might be a problem not related to vim-latex itself, as I think this
didn't happen on vim 6.4 (Now I run vim 7.0.91 on Gentoo/Linux). 
The problem is that after every compile cycle, some of the bibtex
messages remain in the lower area of the screen (remember vim runs on
an xterm window). I have then to hit CTRL-L to clear and redraw the
screen. The problem seems to be tied up to bibtex, as I can't reproduce
it after removing the lines \bibliographystyle{...} and
\bibligraphy{..} from the tex file
Anybody knows how can I fix this? I tried using the default vimrc and I
still get the same behaviour.
Another annoying thing is that if I use the \lv commands to open xdvi,
I also get garbage on the xterm screen (I think, but I'm not sure, that
they come from stderr as they always relate to some warning or error
message). The workaround I found for this is to launch xdvi not from
within vim, but as a standalone application and leave it open all the
time.
Thanks for any help, suggestions (please don't tell me to switch to
gvim), or directions to investigate...

jorges



	
	
		
______________________________________________ 
LLama Gratis a cualquier PC del Mundo. 
Llamadas a fijos y móviles desde 1 céntimo por minuto. 
http://es.voice.yahoo.com

[Vim-latex-devel] Problems with latex-suite

[Michal K. <mic...@mo...>]

Hello!

Recently i tried to use latex-suite as an LaTeX editor. It work quite ok, but
have at last few problems:

 * on list there was mentioned problem with <F5> shortcut, after using it i
also get strange results like this (for eqnarray and other default):

\begin{eqnarray*}
"
\end{eqnarray*}<++>

or (for ie. tabular):

<+position+>]{<+format+>}
``
\end{tabular}<++>begin{tabular}[X

On other hand three letter sequences work as they should...

 * mentioned problem about \usepackage completion:

<++>]{amsmath}``usepackage[X

 * i have problems with View command, but only if file is called from Thunar
file manager, it uses gvim.desktop file to open file. There "gvim -f" command
is used and somehow this combination prevents View from working. If i use
gvim file_path from command line this feature works ok.

On other hand there is one additional functionality that i miss from
latex-suite. Automatic completion of environment, after manually inserting
\begin{something} it would be very nice to get automatically \end{something}.
If this is already present i would be extremely grateful for hints about it.

-- 
Michal Kurgan

[Vim-latex-devel] syntax highlighting for xy-pic

[Sebastian M. <seb...@un...>]

Hi all

im texing a lot with diagrams made in xy-pic. a typical diagram looks
like this:

\xymatrix{
X \ar@{.>}[r]^{\gamma} \ar[d]_{Ff(v)} & A \ar[d]^v      \\
Y \ar@{.>}[r]^{\kappa}		      & B
}

Thus in \xymatrix{} i type math formulas, but i dont have "$" anywhere.

Now, all the "_", "^" and "\ar@" are not highlighted correctly.

How can i repair the syntax highlighting?

thanks in advance,

Sebastian.

Re: [Vim-latex-devel] Alt key based mapping (eg. Alt-I) don't workunder "OS X"

[Yuan Qi <gma...@sp...>]

Vim's help file states that vim takes over keyboard mapping 
from the OS in order to increase the number of possible mappings.
In particular, the alt key mappings are mentioned. Does this apply 
for OS X? Is there an option similar to "winaltkey" for OS X?

Re: [Vim-latex-devel] how to configure the View rule?

[Yuan Qi <gma...@sp...>]

I added this to ~/.vimrc and both problems are
gone:

let g:Tex_ViewRuleComplete_pdf = 'open $*.pdf'

The problem seems to lie in the compiler.vim file.
In particular, the following lines:

		if strlen(s:viewer)
			let s:viewer = '-a '.s:viewer
		endif
		let execString = 'open '.s:viewer.' $*.'.s:target

Should be changed to:

		let execString = 'open $*.'.s:target

[Vim-latex-devel] Alt key based mapping (eg. Alt-I) don't work under "OS X"

[Yuan Qi <gma...@sp...>]

Specifically, under Mac OS X 10.4.7

Under OS X, alt/option key is used to enter diacritics. 
While there is an option under Terminal.app to use 
option as meta key, this is not available under 
CarbonVim.

Re: [Vim-latex-devel] how to configure the View rule?

[Yuan Qi <gma...@sp...>]

Christian Ebert <blacktrash <at> gmx.net> writes:

> 
> * Yuan Qi on Wednesday, September 20, 2006 at 23:15:48 +0000:
> >> Turns out this is a bug in latex-suite specific to the Mac. I fixed this
> >> (hopefully) in SVN, but I cannot be sure since I do not have access to
> >> a Mac. In the meanwhile, a simple way to get around this is to put
> >> something like:
> >> 
> >> let Tex_ViewRule_pdf = '/path/to/acrobat/reader $*.pdf'
> >> 
> >> in your ~/vimfiles/ftplugin/tex.vim or .vimrc (I do not know how these
> >> files are named, but you hopefully get the idea).
> >> 
> >> BTW, even with this warning, viewing should still have worked.
> > 
> > I have a related problem with the View function on OS X 10.4.7
> > 
> > With the default value of Tex_ViewRule_format (empty string),
> > \lv won't work at all! Changing it to 'open' doesn't help either. 
> > I have to change the string to 'open -a Preview' or "open $.pdf" 
>                                                        ^^^^^^^^^^
> I think this should be 'open $*.pdf' or 'open $1.pdf'.

I meant 'open $*.pdf'. However, this option stopped working after I
did rebuilt the LaunchServices database (I am guessing this is what
cause it to stop working):

/System/Library/Frameworks/ApplicationServices.framework/\
Frameworks/LaunchServices.framework/Support/lsregister \
-kill -r -domain local -domain system -domain user

> 
> > to make it work.
> > 
> > Even then, \lv will only work every other time (that is I have to
> > type \lv twice to get it to work).

This bug is always present regardless of what I tried.

> 
> I can't reproduce this on MacOS 10.3.9. Just 'open' works, even
> though I use the little "launch" utility that you might get via
> fink most of the time.

There are large differences between Tiger and Panther when it comes
to LaunchServices.

> 
> Perhaps it helps if you do "Finder->File->Show Info" on a .pdf,
> and then specify Preview under "Open with" and "Use this
> application to open all documents like this" explicitly?

I tried changing 'Open with' to some other application and then back, 
but that doesn't work.

> 
> c

[Vim-latex-devel] [patch] fix comment in texrc

[Christian E. <bla...@gm...>]

Hi,

This small patch fixes a typo and an 8bit char in a comment in
texrc:

#v+
--- ftplugin/latex-suite/texrc.orig	2006-09-21 08:49:10.000000000 +0200
+++ ftplugin/latex-suite/texrc	2006-09-21 08:49:38.000000000 +0200
@@ -195,7 +195,7 @@
 "
 " this is the list of patterns which will be ignored from the compiler output.
 " This is a handy way of specifying which warnings/errors to ignore. This is a
-" list of patterns seperated by '¡'
+" list of patterns separated by '\n'
 TexLet g:Tex_IgnoredWarnings =
 	\'Underfull'."\n".
 	\'Overfull'."\n".
#v-

c
-- 
_B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html>

Re: [Vim-latex-devel] how to configure the View rule?

[Christian E. <bla...@gm...>]

* Yuan Qi on Wednesday, September 20, 2006 at 23:15:48 +0000:
>> Turns out this is a bug in latex-suite specific to the Mac. I fixed this
>> (hopefully) in SVN, but I cannot be sure since I do not have access to
>> a Mac. In the meanwhile, a simple way to get around this is to put
>> something like:
>> 
>> let Tex_ViewRule_pdf = '/path/to/acrobat/reader $*.pdf'
>> 
>> in your ~/vimfiles/ftplugin/tex.vim or .vimrc (I do not know how these
>> files are named, but you hopefully get the idea).
>> 
>> BTW, even with this warning, viewing should still have worked.
> 
> I have a related problem with the View function on OS X 10.4.7
> 
> With the default value of Tex_ViewRule_format (empty string),
> \lv won't work at all! Changing it to 'open' doesn't help either. 
> I have to change the string to 'open -a Preview' or "open $.pdf" 
                                                       ^^^^^^^^^^
I think this should be 'open $*.pdf' or 'open $1.pdf'.

> to make it work.
> 
> Even then, \lv will only work every other time (that is I have to
> type \lv twice to get it to work).

I can't reproduce this on MacOS 10.3.9. Just 'open' works, even
though I use the little "launch" utility that you might get via
fink most of the time.

Perhaps it helps if you do "Finder->File->Show Info" on a .pdf,
and then specify Preview under "Open with" and "Use this
application to open all documents like this" explicitly?

c
-- 
_B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html>

Re: [Vim-latex-devel] how to configure the View rule?

[Yuan Qi <gma...@sp...>]

> Turns out this is a bug in latex-suite specific to the Mac. I fixed this
> (hopefully) in SVN, but I cannot be sure since I do not have access to
> a Mac. In the meanwhile, a simple way to get around this is to put
> something like:
> 
> let Tex_ViewRule_pdf = '/path/to/acrobat/reader $*.pdf'
> 
> in your ~/vimfiles/ftplugin/tex.vim or .vimrc (I do not know how these
> files are named, but you hopefully get the idea).
> 
> BTW, even with this warning, viewing should still have worked.

I have a related problem with the View function on OS X 10.4.7

With the default value of Tex_ViewRule_format (empty string),
\lv won't work at all! Changing it to 'open' doesn't help either. 
I have to change the string to 'open -a Preview' or "open $.pdf" 
to make it work.

Even then, \lv will only work every other time (that is I have to
type \lv twice to get it to work).

Re: [Vim-latex-devel] Alt key bindings not working, Alt combinations giveing accented characters

[Christian E. <bla...@gm...>]

Hi Mark,

* Mark Gesing on Saturday, September 16, 2006 at 22:22:21 -0400:
> I'm trying to use the alt commands (for example ALT+I to insert a new
> item into an enumerate or itemize). However, instead of getting a
> new /item it inserts é.

<http://vim-latex.sourceforge.net/index.php?subject=faq&title=FAQ#faq-e-acute>

> How can I fix my alt-key bindings so that they
> work properly?

<http://vim-latex.sourceforge.net/index.php?subject=faq&title=FAQ#faq-euro-symbols>

HTH

c
-- 
_B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html>

[Vim-latex-devel] Alt key bindings not working, Alt combinations giveing accented characters

[Mark G. <mag...@gm...>]

Hi, 

I'm trying to use the alt commands (for example ALT+I to insert a new
item into an enumerate or itemize). However, instead of getting a
new /item it inserts é. How can I fix my alt-key bindings so that they
work properly? I don't need the accented characters, so if the solution
blows their bindings away that's fine with me.

I am running gentoo linux, and I am using the "us" keyboard layout.

Thank you very much,

Mark.

Re: [Vim-latex-devel] <F9> Debian

[Yigal W. <yig...@gm...>]

I played with this some more - it took me a month to play with it rather
than typing :w, :v :($numberofwords)e - and realized that the automated
pasting of a reference occurs - at this point - if there are no spaces
in the label i.e. the automatic completion of the reference to fig:
structure vs. tree is:
\ref{fig:}
However the automatic reference to fig:structure-vs-tree is:
\ref{fig: structure-vs-tree}
so not worrying about python for now I can perl, sed or awk my thesis
documents into automatic reference completions.  Still some help on full
usability would be nice eventually.

On Sat, 2006-09-16 at 15:04 -0700, Yigal Weinstein wrote:

> In Debian without a patch from the package maintainer, Franz Pletz
> <fp...@fr...> , (attached is the patch) no outline is
> generated when attempting to obtain a reference through \ref{<F9>} but
> only python errors (as has been discussed on this board).  With the
> patch, however, an outline is available but it lacks the feature that
> if a return is made on the ">"  the name is inserted into the
> references instead only the type is.  
> 
> For example, assume I wanted a certain reference "fig: structure vs.
> tree" so \ref{<F9>}: 
> >      fig: structure vs. tree
> 
> Pressing return on the ">" one gets \ref{fig:} and not the desired
> \ref{fig: structure vs. tree}?
> 
> I believe the answer is an error in $VIM/addons/ftplugin/outline.py,
> unfortunately I don't speak python.
> 
> Please help me get this functionality.  I realize that as I am dealing
> with a patched outline I may be on my own but perhaps you can give me
> suggestions.

[Vim-latex-devel] <F9> Debian

[Yigal W. <yig...@gm...>]

In Debian without a patch from the package maintainer, Franz Pletz
<fp...@fr...> , (attached is the patch) no outline is
generated when attempting to obtain a reference through \ref{<F9>} but
only python errors (as has been discussed on this board).  With the
patch, however, an outline is available but it lacks the feature that if
a return is made on the ">"  the name is inserted into the references
instead only the type is.  

For example, assume I wanted a certain reference "fig: structure vs.
tree" so \ref{<F9>}: 
>      fig: structure vs. tree

Pressing return on the ">" one gets \ref{fig:} and not the desired
\ref{fig: structure vs. tree}?

I believe the answer is an error in $VIM/addons/ftplugin/outline.py,
unfortunately I don't speak python.

Please help me get this functionality.  I realize that as I am dealing
with a patched outline I may be on my own but perhaps you can give me
suggestions.

[Vim-latex-devel] \lv does not work on windows using AcroRd32

[Thomas I. <tho...@or...>]

There was an earlier post on this with the subject "Adobe Acrobat 7.0
(Full version) with Vim-LaTeX" and I would have replied to that, but
unfortunately I am new to the mailing list and I can't work out how to
reply to older posts.

Anyway the problem is indeed that: ":!start AcroRd32" causes an error,
but ":! start AcroRd32" works fine. To work around this problem I
changed line 290 of "$VIM/vimfiles/ftplugin/latex-suite/compiler.vim"
from:
"exec 'silent! !'.execString", to:
"exec 'silent! ! '.execString"

This solves the problem, however I realise this may cause other
problems and should be done properly, but for my purposes it's ok as I
only ever create and view pdfs.

Tom

[Vim-latex-devel] Automatic Insertion of Labels

[Tang H. T. M. <mh...@cs...>]

Hello List,

One of the most useful features of auctex + reftex in Emacs is that of 
automatic insertion of labels for equations, figures, theorems, ... . For 
example, if I use the macro to insert an equation in Emacs, the macro will 
automatically insert a label with an appropriate label number, such as 
\label{eqn:14}. I think this is extremely useful for equations, since a lot 
of paper has a lot of equations, and managing the creation of labels by hand 
is quite tedious. Is there a way to get this feature with LatexSuite ? Thanks 
in advance.

Minh

Re: [Vim-latex-devel] Tex_CompileMultipleTimes fails

[Bill W. <bil...@ya...>]

Hello,
   I fixed the problem!  I did not have Python installed.  I installed Python24 and voila, no more problems...

--Bill

 			
---------------------------------
Sneak preview the  all-new Yahoo.com. It's not radically different. Just radically better. 

[Vim-latex-devel] Tex_CompileMultipleTimes fails

[Bill W. <bil...@ya...>]

Hello!
  I upgraded to Vim 7 over the summer.  This is the first time I am using bibtex in Vim 7.   I followed the instructions posted on vim-latex-devel for identifying the problem.  It seems that there are errors in the compilation

In the debug output I have this:

Tex_CompileMultipleTimes: errors = [
  1: (paper.aux)]

and later...

Tex_RunLaTeX: errlist = [
  1: (paper.aux)
  2: ]

How do I find out what that error is, or why it's happening?

Thanks!

--Bill

 		
---------------------------------
Get your email and more, right on the  new Yahoo.com