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

[Vim-latex-devel] Does vim-latex show a general problem of OS?

[Heiko <hei...@vo...>]

Dear list,

vim and LaTeX are genius inventions not only because of their great 
functionality, but also because of their splendid documentation. It is like a 
great forest where it is *not* possible to hide any non-documented eggs. 
What about the latex-vim suite?  :-|  

It is said that the suite runs with vim6+. Obviously it is meant vim6.x, not 
version 7.x. I did *exactly* what is said in the installation instructions on 
different machines -- with vim7.0. Exactly with no exception. Nothing 
happens. 

I  know and I appreciate it very much that the suite is work done by free 
will. Indeed! And that the members of this list help by their free will. That 
is great, but it does not solve IMHO the general problem. It is clear that a 
software has its development stage. But if something is called stable, it 
*must* have a good installation instruction (more important than a user 
manual). Otherwise it IS in development. 

Especially in this case if the software  is aimed to *help* users. Which 
users? Those who are lucky to have requirement no. 6.1.1-2 (and not 6.1.1-2.1 
where the usage *sometimes* fails)? Sureley not those who celebrate Easter 
again, searching for the non documented eggs hidden *between* the lines of 
the instructions, meaning perhaps that 7.0 is not 6.+ but obviously 6.++. 
And -- if you really think, think right -- we *did* say 6.+ ONLY, nothing 
more     ;-). 

And: *See those lucky people. Can't you imagine, that you DID a mistake? They 
can run it, so everyone *could* run it, if one only uses its brain -- Yes, 
you have to think, but think right.  Find out WHAT is meant, not what is NOT 
meant or what we mean that it should be clear that it IS not meant.*  And if 
you do not succeed read the FAQ (Feigned Annoying Questions -- which have 
never been asked) ;-)

Please apologize for coming a bit too steep out of the hedge. But OpenSource 
is by a too great amount of people still  regarded as *software for 
specialists* -- and that shows IMHO that there is something wrong; but not 
about OpenSource! Nobody cares about the free willing work done by the user 
(and it *is* sureley not important). Software *cannot* be free of bugs. That 
is clear.But a suite which sometimes works and sometimes with not hints what 
could be wrong is use-less (in the exact meaning). 

Best regards
Heiko Schroeder
  
-- 
Heiko Schroeder
Praha, Ceska Republica
http://home.foni.net/~heikos
http://www.od.shuttle.de/evb-1

Re: [Vim-latex-devel] newbie question

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

On 1. Alexandre I am using Feisty but I was using Edgy a couple of weeks
ago and the filetype extension "tex" seamed to work most of the time.
Do you have these in your ~/.vimrc file,

filetype plugin on
filetype indent on
syntax enable
 

Re: [Vim-latex-devel] newbie question

[Vaidotas Z. <ze...@gm...>]

On 3/20/07, Alexandre Rosas <fre...@gm...> wrote:
> Thanks, Vaidotas. Your tip about the filetype helped me to
> find out a solution. The problem was the default type for
> .tex file was plain tex and no latex. I managed to change this
> with the following line in my .vimrc
> let g:tex_flavor =3D "latex"
>
> I also solved the second problem (using your first method),
> however I still have a problem with "=E9". When I type
> 'e (in the insert mode) the cursor just move back one
> character if it is at the end of the line. Do you know how
> to get =E9?
>

Actualy this was discussed in this list in December 2006. Search the archiv=
es.

Vaidotas

Re: [Vim-latex-devel] newbie question

[Vaidotas Z. <ze...@gm...>]

Hi,

On 3/20/07, Alexandre Rosas <fre...@gm...> wrote:
> Thanks, Vaidotas. Your tip about the filetype helped me to
> find out a solution. The problem was the default type for
> .tex file was plain tex and no latex. I managed to change this
> with the following line in my .vimrc
> let g:tex_flavor =3D "latex"
>
> I also solved the second problem (using your first method),
> however I still have a problem with "=E9". When I type
> 'e (in the insert mode) the cursor just move back one
> character if it is at the end of the line. Do you know how
> to get =E9?
>
=E9 in vim is mapped to Alt-i. This is also vim-latex keymap for
inserting \item. I found that besides brackets.vim it is also used in
envmacros.vim. So if you already have
TexLet g:Tex_AdvancedMath=3D0

go to envmacros.vim file search for M-i, and either comment the lines
where this mapping is being used or change it to something else.

I am beginning to see a big problem. You cannot use some of the meta
mappings with vim, if you use certain accented letters a lot. And I
did not find any documentation about this feature. If you have further
problems with accented letters, try opening empty vim window, type all
the letters while holding alt, find which mapping corresponds to
accented letter and then search this mapping in vim-latex code. Highly
annoying!

Vaidotas

Re: [Vim-latex-devel] newbie question

[Alexandre R. <fre...@gm...>]

Thanks, Vaidotas. Your tip about the filetype helped me to
find out a solution. The problem was the default type for
.tex file was plain tex and no latex. I managed to change this
with the following line in my .vimrc
let g:tex_flavor =3D "latex"

I also solved the second problem (using your first method),
however I still have a problem with "=E9". When I type
'e (in the insert mode) the cursor just move back one
character if it is at the end of the line. Do you know how
to get =E9?

Thanks,
Alexandre

On 3/20/07, Vaidotas Zemlys <ze...@gm...> wrote:
>
> Hi,
>
> On 3/20/07, Alexandre Rosas <fre...@gm...> wrote:
> > Hi,
> > I've just got into the vim-latex world and I'm having some problems.
> > * The first one is that my .tex files are not detected as latex files
> (only
> > .latex files are). How can I make vim understand
> > that the .tex files are in fact latex files?
> >
> Hm, for me it works with vim 7.0, but I have older vim-latex version.
> It should be related to filetype selection in vim. Unfortunately I do
> not know enough to help you here.
>
> > * Often I need to type =E3 and my keyboard is configured so that whenev=
er
> I
> > type ~a I get =E3. However, vim-latex seems to bind
> > ~a to \cite{}. I've created the file .vim/after/ftplugin/tex.vim with
> > the following line:
> > call IMAP('~a', '=E3', 'tex')
> > but it did not work at all.
> >
> > By the way, I'm using vim 7.0 on linux (ubuntu edgy) and
> > vim-latex latexSuite20060325.tar.gz
> >
> >
> It is actualy a problem of vim, not vim-latex. For vim alt-c and =E3 is
> the same. When you press alt-c you get =E3, and when you press  =E3 vim
> generates alt-c. Since vim-latex uses mapping alt-c, you have the
> problem. I searched a bit, but found nothing how to turn of this
> behaviour. You can solve this problem in following ways:
>
> 1. Turn off vim-latex mapping alt-c. You have to have line
> TexLet g:Tex_AdvancedMath=3D0
>
> in your texrc file. There is  an explanation there, what else you will
> lose by setting this option
>
> 2. Enter  =E3, like diacritic, by pressing ctrl-k, then a, then ?.
>
> 3. Manually change alt-c mapping (actualy m-c) in brackets.vim to some
> other mapping you like.
>
> 4. Find how to turn off this unwanted vim behaviour, and share it with
> me:)
>
> Vaidotas
>

Re: [Vim-latex-devel] newbie question

[Vaidotas Z. <ze...@gm...>]

Hi,

On 3/20/07, Alexandre Rosas <fre...@gm...> wrote:
> Hi,
> I've just got into the vim-latex world and I'm having some problems.
> * The first one is that my .tex files are not detected as latex files (on=
ly
> .latex files are). How can I make vim understand
> that the .tex files are in fact latex files?
>
Hm, for me it works with vim 7.0, but I have older vim-latex version.
It should be related to filetype selection in vim. Unfortunately I do
not know enough to help you here.

> * Often I need to type =E3 and my keyboard is configured so that whenever=
 I
> type ~a I get =E3. However, vim-latex seems to bind
> ~a to \cite{}. I've created the file .vim/after/ftplugin/tex.vim with
> the following line:
> call IMAP('~a', '=E3', 'tex')
> but it did not work at all.
>
> By the way, I'm using vim 7.0 on linux (ubuntu edgy) and
> vim-latex latexSuite20060325.tar.gz
>
>
It is actualy a problem of vim, not vim-latex. For vim alt-c and =E3 is
the same. When you press alt-c you get =E3, and when you press  =E3 vim
generates alt-c. Since vim-latex uses mapping alt-c, you have the
problem. I searched a bit, but found nothing how to turn of this
behaviour. You can solve this problem in following ways:

1. Turn off vim-latex mapping alt-c. You have to have line
TexLet g:Tex_AdvancedMath=3D0

in your texrc file. There is  an explanation there, what else you will
lose by setting this option

2. Enter  =E3, like diacritic, by pressing ctrl-k, then a, then ?.

3. Manually change alt-c mapping (actualy m-c) in brackets.vim to some
other mapping you like.

4. Find how to turn off this unwanted vim behaviour, and share it with me:)

Vaidotas

[Vim-latex-devel] newbie question

[Alexandre R. <fre...@gm...>]

Hi,
I've just got into the vim-latex world and I'm having some problems.
* The first one is that my .tex files are not detected as latex files (only
.latex files are). How can I make vim understand
that the .tex files are in fact latex files?

* Often I need to type =E3 and my keyboard is configured so that whenever I
type ~a I get =E3. However, vim-latex seems to bind
~a to \cite{}. I've created the file .vim/after/ftplugin/tex.vim with
the following line:
call IMAP('~a', '=E3', 'tex')
but it did not work at all.

By the way, I'm using vim 7.0 on linux (ubuntu edgy) and
vim-latex latexSuite20060325.tar.gz<http://vim-latex.sourceforge.net/downlo=
ad/latexSuite20060325.tar.gz>

Any help would be appreciated.
Alexandre

[Vim-latex-devel] venting

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

venting helps me a bit and I don't see why it shouldn't others.  I am
not suggesting that Srinath put 1 more meme in the code that was made.
What I am suggesting is that 

1. it should be forked if no work is going to be done on it by the
initial developer(s) because it is the best LaTex program I know of but
it has bugs - what program doesn't :-) - and therefore can be
improved.  

2.  If I knew python I would immediately adopt this program.
Unfortunately I have other responsibilities but I am more than willing
to put some time into improving it.  

3. My intention of writing that letter was simply to point out, maybe in
an inferior way, that people do care about vim-latex.  That if the
developers of this project have no interest in continuing development on
this project they should make sure to open it up for new people.  

For instance Franz Pletz the Debian package manager of vim-latex has
made a patch to make the \cite and \ref function work but it needs to be
applied each time I install another distribution.  Patches should be
applied before using.  

improvements should be added that is all I am getting at.  Getting
emotional is about being human - get over it.

Re: [Vim-latex-devel] well thanks for not responding.

[Vaidotas Z. <ze...@gm...>]

An, 2007 03 13 13:33 -0700, Yigal Weinstein rašė:
> Fine I am not going to stay with a package that is dying.  It is a shame
> that such a nice package has to shrivel and die, but if you have no
> intention of bug fixing, new releases etc.  I have no interest in
> continuing with this project.  
> 
> 
I understand your frustration, but on the other hand this situation is
pretty common in open source world. So if the last update was very long
ago, and main developer is not responding you just move on. Do not vent
your anger publicly, since you are only showing disrespect. Srinath made
this project as it is, and if he is now more occupied with other stuff,
so be it. I am eternaly thankful to him, and even with no updates
vim-latex is still very useful for me. If you so badly want the updates
fork the project and provide your own, the source is open. Remember
nobody is obliged to create LaTeX plugin for vim, people are donating
their free time, since it is their free time, they are free to do with
it what they want. Insulting them or their work or saying how offended
you are will not get you anywhere, that is not how open source works.

Vaidotas

[Vim-latex-devel] Polski package available only in the main project file

[Bartlomiej C. <bar...@gm...>]

Hello,
That's my first post here, so just like to say hello again to all :)

Im having a small issue with vim-latex. Actually this is rather minor thing,
but a bit irritating. I am using polski package and thus there are things
like ,, '' that should appear instead of ``'' or a ~ in sentences like
a~propos. And the thing is that while the main project file is OK with those
locales, the rest of the files wont work like this. It works as if there was
no polski package things loaded at all. I can see it in the
TeX-Suite->Packages menu... Is there anything I'm doing wrong here? Or is it
a (known?) bug?

Thanks and regards,
--
Bartek Celary

[Vim-latex-devel] well thanks for not responding.

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

Fine I am not going to stay with a package that is dying.  It is a shame
that such a nice package has to shrivel and die, but if you have no
intention of bug fixing, new releases etc.  I have no interest in
continuing with this project.  

Re: [Vim-latex-devel] is vim-latex development dead?

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

I certainly hope that the development is not dead. There was an email
from Srinath some time ago on the list that he is graduated and he can
spend more time on vim-latex. This is a wonderful vim plugin and I
think it shouldn't be discontinued.


On 3/7/07, Yigal Weinstein <yig...@gm...> wrote:
> Have the developers stopped all work on latexsuite?  If so these scripts
> need to be adopted by people who are actively working on them - they are
> quite good and are still powerful.
>
> Yigal
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] is vim-latex development dead?

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

Have the developers stopped all work on latexsuite?  If so these scripts
need to be adopted by people who are actively working on them - they are
quite good and are still powerful.

Yigal

[Vim-latex-devel] section indentation

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

Thank you, this is a really nice option.  I think this is the kind of
open source community projects that can be good.  However the code has
to be simple enough to implement new features without disturbing other
ones.  Oh well, thanks.

reply to,

Message: 3
Date: Wed, 21 Feb 2007 11:26:11 +0100
From: "corentin barbu" <cor...@gm...>
Subject: [Vim-latex-devel] section indentation
To: vim...@li...
Message-ID:
        <f2e...@ma...>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I finally implement it myself, you can find the modified
.vim/indent/tex.vim attached.
I only don't find where to define the variable g:tex_indent_section.

If anybody is interested in ...

Or should I put it directly on the vim script site ?

Regards,

Corentin

Re: [Vim-latex-devel] "jump to error" doesn't jump

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

Hi,

I think this has been discusses in the list before. Search the list
for and I am pretty sure you find some information.

When I compile multi-file projects this feature doesn't work, but for
single file TeX files, it shows the location of the error.

Best,
Hooman

On 2/25/07, Jushan Bai <jus...@ny...> wrote:
> Hi,
>
> I'm using   gVIM7.0+ miktex2.5 + Windows XP.
> After compiling, hitting <enter> doesn't bring the cursor to the error
> place. There is no response. Any ideas? Thanks.
>
> Jushan
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] Vim Latex with new file with Vim.app on Mac OS X

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

Hi Ritesh,

I had the same problem on Win XP machine. The solution to your first
question is simple. Just put the following line in your _vimrc file
(or .vimrc if it is called that in Mac OS X):

let g:tex_flavor='latex'

This will solve the first part of your problem. As soon as you create
a new TeX file, the menus will appear.

I don't know about the previewers in Mac OS, but I believe you have to
set your favorite PDF viewer in texrc file. It shouldn't be difficult.

Best,
Hooman

On 3/2/07, Ritesh Nadhani <ri...@gm...> wrote:
> Hello
>
> I downloaded the Vim.app package from http://macvim.org/OSX/
> index.php. I installed it and downloaded the Vim-Latex package. I
> copied the stuff in .vim folder as mentioned in the tutorial.
>
> My .vimrc has the entry:
>
> syntax on
> set tabstop=4
> set guifont=Monaco:h12
> winsize 170 45
> filetype plugin on
>
> It seems that the suite dosnt work with Vim.app when I create a new
> file using the
>
> :e newfile.tex
>
> No change in the menu bars nor the F5 method works as mentioned at:
> http://vim-latex.sourceforge.net/documentation/latex-suite-quickstart/
> lsq-inserting-template.html
>
> Now if I open an existing .tex file, then I get an error:
>
> "No View rule defined for target pdf. Please specify a rule in
> $VIMRUNTIME/ftpluglin/tex/texrc :help Tex_ViewRule_format
>
> but I can now see the three Latex Suite menu and even things are
> working with <F5>.
>
> Is it a known issue? I can workaround the problem by creating an
> empty file in the terminal by using touch command and then opening
> the .tex file in VIM but sometimes it is not convenient.
>
> Is this a known issue or am I missing something?
>
> Ritesh
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

[Vim-latex-devel] Vim Latex with new file with Vim.app on Mac OS X

[Ritesh N. <ri...@gm...>]

Hello

I downloaded the Vim.app package from http://macvim.org/OSX/ 
index.php. I installed it and downloaded the Vim-Latex package. I  
copied the stuff in .vim folder as mentioned in the tutorial.

My .vimrc has the entry:

syntax on
set tabstop=4
set guifont=Monaco:h12
winsize 170 45
filetype plugin on

It seems that the suite dosnt work with Vim.app when I create a new  
file using the

:e newfile.tex

No change in the menu bars nor the F5 method works as mentioned at:  
http://vim-latex.sourceforge.net/documentation/latex-suite-quickstart/ 
lsq-inserting-template.html

Now if I open an existing .tex file, then I get an error:

"No View rule defined for target pdf. Please specify a rule in  
$VIMRUNTIME/ftpluglin/tex/texrc :help Tex_ViewRule_format

but I can now see the three Latex Suite menu and even things are  
working with <F5>.

Is it a known issue? I can workaround the problem by creating an  
empty file in the terminal by using touch command and then opening  
the .tex file in VIM but sometimes it is not convenient.

Is this a known issue or am I missing something?

Ritesh

[Vim-latex-devel] "jump to error" doesn't jump

[Jushan B. <jus...@ny...>]

Hi,

I'm using   gVIM7.0+ miktex2.5 + Windows XP.
After compiling, hitting <enter> doesn't bring the cursor to the error 
place. There is no response. Any ideas? Thanks.

Jushan

Re: [Vim-latex-devel] section indentation

[corentin b. <cor...@gm...>]

This version contain a minor bug fix

2007/2/21, corentin barbu <cor...@gm...>:
> I finally implement it myself, you can find the modified
> .vim/indent/tex.vim attached.
> I only don't find where to define the variable g:tex_indent_section.
>
> If anybody is interested in ...
>
> Or should I put it directly on the vim script site ?
>
> Regards,
>
> Corentin
> --
> ___________________
> Corentin Barbu
> http://corentin.barbu.free.fr/
> 91 avenue Gabriel P=E9ri
> 95200 Sarcelles
> France
> +33679284434
>


--=20
___________________
Corentin Barbu
http://corentin.barbu.free.fr/
91 avenue Gabriel P=E9ri
95200 Sarcelles
France
+33679284434

[Vim-latex-devel] section indentation

[corentin b. <cor...@gm...>]

I finally implement it myself, you can find the modified
.vim/indent/tex.vim attached.
I only don't find where to define the variable g:tex_indent_section.

If anybody is interested in ...

Or should I put it directly on the vim script site ?

Regards,

Corentin
--=20
___________________
Corentin Barbu
http://corentin.barbu.free.fr/
91 avenue Gabriel P=E9ri
95200 Sarcelles
France
+33679284434

[Vim-latex-devel] indentation

[corentin b. <cor...@gm...>]

Hello,
I desperatly look for indentation in latex files, I now use
latex-suite for months and I've already put the followings :
" OPTIONAL: This enables automatic indentation as you type.
filetype indent on

in .vimrc

and

" this is mostly a matter of taste. but LaTeX looks good with just a bit
" of indentation.
set sw=3D2

in ~/.vim/ftplugin/tex.vim

May you help me to find what's wrong ? Is it simply that latex-suite
doesn't allow indentation according to section, subsection etc... ?
Any help welcome to implement it.

Regards,

Corentin
___________________
Corentin Barbu
http://corentin.barbu.free.fr/
91 avenue Gabriel P=E9ri
95200 Sarcelles
France
+33679284434

[Vim-latex-devel] completing \ref on F9

[Sergei D. <dor...@ic...>]

Completing \cite on F9 work very well.
But when I want to complete \ref no F9, I get in the window __OUTLINE__
only two empty strings. When I press Enter
Tex_FinishOutlineCompletion() is calling but nothing occur.
system: GVim 7.0, Win Xp.

---
Best regards,
Sergei D.
dor...@ic...
IPCP RAS, Russia, Chernogolovka

Re: [Vim-latex-devel] Yap 2.5 and Locking Files

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

Hi

Unfortunately, I haven't found a solution to this problem. I have
noticed that the problem happens only when the AUX files is changes
(for example a new label is added, a new reference is added,
pagination is changed, etc.). In such cases I just close the file in
YAP and then issue the \lv command.

Basically, I think YAP is locking the AUX file, not the DVI file.

Best,

Hooman

[Vim-latex-devel] Problems with python2.5

[<tri...@gm...>]

Hello,

I run on archlinux testing, and they switched about one month ago to python2.5
Since then I have some problems with vim-latex

When running vim, I get the following message in the terminal :
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
'import site' failed; use -v for traceback

When setting $PYTONHOME to /usr (that is what I get with
python-config --exec-prefix), I only have the 'import site' failed;
use -v for traceback error.

In both cases, I get an error when opening a tex file (it disapears
instantly and I don't know how to see it again).
When compiling (\ll) I get the following message in vim :

                  line    2:
Traceback (most recent call last):
  File "<string>", line 1, in ?
NameError: name 'catFile' is not defined
line    4:
E121: Undefined variable: retval
E15: Invalid expression: retval
Error detected while processing function
RunLaTeX..Tex_CompileMultipleTimes..Tex_IsPresentInFile:
line    1:
Traceback (most recent call last):
  File "<string>", line 1, in ?
NameError: name 'isPresentInFile' is not defined
line    3:
E121: Undefined variable: retval
E15: Invalid expression: retval
line    1:
Traceback (most recent call last):
  File "<string>", line 1, in ?
NameError: name 'isPresentInFile' is not defined
line    3:
E121: Undefined variable: retval
E15: Invalid expression: retval
Ran latex 1 time(s)


Still the document compiles and I'm able to view it. Completion work...

I guess it's an as simple matter as setting the right variable, but I
didn't find anything about that.

Regards,

tristram

Re: [Vim-latex-devel] quickfix window doesn't work

[Aditya M. <ad...@um...>]

On Wed, 7 Feb 2007, Sandeep wrote:

> Hi,
> I am using GVIM 7.0 + Miktex. This installation had some hiccups. GVIM
> complains at the startup which disappears too quickly to make sense.

Try :message to see the output. The exact error message may be useful 
to determine what is going wrong.

Aditya