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

[Vim-latex-devel] [Contact] Windows Volume/Drive for RunLaTeX

[Franz Z. <vim...@so...>]

I\'ve got a *.tex file on my Windows \"D:\" drive. Unfortunately its impossible to 
compile it with latex-suite (version 1.5). So I looked up the file \"compiler.vim\" 
and the function \"RunLaTeX\". To change the directory from C: to \"D:/path.../\" 
it\'s not enough to execute \"cd D:/path.../\" on my windows system, obviously it is 
also takes a \"D:\"-command. 

Therefore, I think, it\'s only possible on my Win-PC 
to compile *.tex-files from my (c:)-volume. I\'m too clumsy to fix it myself, perhaps 
I\'m wrong anyway. Thanks in advance!  

[Vim-latex-devel] [Contact] BUG: <S F5> shows VIM-help instead of prompting environment names in xterm mode

[Lawrence T. <vim...@so...>]

If vim is invoked in xterm instead of gvim, the following two bugs are obversed:



1) 
When Shift-<F5> is hit (for both insert and normal mode), the VIM help window is shown 
instead of prompting me a list of environment name.  In gvim, this misbehavior is not 
observed.



2) None of the <Alt-X> macros works, even though the winaltkeys is set 
to 0.  However, in gvim, this misbehavior is not observed.



I am running it on RedHat 
Linux 9, i386 platform.  

[Vim-latex-devel] [Contact] problem with accent in e

[Galoppin F. <vim...@so...>]

I can\'t type é direclty in my latex file without using \\\'e but this character 
didn\'t appear. 



I can type è or à characters.

I put in my file so 
:

\\usepackage[latin1]{inputenc}

\\usepackage[T1]{fontenc}



I can type 
accent é in vim when I use another file than .tex files (when vim-latex is 
loaded).



Don\'t know if it\'s a bug.  

[Vim-latex-devel] [Contact] Viewing in mac

[aviv f. <vim...@so...>]

This is a great package and I am really enjoing it. Only one thing I can\'t seem to get 
working is viewing. I use mac osx and I tried to change the setting in texrc but no matter 
what i do \\lv does nothing. Is there somthing I am missing?

I set my compiler defult 
target to pdf and I would like to view it with Preview.

Thank you so much. 

Aviv  

[Vim-latex-devel] [Contact] Space in filename/path

[Pongtawat <vim...@so...>]

Hello,



I would like to know how to enable vim-latex to handle file name with space 
in it.

For example \'/home/joe/my files/my text file.tex\' won\'t compile under 
vim-latex.



Thank you.  

Re: [Vim-latex-devel] [Contact] A problem with =?iso-8859-1?Q?=5C?= =?iso-8859-1?B?IulcIg==?=

[David O. <dav...@cp...>]

On Mon, Apr 05, 2004 at 03:52:13AM -0700, Javier M Mora wrote:
>=20
> I\'m a spanish user of vim-latex (i use prepackaged vim-latexsuite from d=
ebian) and=20
> in my language we use these \"special\" caracters:
>=20
>=20
>=20
> =C1 =C9 =CD =D3 =DA =E1 =E9 =ED =F3 =FA =D1 =F1 =BF =A1 =FC =DC
>=20
>=20
>=20
> I can=20
> type all of them unless \"=E9\" than move the cursor in insert mode. I\'v=
e looked in=20
> sources of vim-latex but I cann\'t find anything.=20
>=20
>=20
>=20
> Can you change this=20
> \"feature\" to another macro? In spain \"=E9\" isn\'t a key. You must pus=
h \"\'\" key and=20
> them \"e\" key.
>=20

  I have almost the same problem in french. "=E9" is an equivalent for
Alt-I, and alt-I is remapped by vim-latex to the Tex_InsertItem
function.

The documentation says that one should affect this function to another
key with this mapping (we should put this in .vimrc or
~/.vim/ftplugin/tex.vim):

imap =A7 <Plug>Tex_InsertItem

where =A7 is the new mapping

Unfortunately, there is a bug in vim-latexsuite. The mapping is only
tested in normal mode.

To fix this, you can:
- use a dead map:

map =A7=A7=A7 <Plug>Tex_InsertItem

Note the map instead of imap. Where =A7=A7=A7 is a very unlikely key sequen=
ce.

Or you can fix the vim-latexsuite package. On my system, this means
editing the following file:
/usr/share/vim/addons/ftplugin/latex-suite/envmacros.vim

and change the line 903 from
  if !hasmapto("<Plug>Tex_InsertItem")
to
  if !hasmapto("<Plug>Tex_InsertItem", 'i')
 =20
and line 906 from
  if !hasmapto("<Plug>Tex_InsertItemOnNextLine")
to
  if !hasmapto("<Plug>Tex_InsertItemOnNextLine", 'i')
 =20
 =20
   Regards,

           DindinX


--=20
<dav...@cp...>

[Vim-latex-devel] [Contact] A problem with \"é\"

[Javier M M. <vim...@so...>]

I\'m a spanish user of vim-latex (i use prepackaged vim-latexsuite from debian) and 
in my language we use these \"special\" caracters:



Á É Í Ó Ú á é í ó ú Ñ ñ ¿ ¡ ü Ü



I can 
type all of them unless \"é\" than move the cursor in insert mode. I\'ve looked in 
sources of vim-latex but I cann\'t find anything. 



Can you change this 
\"feature\" to another macro? In spain \"é\" isn\'t a key. You must push \"\'\" key and 
them \"e\" key.



I\'m not subscribed to vim-latex-devel. If you want , you can 
re-send this thread to my email. jav...@ER...



Thanks  

[Vim-latex-devel] [Contact] loading log file and quickfix-window

[Milan B. <vim...@so...>]

Latex-suite does not display a quickfix-window when I use to compile-rules for ps. I 
use these parameters.



let g:Tex_FormatDependency_ps = \'dvi,ps\'

let 
g:Tex_DefaultTargetFormat = \'ps\'

let g:Tex_CompileRule_ps = \'dvips -o $*.ps 
$*.dvi\'



(Maybe there is an unnesesary backslash, I just want to escape all 
special characters.)



Without these it display the quickfix-window and I get 
just a dvi file.  

[Vim-latex-devel] [Contact] loading log file and quickfix-window

[Milan B. <vim...@so...>]

Latex-suite does not display a quickfix-window when I use to compile-rules for ps. I 
use these parameters.



let g:Tex_FormatDependency_ps = \\\'dvi,ps\\\'

let 
g:Tex_DefaultTargetFormat = \\\'ps\\\'

let g:Tex_CompileRule_ps = \\\'dvips 
-o \\$\\*.ps \\$\\*.dvi\\\'



(Maybe there is an unnesesary backslash, I just 
want to escape all special characters.)



Without these it display the 
quickfix-window and I get just a dvi file.  

[Vim-latex-devel] [Contact] cite completion tolerance

[<vim...@so...>]

hi,



i noticed that the automatic completion for bibtex-references only works, 
if the entry is surrounded by braces, whereas the entry is not recognised if in 
parentheses, like @ARTICLE(...). furthermore, the completion function seems to be 
confused, if @STRING... definitions occur in the bibtex file - the actual 
bib-entries are not listed anymore in such a case.



regards,

roman  

[Vim-latex-devel] [Contact] e-accute

[Vladimir C. <vim...@so...>]

Hi, I\'v got the following problem: I can\'t write the e-accute symbol in a tex 
document even after having done what the FAQ says, map the Tex_InsertItemOnThisLine 
to other key. When I intend to write it, the cursor blinks and stays at the same place or 
jumps one character to the left if it is after the last character on the line. At the same 
time the contents of the whole line blinks at the status/command line at the bottom 
(the line where the commands are typed).



Also I would like to point out a typo in the 
FAQ, in the section about e-accute. The file to be modified should most like be: 
~/.vim/ftplugin/tex.vim



Thanks



Vladimir  

[Vim-latex-devel] [Contact] Starting external programs under Windows

[Milan B. <vim...@so...>]

I have a problem (:-)



If I use the feature \"<mainfilename>.latexmain\", I got 
the problem with starting a dvi-viewer (Yap). Latex-Suite call Yap this 
way:



!start yap -1 c:\\Documnents\\ and\\ 
settings\\blabla\\bla.dvi



there are escaped <space>.



Yap says: \"Could 
not open: c:\\documents\\.dvi\". In Windows should be not \\<space> but 
\"<space>\"



So, if I execute on the command-line:



!start yap -1 
\"c:\\Documnents and settings\\blabla\\bla.dvi\"



it works very 
well.



And now the question:



How can I say to latex-suite, take the path of the 
bla.dvi in \"\" and not use escape sequences?  

[Vim-latex-devel] folding bug

[Claus A. <cla...@fr...>]

Hi,

I have experienced that there is a folding bug with \begin{figure*}. It
works fine without the "*", but with an "*" vim-latex folds
until the next (sub-)section starts.

I was copy & pasting the figure part from folding.vim into
after/ftplugin/folding.vim (new created file), but without success.

Anything I can do quickly?

Greetings,
Claus

[Vim-latex-devel] [Contact] missing russian letters

[Eugene <vim...@so...>]

Hello!



When I using gvim under Linux and change keymap from english into russian 
using my X-switcher, I can\'t get the russian letters if &ft=tex.  

Re: [Vim-latex-devel] [Contact] stuck floats

[Srinath A. <sr...@fa...>]

On Thu, 18 Mar 2004, trevor andrade wrote:

> I get error messages about stuck floats when I compile from vim latex
> but not when I compile using the commercial program WinEdt.  Both
> programs are running on WinXp and are using Miktex.

This is definitely not a bug in Latex-suite. If anything, I would think
this is a bug/lack of documentation in WinEdt. Latex-suite displays all
the warnings/errors which the following command produces:

	latex --src-specials --interaction=nonstopmode file.tex

except those errors/warning which have been explicitly "turned off" as
described in:

http://vim-latex.sourceforge.net/documentation/latex-suite/compiler-output-customization.html

If your email reader wraps that long URL, try this:

http://tinyurl.com/2qjhe

Srinath

[Vim-latex-devel] [Contact] stuck floats

[trevor a. <vim...@so...>]

I get error messages about stuck floats when I compile from vim latex but not when I 
compile using the commercial program WinEdt.  Both programs are running on WinXp and 
are using Miktex.   

[Vim-latex-devel] [Contact] latex-suite_1.5 smart quotes and stuff

[Lars W. <vim...@so...>]

Hi,

first of all a big thank you for latex-suite it\'s

just *great*. Especially 
the documentation :)

But in the latex-suite doc file for vim i couldn\'t

find an 
email address which says post bugs to this address,

so i am hopefully not too wrong 
here.



I noticed some points about the settup/behaviour of

latex-suite and 
justed wanted to share my views with you.

So let\'s begin:

* some file in the 
package (filebrowser.vim...) have

no label on them that they are shipped with 
latex-suite.

That\'s bad IMHO i had first to look around a little bit

until i felt 
sure that for example filebrowser.vim shipped

with latex-suite

Maybe you 
should leave a note in the filename or

even better put all files in one common sub 
directory.

* the mapping for `\"\': in german characters like

ß, ü, ä... are used 
very frequently. The mapping `+}\' is

too clumsy and by default only uses ä. This is 
not

very useful (hey i would try to tell that in a more

gentle way. But my English is 
too..uhm..bad)

So what about making the `\"\' mapping more configurable?

I 
personally use a keyboard with a british layout

and find it very convenient to use 
\\\"a and friends.

In ftplugin/latex-suite/main.vim i changed the mapping 
for

`\"\' to `\"\"\'. It\'s working quite good.

* I noticed further that the 
startup of vim is

quite a bit slower if i edit a tex file. Maybe this is not

a problem 
on modern machines but if latex-suite 

continues growing or a user has a more 
complicated setup

this might be an issue in the future. Is there no

way of making 
the loading of latex suite features

a little bit more dynamic?



That\'s it. 
Thank you for your time.

    --lars  

[Vim-latex-devel] fold header

[Claus A. <cla...@fr...>]

Hi,

how can I tell vim-latex to fold everything from the beginning of the
LaTeX file to \begin{document} (including this line)?

Greetings,
Claus

[Vim-latex-devel] foldding scheme

[Claus A. <cla...@fr...>]

Hi,

I am writing on a LaTeX document using vim and its LaTeX suite.
According to the LaTeX suite reference, a line which starts with
"%%fakesection" will be folded the same way as any \section. However,
not for me. %%fakesection is handled as all other text, whereas \section
etc. is folded.

BTW, I could not find a keystroke which lets me fold a specific area
once it is unfolded. Any idea how this would work?

Thanks for any hint!
Claus

Re: [Vim-latex-devel] Feature request: find current environment

[Alan S. <ala...@po...>]

* Srinath Avadhanula (sr...@fa...) wrote:
> On Mon, 15 Mar 2004, Srinath Avadhanula wrote:
>=20
> > problems changing Tex_InsertItem to behave as you describe. I'll make
> > the change soon.
> >
> Okay. I made the change in CVS. The latest should be usng the Tex_GetEnv
> function to form a more precise \\item.

Thanks. And thanks for putting in the code to keep the cursor in place.

Alan Schmitt

--=20
The hacker: someone who figured things out and made something cool happen.
=2EO.
=2E.O
OOO

Re: [Vim-latex-devel] Feature request: find current environment

[Srinath A. <sr...@fa...>]

On Mon, 15 Mar 2004, Srinath Avadhanula wrote:

> problems changing Tex_InsertItem to behave as you describe. I'll make
> the change soon.
>
Okay. I made the change in CVS. The latest should be usng the Tex_GetEnv
function to form a more precise \\item.

Srinath

Re: [Vim-latex-devel] [Contact] Typing accented characters

[Srinath A. <sr...@fa...>]

On Mon, 15 Mar 2004, Rui Lopes wrote:

> vim-latexsuite, it replaces it with \\cite{}<++>. If preceeded with a \'c=
\', it
> writes \\mathcal{C}. Is there any way to change this shortcut to write a
> \'=E3\'?
>
Please refer:

http://vim-latex.sourceforge.net/index.php?subject=3Dfaq&title=3DFAQ#faq-5

Srinath

[Vim-latex-devel] [Contact] Typing accented characters

[Rui L. <vim...@so...>]

Hi.

I\'m using portuguese characters but, when typing \'ã\' (tilde a) in 
vim-latexsuite, it replaces it with \\cite{}<++>. If preceeded with a \'c\', it 
writes \\mathcal{C}. Is there any way to change this shortcut to write a 
\'ã\'?



Cheers,



/rp  

Re: [Vim-latex-devel] Feature request: find current environment

[Srinath A. <sr...@fa...>]

On Mon, 15 Mar 2004, Alan Schmitt wrote:

> It would be very useful to be able to know what the current environment
> is, for instance to insert a closing tag, or to have a more precise
> behavior of the Tex_InsertItem() function (right now it guesses the
> environment according to the "begin" that occurs before, but it might
> guess wrong:
>
>       \begin{itemize}
>         \item ...
>         \item ...
>           \begin{description}
>             \item[Static] ...
>             \item[Dynamic] ...
>           \end{description}
>         % HERE it thinks it is in a description, and alt-i insert the
>         % wrong \item
>       \end{itemize}
> )
>

Yes. This sounds like how Tex_InsertItem should be behaving. The
solution you propose sounds excellent. I don't think there should be any
problems changing Tex_InsertItem to behave as you describe. I'll make
the change soon.

I remember from some time back Mikolaj and I had a bit of a discussion
about changing Tex_InsertItem and he had some reservations about
changing it to anything more complex than the present scheme...
Mikolaj: does Alan's scheme sound good?

Srinath

[Vim-latex-devel] Feature request: find current environment

[Alan S. <ala...@po...>]

Hi,

It would be very useful to be able to know what the current environment=20
is, for instance to insert a closing tag, or to have a more precise=20
behavior of the Tex_InsertItem() function (right now it guesses the=20
environment according to the "begin" that occurs before, but it might=20
guess wrong:

      \begin{itemize}
        \item ...
        \item ...
          \begin{description}
            \item[Static] ...
            \item[Dynamic] ...
          \end{description}
        % HERE it thinks it is in a description, and alt-i insert the=20
        % wrong \item
      \end{itemize}
)

Such a thing could reuse matchit, which is already able to match begin=20
and end environments. Or we could rewrite it from scratch (a simple=20
implementation that does not try to check whether the environments are=20
correctly opened and closed is:

function! Tex_GetCurrentEnv()
  " WARNING: this modifies the cursor position
  let i =3D 0
  while 1
    let env_line =3D search('^[^%]*\\\%(begin\|end\){', 'bW')
    if env_line =3D=3D 0
      " we reached the beginning of the file, so we return the empty string
      return ''
    endif
    if match(getline(env_line), '^[^%]*\\begin{') =3D=3D -1
      " we found a \\end, so we keep searching
      let i =3D i + 1
      continue
    else
      " we found a \\begin
      if i =3D=3D 0
	"this is the one we want
	let env =3D matchstr(getline(env_line), '\\begin{\zs.\{-}\ze}')
	return env
      else
	" this begin closes a \\end
	let i =3D i - 1
	continue
      endif
    endif
  endwhile
endfunction

function! Tex_InsertItem()
    " Get current enclosing environment
    let pos =3D line('.').' | normal! '.virtcol('.').'|'
    let env =3D Tex_GetCurrentEnv()
    exe pos

    if exists('g:Tex_ItemStyle_'.env)
      return IMAP_PutTextWithMovement(g:Tex_ItemStyle_{env})
    else
      return ''
    endif
endfunction
)

Alan Schmitt

--=20
The hacker: someone who figured things out and made something cool happen.
=2EO.
=2E.O
OOO