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

Re: [Vim-latex-devel] problems in vim7 (not only)

[Thomas G. <Tho...@st...>]

Hi all,

Found the same problem.  In vim after inserting a environment using F5 
the text
turns white.  Latex-suite didnt even work at all in gvim for me.  Oh 
well maybe
once I have some spare time I can try and help getting it to work in vim 7.

If anyone find solutions please remember to post them.

Tom

Quoting Andreas Wagner <A.W...@st...>:

> Hello vim-latex-devel, hello list,
>
> * Andreas Wagner wrote on Mai/17/2006:
>>> On Wed, 17 May 2006, Andreas Wagner wrote:
>>>> I have the same behaviour (all the document is rendered in white 
>>>> background and one single foreground colour upon entering an 
>>>> insert command - I've just verified it with FIT. `it is not doing 
>>>> any harm tho.) on vim 6.3 and LaTeX-suite 1.8.13 (that's what 
>>>> LaTeX-suite/version.vim says) from March 28.
>>>
>>> Could it be because of the colorscheme? Try switching to a 
>>> different colorscheme and see if the problem persists.
>>
>> The problem persists both with another colorscheme (tried peachpuf, 
>> ps_color and without any) and with svn from an hour ago.
>
> As a sidenote, I found that if you select "test colors" in gvim's 
> "Syntax" menu, your colors return to normal.
>
> HTH,
> Andreas
>
>
> -- 
> Real programmers don't document. If it was hard to write, it should 
> be hard to understand.
>
> -- 
> My Public PGP Keys:
> 1024 Bit DH/DSS: 0x869F81BA
> 768 Bit RSA:     0x1AD97BA5
>
>
> -------------------------------------------------------
> 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
>

[Vim-latex-devel] Patch (to be reviewed): slide title in folding text

[Cristian R. <cr...@li...>]

Hi, I've just started using the prosper package and I happily discovered that
vim-latex lets me fold "slide" environments. Since I like to see the title of
each slide in the folded text, I made the enclosed patch (against the current
svn version of folding.vim), to turn this:

  \begin{slide}[options]{Title of the slide}
  ...
  ...
  \end{slide}

into this (when folded): 

  +-- 16 lines: slide () : Title of the slide

instead of just:

  +-- 16 lines: slide ()


(of course you must add "slide" to g:Tex_FoldedMisc in your
~/.vim/ftplugin/tex.vim to enable folding of slide environments)

Please note that it was a quick hack, maybe there's a cleaner way to do it;
maybe there are side-effects I've not considered, so give it a close look if you
plan to accept it (as if you wouldn't do :-)

Cri

-- 
GPG/PGP Key-Id 0x943A5F0E      -     http://www.linux.it/~cri/cri.asc
Free software, free society    -     http://www.fsfeurope.org

Re: [Vim-latex-devel] problems in vim7 (not only)

[Andreas W. <A.W...@st...>]

Hello vim-latex-devel, hello list,

* Andreas Wagner wrote on Mai/17/2006:
>> On Wed, 17 May 2006, Andreas Wagner wrote:
>>> I have the same behaviour (all the document is rendered in white 
>>> background and one single foreground colour upon entering an insert 
>>> command - I've just verified it with FIT. `it is not doing any harm 
>>> tho.) on vim 6.3 and LaTeX-suite 1.8.13 (that's what 
>>> LaTeX-suite/version.vim says) from March 28.
>>
>> Could it be because of the colorscheme? Try switching to a different 
>> colorscheme and see if the problem persists.
>
> The problem persists both with another colorscheme (tried peachpuf, 
> ps_color and without any) and with svn from an hour ago.

As a sidenote, I found that if you select "test colors" in gvim's 
"Syntax" menu, your colors return to normal.

HTH,
Andreas


-- 
Real programmers don't document. If it was hard to write, it should be 
hard to understand.

-- 
My Public PGP Keys:
1024 Bit DH/DSS: 0x869F81BA
768 Bit RSA:     0x1AD97BA5

Re: [Vim-latex-devel] problems in vim7 (not only)

[Andreas W. <A.W...@st...>]

Hi list,

* On 17 Mai 2006, Andreas Wagner wrote:
> The problem persists both with another colorscheme (tried peachpuf, 
> ps_color and without any) and with svn from an hour ago.

it seems I have gotten rid of it now. I've upgraded to vim7, but I don't 
think that this has much to do with it.
I had a plugin -- Hugo Haas's uri-ref (script_id=76) -- which I had 
changed a little bit. Unlike vim63, vim7 complained about a missing 
endfunction. When I removed the plugin, the syntax highlighting problem 
went away.

I've attached the plugin, maybe if you're interested -- and more 
knowledgeable than I am -- you can find the cuplrit in it. I'm not sure 
that this has been the problem of the original poster either...

HTH,
Andreas


-- 
File not found. Should I fake it? (Y/N)

-- 
My Public PGP Keys:
1024 Bit DH/DSS: 0x869F81BA
768 Bit RSA:     0x1AD97BA5

Re: [Vim-latex-devel] problems in vim7 (not only)

[Andreas W. <A.W...@st...>]

Hello Aditya, hello list,

* Aditya Mahajan wrote on Mai/17/2006:
> On Wed, 17 May 2006, Andreas Wagner wrote:
>> I have the same behaviour (all the document is rendered in white 
>> background and one single foreground colour upon entering an insert 
>> command - I've just verified it with FIT. `it is not doing any harm 
>> tho.) on vim 6.3 and LaTeX-suite 1.8.13 (that's what 
>> LaTeX-suite/version.vim says) from March 28.
>
> Could it be because of the colorscheme? Try switching to a different 
> colorscheme and see if the problem persists.

The problem persists both with another colorscheme (tried peachpuf, 
ps_color and without any) and with svn from an hour ago.

Andreas

-- 
Komme gleich wieder - Godot

-- 
My Public PGP Keys:
1024 Bit DH/DSS: 0x869F81BA
768 Bit RSA:     0x1AD97BA5

Re: [Vim-latex-devel] problems in vim7 (not only)

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

On Wed, 17 May 2006, Andreas Wagner wrote:

> Hello Kim, hello list,
>
> * Kim Schulz wrote on Mai/15/2006:
>> Whenever I execute one of the insert mode commands (like EIT) then it 
>> inserts the template correctly but the text in the entire document changes 
>> syntax coloring to have white background. I can't seem to revert this 
>> problem (going back to normal syntax colors) and have to restart gvim to 
>> have it back to normal. 
>
> I have the same behaviour (all the document is rendered in white background 
> and one single foreground colour upon entering an insert command - I've just 
> verified it with FIT. `it is not doing any harm tho.) on vim 6.3 and 
> LaTeX-suite 1.8.13 (that's what LaTeX-suite/version.vim says) from March 28.
>
> I have no idea what could be the cause of it, but it's getting on my nerves.

Could it be because of the colorscheme? Try switching to a different 
colorscheme and see if the problem persists.

-- Aditya

Re: [Vim-latex-devel] problems in vim7 (not only)

[Andreas W. <A.W...@st...>]

Hello Kim, hello list,

* Kim Schulz wrote on Mai/15/2006:
> Whenever I execute one of the insert mode commands (like EIT) then it 
> inserts the template correctly but the text in the entire document 
> changes syntax coloring to have white background. I can't seem to 
> revert this problem (going back to normal syntax colors) and have to 
> restart gvim to have it back to normal. 

I have the same behaviour (all the document is rendered in white 
background and one single foreground colour upon entering an insert 
command - I've just verified it with FIT. `it is not doing any harm 
tho.) on vim 6.3 and LaTeX-suite 1.8.13 (that's what 
LaTeX-suite/version.vim says) from March 28.

I have no idea what could be the cause of it, but it's getting on my 
nerves. I'll check out svn in a minute and keep you updated.

Andreas

-- 
Just because you're paranoid, that doesn't mean they're not after you.

-- 
My Public PGP Keys:
1024 Bit DH/DSS: 0x869F81BA
768 Bit RSA:     0x1AD97BA5

[Vim-latex-devel] problems in vim7

[Kim S. <ki...@sc...>]

Hi
I was just editing my first tex document in vim7 using latex-suite
(March 25, 2006 release) but it seems really buggy.

Whenever I execute one of the insert mode commands (like EIT) then it
inserts the template correctly but the text in the entire document
changes syntax coloring to have white background. I can't seem to
revert this problem (going back to normal syntax colors) and have to
restart gvim to have it back to normal. 

is anyone else experiensing this and is there a fix for it? 

Kim Schulz

[Vim-latex-devel] on/off

[Olivier R. <vi...@ri...>]

Hi,

 Is there is a way to switch off LateX-Suite for a while and then
switch it on again ?

 Each time I do a copy/paste of an URL or Unix commands, it's a mess.

Olivier.

Re: [Vim-latex-devel] Vim 7 problems

[Lee H. <on...@oh...>]

Thank you all, problem solved... Milan's suggestion got me looking at my 
_vimrc and I found that somehow I had a couple of _vimrc files on the 
hard drive. Vim 7 was looking at one while I was looking at another. 
Everything works as advertised now!

Milan Berta wrote:
> I had this problem with 7 (but I can't reproduce it in 6.4 now - cause
> I don't want it install it again..). The part of the .vimrc which
> contained the tex commands was placed too deep (e.g. in .vimrc ":so
> .vim/vimrc", then in .vim/vimrc ":so vimrc_tex",...). When I sourced it
> directly from .vimrc it worked. Isn't it also your problem?
> 
> Regards,
> Milan
> 
> On Wed May 10, 2006 at 08:29:36AM -0700, Lee Hauser wrote:
>> I can't seem to make vim-latex work in Vim 7. I've been using it without 
>> difficulty in 6.4, but after installing the latest version in my Vim 7 
>> folders (I use the Windows installer version), and with my the same 
>> _vimrc I used in 6.4, I don't see any LaTeX menus when I open a .tex 
>> file, nor do I get `` when I type ". Any idea what I may be doing wrong?
>>
>> Lee
>>
>>
>> -------------------------------------------------------
>> 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] Vim 7 problems

[Milan B. <ber...@ar...>]

I had this problem with 7 (but I can't reproduce it in 6.4 now - cause
I don't want it install it again..). The part of the .vimrc which
contained the tex commands was placed too deep (e.g. in .vimrc ":so
.vim/vimrc", then in .vim/vimrc ":so vimrc_tex",...). When I sourced it
directly from .vimrc it worked. Isn't it also your problem?

Regards,
Milan

On Wed May 10, 2006 at 08:29:36AM -0700, Lee Hauser wrote:
> I can't seem to make vim-latex work in Vim 7. I've been using it without 
> difficulty in 6.4, but after installing the latest version in my Vim 7 
> folders (I use the Windows installer version), and with my the same 
> _vimrc I used in 6.4, I don't see any LaTeX menus when I open a .tex 
> file, nor do I get `` when I type ". Any idea what I may be doing wrong?
> 
> Lee
> 
> 
> -------------------------------------------------------
> 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

-- 
* Milan Berta
* Institute of Physics
* Academy of Sciences of the Czech Republic
* Na Slovance 2
* CZ-182 21 Prague 8
* Czech Republic
* 
* mailto: be...@fz...
* phone:  +420 266 052 650, +420 266 052 748
* fax:    +420 286 890 416
* URL:    http://www.fzu.cz/

Re: [Vim-latex-devel] Vim 7 problems

[Lee H. <on...@oh...>]

Javier Rojas wrote:
> On 5/10/06, Lee Hauser <on...@oh...> wrote:
>> I can't seem to make vim-latex work in Vim 7. I've been using it without
>> difficulty in 6.4, but after installing the latest version in my Vim 7
>> folders (I use the Windows installer version), and with my the same
>> _vimrc I used in 6.4, I don't see any LaTeX menus when I open a .tex
>> file, nor do I get `` when I type ". Any idea what I may be doing wrong?
>>
>> Lee
>>
> perhaps your _vimrc was overwritten??
> 

I wish that was the case. Unfortunately, it's just as it was under Vim 
6.4...

Re: [Vim-latex-devel] Vim 7 problems

[Javier R. <jer...@gm...>]

On 5/10/06, Lee Hauser <on...@oh...> wrote:
> I can't seem to make vim-latex work in Vim 7. I've been using it without
> difficulty in 6.4, but after installing the latest version in my Vim 7
> folders (I use the Windows installer version), and with my the same
> _vimrc I used in 6.4, I don't see any LaTeX menus when I open a .tex
> file, nor do I get `` when I type ". Any idea what I may be doing wrong?
>
> Lee
>
perhaps your _vimrc was overwritten??

[Vim-latex-devel] Vim 7 problems

[Lee H. <on...@oh...>]

I can't seem to make vim-latex work in Vim 7. I've been using it without 
difficulty in 6.4, but after installing the latest version in my Vim 7 
folders (I use the Windows installer version), and with my the same 
_vimrc I used in 6.4, I don't see any LaTeX menus when I open a .tex 
file, nor do I get `` when I type ". Any idea what I may be doing wrong?

Lee

[Vim-latex-devel] Re: F9 completion does not work when a .latexmain file is present

[Thomas G. <Tho...@st...>]

Had same problem with using latexmain and non-existent files causing IOError.

I modified outline.py by adding try and except.

# This longish thing is to make sure that all files are converted into
# \n seperated lines.
    try:
      contents = '\n'.join(open(fname).read().splitlines())
      # TODO what are all the ways in which a tex file can include another?
      pat = re.compile(r'^\\(@?)(include|input){(.*?)}', re.M)
      contents = re.sub(pat, lambda input: getFileContents(input, ext),
contents)
    except IOError:
      contents = 'NONE\n'

    return ('%%==== FILENAME: %s' % fname) + '\n' + contents

Dont know much python so dont know if this correct but seems to work. I am sure
someone out there can improve it.

Tom

[Vim-latex-devel] ltags

[Dimitri A. <di...@ri...>]

 Hi,

 A few years ago I wrote the short script ltags that is included in vim-latex.
 I attach an improved version, in case anybody wants to use it.
 Changes:
 * now it can read multiply-nested \input'd files
 * fixed some strange things that people brought to my attention,
   eg \include can now have whitespace in front, 
   commented-out lines are ignored,
   it doesn't unnecessarily read the source file more than once (as the original did)
 * small changes in the regular expression capture more things, eg arguments
   in \cite commands that spread over more than 1 line.

 Also, I attach a very brief script I use, let's call it bibgrep,
 which can search the bibliography database file using keywords, like this:
     bibgrep keyword1 keyword2 ... 
 will print the full bibitems that matched these keywords.
 I invoke this script from inside vim, typing ",b" and then the keywords,
 and the results are shown in a preview vim window - I use these in my .vimrc:

     map ,b  :Bibgrep
     command -nargs=* Bibgrep call SearchBib(<f-args>)
     function SearchBib(first, ...)
       let keywords = a:first
       for morekeywords in a:000
          let keywords = a:first . ' ' . morekeywords
       endfor
       cexpr system('/usr/local/bin/bibgrep' . ' ' . keywords)
       copen
     endfunction

-- 
 Dimitri Antoniou
 Department of Biophysics
 Albert Einstein College of Medicine      
 email  : di...@ri...                 

[Vim-latex-devel] Vim 7 and character =?utf-8?q?=27=C3=A9=27_+_how_to_setup_s=3Atarget_in?= vimrc?

[Boris <bor...@cm...>]

Hi!

I have started using vim7 today and latex-suite from svn. However I cannot=
=20
type character '=C3=A9', I can press the key 100 times but nothing appears =
on the=20
screen. If I start typing after that, nothing special happens (e.g. the=20
letter '=C3=A9' has no side-effect). Other characters (e.g. =C4=9B, =C5=A1,=
 =C4=8D, =C5=99, =C5=BE, =C3=BD, =C3=A1,=20
=C3=AD, =C3=A9) just appear fine. The big letter '=C3=89' appears fine too.=
 Any suggestions?

I had problems with previous setup (don't remember exactly what version of=
=20
latex-suite, maybe also svn, but certainly vim 6.4) where I believe that th=
e=20
letter '=C3=A9' triggered a shortcut for "\item", if I recall correctly. Ma=
ybe=20
this might be a clue? (the unicode index of letter '=C3=A9' is 00E9, so it =
is in=20
latin1, so the problem probably has nothing to do with encodings. I am usin=
g=20
utf-8 as my file and terminal encoding)

Next question I have is on compilation, particularly s:target. When startin=
g a=20
session, I have to choose s:target by issuing ":TTarget pdf". Otherwise=20
compilation does not work because s:target is not defined. I would prefer t=
o=20
have it setup in my .vimrc. I tried in my .vimrc:

let s:target=3D'pdf'
let target=3D'pdf'

but it did not help.

My current .vimrc which worked till now looks like this:
let s:target=3D'pdf'
let target=3D'pdf'
let g:Tex_DefaultTargetFormat=3D'pdf'
let g:Tex_CompileRule_ps=3D'latex --interaction=3Dnonstopmode $*; dvips -Pp=
df-o=20
`basename $* .tex`.ps `basename $* .tex`.dvi'
let g:Tex_ViewRule_ps=3D'kghostview'
let g:Tex_CompileRule_pdf=3D'latex --interaction=3Dnonstopmode $*; dvips -P=
pdf -o=20
`basename $* .tex`.ps `basename $* .tex`.dvi; ps2pdf14 `basename $* .tex`.p=
s'
let g:Tex_ViewRule_pdf=3D'acroread'
let g:Tex_Env_exercise =3D "%<++>%{{{2\<CR>\\begin{exercise}{<++>}
{%\<CR><++>\<CR>}\<CR><++>\<CR>\\end{exercise}"

With non-svn latex-suite (dated approx. 2006-01-10) my .vimrc worked=20
seamlessly. I grepped for the string "s:target" in the whole doc subdirecto=
ry=20
of latex-suite, but it is not there. Could you please help me?

Thanks for any help/suggestions.

Best regards,
Boris Du=C5=A1ek

Re: [Vim-latex-devel] F9 completion does not work when a .latexmain file is present

[Dan D. <dr...@ma...>]

I figured it out!

The problem is all in the outline.py script. The following line

  pat =3D re.compile(r'^\\(@?)(include|input){(.*?)}', re.M)

only looks for \input and \include statements at the beginning of the
line. My 0main.tex file didn't have those statements at the beginning of
the line, so the outline.py script never looked in those files and never
found any tags. When the .latexmain file wasn't present, I would be
editing a file in one of the subdirectories, and the F9 completion would
only run outline.py on the current file.

Removing the caret solves the main problem but introduces another
problem. Many of my figures have LaTeX-formatted text in them; I use the
"Combined PS/LaTeX" export format in Xfig, and in my document use
"\input{foo.pstex_t}" to pull in the figure -- but without the caret,
outline.py tries to search that file, and if it doesn't exist, the
script dies.

I would recommend dropping the caret from the regex, and adding some
logic to the getFileContents function so that it simply ignores
nonexistent files.

Dan



--=20
---    Dan Drake <dr...@ma...>    University of Minnesota
-----    http://www.math.umn.edu/~drake    School of Mathematics
-------

Re: [Vim-latex-devel] Bug#365572: vim-latexsuite: Screen not redrawn after compilation via \ll

[Srinath A. <sri...@gm...>]

Hi Franz,

On 5/1/06, Franz Pletz <fp...@fr...> wrote:
> I've got a new bug in Debian which I am able to reproduce only partly.
> Please refer to http://bugs.debian.org/365572 for details.
>
> Original report following:
>
> After recompilation of my LaTeX files via \ll inside a terminal running
> vim, the terminal content is not redrawn and only one line of text shows
> up. After pressing <Ctrl>+l everything shows up normally again. This
> doesn't happen with gvim.

With the latest version, I am unable to reproduce this at all! If there
is a test case or anything similar, I can try to fix it.

Thanks
Srinath

[Vim-latex-devel] F9 completion does not work when a .latexmain file is present

[Dan D. <dr...@ma...>]

I have a large project (my thesis) and F9 completion does not work when
a .latexmain file is present. I hit F9 and the bottom window opens, but
nothing is in it.

I've tried various uses of Tex_ProjectSourceFiles,
Tex_UseSimpleLabelSearch, and so on, but I eventually discovered that
even an empty .latexmain file makes the completion not work. When I
remove the .latexmain file, completion works as advertised.

I'm using the most recent version of vim-latex.

Any suggestions?

Dan

--=20
---    Dan Drake <dr...@ma...>    University of Minnesota
-----    http://www.math.umn.edu/~drake    School of Mathematics
-------

Re: [Vim-latex-devel] sloppypar

[Srinath A. <sri...@gm...>]

Hi Bernhard,

On 5/1/06, Bernhard Walle <ber...@gm...> wrote:
> I think the 'sloppybar' environment should be a  'sloppypar'
> environment, shouldn't it?
>
Yes... It should be. I'll fix this in SVN.

Thanks,
Srinath

[Vim-latex-devel] sloppypar

[Bernhard W. <ber...@gm...>]

Hello,

I think the 'sloppybar' environment should be a  'sloppypar'
environment, shouldn't it?


Regards,
  Bernhard
-- 
Der Mensch erfand die Atombombe, doch keine Maus der Welt würde eine
Mausefalle konstruieren
	-- Albert Einstein

[Vim-latex-devel] Bug#365572: vim-latexsuite: Screen not redrawn after compilation via \ll

[Franz P. <fp...@fr...>]

Hi,

I've got a new bug in Debian which I am able to reproduce only partly.
Please refer to http://bugs.debian.org/365572 for details.

Original report following:

After recompilation of my LaTeX files via \ll inside a terminal running
vim, the terminal content is not redrawn and only one line of text shows
up. After pressing <Ctrl>+l everything shows up normally again. This
doesn't happen with gvim.

Cheers,
Franz

--=20
Franz Pletz                   \  The Internet treats censorship as
www: http://franz-pletz.org/   \  damage and routes around it.
email: fp...@fr...   \  -- John Gilmore

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

[Srinath A. <sri...@gm...>]

Hi Long,

On 4/29/06, Chen Long <che...@ps...> wrote:
> I am new to vim-latex. When I open .tex file using Vim. It says that
>
> No View rule defined for target pdf
> Please specify a rule in $VIMRUNTIME/ftplugin/tex/texrc
>     :help Tex_ViewRule_format
>
> What should I do? by the way, I am using Mac OS 10.4.

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 =3D '/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.

Thanks,
Srinath

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

[Chen L. <che...@ps...>]

I am new to vim-latex. When I open .tex file using Vim. It says that

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

What should I do? by the way, I am using Mac OS 10.4.

Thanks,

Long