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

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

[Muhammad N. A. Z. <naj...@gm...>]

Hello, I was having problem compiling Arabic character (arabtex package).

--
documentclass[40pt]{article}
\usepackage{arabtex}
\begin{document}
\setmalay
\novocalize
Arab\TeX\ <^aku mnulis dgn .hurf jAwI gunA >

\end{document}
--

When I compiled these text with \ll it opened up arabtex.sty instead of
compiling.

What should I do?

Thanks!

Re: [Vim-latex-devel] Is this mailing list still active?

[Ted P. <te...@te...>]

The mailing list is certainly active, and there are still some 
maintainers (in particular, Till Mass) keeping the source up to date.

No clue on when the next official release will be; however, you can get 
a patched version of Vim-LaTeX from SVN. Patches are applied there 
pretty often (lately).

--Ted

On 9/24/09 5:38 AM, Johns Baber wrote:
> Sorry for asking such stupid question... But I really like vim-latex so
> I am just worried that it is not maintained by the authors... because it
> seems that this mailling list is not that active...
>
> Thank you :(
>
> J
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

-- 
Ted Pavlic <te...@te...>

   Please visit my 2009 d'Feet ALS walk page:
         http://web.alsa.org/goto/tedp
   My family appreciates your support in the fight to defeat ALS.

Re: [Vim-latex-devel] can you modify these?

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

On Thu, Sep 24, 2009 at 05:58:21AM -0400, xitong chen wrote:
> So I really wish you could put <++> as 
> 
> \begin{equation*}
> 
>    cursor here
> 
> \end{equation*}
> <++>

have a look at the vim-latex help (:help Tex_Env_name), you can
customize how you want to do the completion of any environment

-- 
Javier Rojas

GPG Key ID: 0x24E00D68

Re: [Vim-latex-devel] can you modify these?

[peng s. <sha...@gm...>]

On Thu, Sep 24, 2009 at 4:58 AM, xitong chen <xit...@li...> wrote:

>
> Hello dear maintainers. I was very happy with vim-latex in the past years.
> However I have two modifications
> which I would like you can take into consideration. For example if I press
> F5 when I was in insert mode I can choose equation*, and the output is
>
> \begin{equation*}
>    cursor here
> \end{equation*}<++>
>
> What I wish you could reconsider is the position of <++>. Many latex users,
> if my guess is correct, prefer typing latex file like
>
> we have the follow equation
> \begin{equation*}
>    my equation
> \end{equation*}
> then by this equation we know...
>
> So I really wish you could put <++> as
>
> \begin{equation*}
>    cursor here
> \end{equation*}
> <++>
>
>
> Ok the next modification is about
>
> $cursor here$my equation$$
>
> Since sometimes I just like to use $$ $$ for convenience. And of course you
> know vim-latex cannot recognize $$$$ well. It means if I press four $
> continuously I got
>
> $$<++>$<++>$<++>
>
> and instead what I really want is
>
> $$ cursor here $$
>
> So could you please add an auto-recognition for latex-suite that if I press
> two $ then of course as normal it gives out $cursor here$<++> and if I press
> an extra $ consequently then it
> recognize I want to have a $$ $$<++>
>
> Thank you.
>
> Xitong
>
>
>
OK I wish the maintainers can add these two functions as well ... Many
thanks.

Peng

[Vim-latex-devel] can you modify these?

[xitong c. <xit...@li...>]

Hello dear maintainers. I was very happy with vim-latex in the past years. However I have two modifications 
which I would like you can take into consideration. For example if I press F5 when I was in insert mode I can choose equation*, and the output is

\begin{equation*}
   cursor here
\end{equation*}<++>

What I wish you could reconsider is the position of <++>. Many latex users, if my guess is correct, prefer typing latex file like

we have the follow equation
\begin{equation*}

   my equation

\end{equation*}
then by this equation we know...

So I really wish you could put <++> as 

\begin{equation*}

   cursor here

\end{equation*}
<++>


Ok the next modification is about 

$cursor here$my equation$$

Since sometimes I just like to use $$ $$ for convenience. And of course you know vim-latex cannot recognize $$$$ well. It means if I press four $ continuously I got

$$<++>$<++>$<++>

and instead what I really want is

$$ cursor here $$

So could you please add an auto-recognition for latex-suite that if I press two $ then of course as normal it gives out $cursor here$<++> and if I press an extra $ consequently then it 
recognize I want to have a $$ $$<++>

Thank you.

Xitong


 		 	   		  
_________________________________________________________________
Insert movie times and more without leaving Hotmail®.
http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutorial_QuickAdd_062009

[Vim-latex-devel] Is this mailing list still active?

[Johns B. <jba...@gm...>]

Sorry for asking such stupid question... But I really like vim-latex so I am
just worried that it is not maintained by the authors... because it seems
that this mailling list is not that active...

Thank you :(

J

[Vim-latex-devel] error messages in gvim's multiplecompile

[peng s. <sha...@gm...>]

Hi everybody. I am using the latest latex-suite through svn and I have set

let g:Tex_MultipleCompileFormats='pdf'

in my .vimrc

Everything works pretty fine in vim. But for gvim there is some differences.
For example if I made a typo in my .tex file, then if I run \ll in
vim(launched through gnome-terminal)
it would take me to the compile message page and tell me that I made a
mistake, such as

! Undefined control sequence.
l.37     \lael
           {}
?

I press x to go back to the original .tex to modify my errors.

However if I run \ll in gvim, the command line shows

latex run time: 1

Then the screen freezes. I have to press ctrl+c to stop the compiling and
read the error messages. I guess the reason why the screen is frozen is
because the gvim met an error and could not go
further. But this is inconvenient for me. So is there any way to let gvim to
read the error messages as vim? I have looked into the documentation but did
not find anything related to my issue.

Thank you.

Peng

[Vim-latex-devel] [ vim-latex-Patches-2860944 ] Preserve primary paste buffer

[SourceForge.net <no...@so...>]

Patches item #2860944, was opened at 2009-09-17 22:50
Message generated for change (Tracker Item Submitted) made by johfel
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: Open
Resolution: None
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

[Vim-latex-devel] [ vim-latex-Bugs-2860939 ] Workaround for this bug

[SourceForge.net <no...@so...>]

Bugs item #2860939, was opened at 2009-09-17 22:44
Message generated for change (Tracker Item Submitted) made by johfel
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=2860939&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: Open
Resolution: None
Priority: 5
Private: No
Submitted By: johfel (johfel)
Assigned to: Nobody/Anonymous (nobody)
Summary: Workaround for this bug

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=466456&aid=2860939&group_id=52322

[Vim-latex-devel] Patches from Debian

[Johann F. S. <jo...@gm...>]

Dear vim-latex developers!

I'm (soon) the new maintainer of the Debian package vim-latexsuite which
packages your vim-latex.

There are some patches that I want forward to you. A summary is
attached.

You can find these patches (and some unimportant) on
http://patch-tracker.debian.org/package/vim-latexsuite/20090816-1

If you want, I can copy them to the sf.net patch tracker.

Best wishes
Johann Felix Soden


Here is the summary: 

==> fix_cite_completion.diff <==
Description: Fix the cite completion: \cite[\cf{abcd}]{<F9>
Author: Johann Felix Soden <jo...@gm...>
Bug-Debian: http://bugs.debian.org/449016

==> fix_input_completion.diff <==
Description: There is a branch missing so the filename completion doesn't work
 completely
Author: Johann Felix Soden <jo...@gm...>
Debian-Bug: http://bugs.debian.org/444397

==> fix_ngerman.diff <==
Description: Stop warning messages in old versions of vim when
 using \usepackage{ngerman}.
Author: Johann Felix Soden <jo...@gm...>
Bug-Debian: http://bugs.debian.org/507617

==> fix_viewer_calls.diff <==
Description: use xdg-open if available, use gv instead of ghostview
Author: Johann Felix Soden <jo...@gm...>

==> remove_escape_key_from_filedialog.diff <==
Description: Remove escape key from filebrowser
 Some shells send escape-key-sequences for the arrow keys. So the
 filebrowser should not be closed when using arrow keys.
Author: Johann Felix Soden <jo...@gm...>
Bug-Debian: http://bugs.debian.org/444394

==> save_errorformats.diff <==
Description: Don't overwrite the global error formats
Author: Thomas Koch <tho...@ym...>
Bug-Debian: http://bugs.debian.org/487661

==> support_labels_after_percent_sign.diff <==
Description: outline.py: \% should not start a comment
Author: Johann Felix Soden <jo...@gm...>
Bug-Debian: http://bugs.debian.org/381161

[Vim-latex-devel] VIM live locks when autocompletion is used.

[Raffi K. <kha...@cs...>]

Hello. My vim instance seems to live lock any time I use
autocompletion for either a citation or a reference. Has anyone else
had this problem? Any solutions? Thanks!

Re: [Vim-latex-devel] [PATCH] Various plugin files fail when path names contain spaces

[Gary J. <gar...@sp...>]

On 2009-09-01, Till Maas wrote:
> On Tue, Sep 01, 2009 at 12:31:44AM -0700, Gary Johnson wrote:
> 
> > I just got around to downloading the latest tarball of
> > /trunk/vimfiles from SourceForge, version 1.8.23.  main.vim now
> 
> Where did you get the version information "1.8.23" from? Afaik there is
> no such version.

I was looking for some way to refer to the particular version I had
installed and discovered this file,

    vimfiles/ftplugin/latex-suite/version.vim

which contains this:

    " Tex_Version: returns a string which gives the current version number of latex-suite
    ...
    function! Tex_Version()
            return "Latex-Suite: version 1.8.23"
    endfunction 

> > The solution is to remove the call to fnameescape() from line 28.
> > A patch is attached.  I hope it's in the right format this time.
> 
> Thank you, the patch (from your other mail) is in the right format and
> applied in revision 1069. A new snapshot is on the way to the
> webinterface.

You're welcome, and thank you.

Regards,
Gary

Re: [Vim-latex-devel] [PATCH] Various plugin files fail when path names contain spaces

[Till M. <ope...@ti...>]

On Tue, Sep 01, 2009 at 12:31:44AM -0700, Gary Johnson wrote:

> I just got around to downloading the latest tarball of
> /trunk/vimfiles from SourceForge, version 1.8.23.  main.vim now

Where did you get the version information "1.8.23" from? Afaik there is
no such version.

> The solution is to remove the call to fnameescape() from line 28.
> A patch is attached.  I hope it's in the right format this time.

Thank you, the patch (from your other mail) is in the right format and
applied in revision 1069. A new snapshot is on the way to the
webinterface.

> An alternative solution would be to keep line 28 as it is and remove
> most if not all of the other occurrences of fnameescape().  I think
> it's better practice, though, to not escape a file name until it's
> given to the OS.

I believe everywhere else I only used fnameescape once at the beginning
of a file or function, but I did not want to mess with that many lines
today.

Regards
Till

Re: [Vim-latex-devel] [PATCH] Various plugin files fail when path names contain spaces

[Gary J. <gar...@sp...>]

On 2009-09-01, Gary Johnson <gar...@sp...> wrote:

> The solution is to remove the call to fnameescape() from line 28.
> A patch is attached.  I hope it's in the right format this time.

> I didn't check to see if there were other places where fnameescape()
> was applied too often.

... or not often enough.  Removing it from line 28 caused a problem
when 'dict' was set.  New patch attached.

Regards,
Gary

Re: [Vim-latex-devel] [PATCH] Various plugin files fail when path names contain spaces

[Gary J. <gar...@sp...>]

On 2009-06-02, Till Maas <ope...@ti...> wrote:
> On Tue June 2 2009, Gary Johnson wrote:
> > Svn is not installed on the Windows computers on which I use the
> > vim-latex suite, so I attempted to get the latest versions on /trunk
> > by downloading the tarball using the "Download GNU tarball" link on
> > this page:
> >
> >     http://vim-latex.svn.sourceforge.net/viewvc/vim-latex/trunk/vimfiles/
> >
> > I discovered several places in various plugin files where other
> > files were sourced without properly accounting for spaces in path
> > names.  I fixed each of these by adding calls to fnameescape().
> > Patches are attached.
> 
> Thank you for your patches. They have been applied in changeset 1051. Be aware 
> that there may be other places that currently break in case there are spaces 
> in vim-latex. After I noticed this I also started to prepare a patch to use 
> fnameescape everywhere in vim-latex, but the patch is not yet ready. If 
> possible, I would prefer to get unified diffs as a patch and with the full 
> path to the files that are patched. That makes it a little easier to apply 
> them.

I just got around to downloading the latest tarball of
/trunk/vimfiles from SourceForge, version 1.8.23.  main.vim now
contains at least one too many calls to fnameescape().  In addition
to the ones I added in my patch, there is this one at line 28.

    let s:path = fnameescape(expand('<sfile>:p:h'))

This causes a problem when fnameescape() is applied again to s:path,
as on line 32,

    exe "so ".fnameescape(s:path.'/texrc')

The second fnameescape() sees the escapes added by the first
fnameescape() as part of the file name and escapes them, causing the
OS to also see those first escapes as part of the file name.

fnameescape() must be applied only once to the components of any
path.

The solution is to remove the call to fnameescape() from line 28.
A patch is attached.  I hope it's in the right format this time.

An alternative solution would be to keep line 28 as it is and remove
most if not all of the other occurrences of fnameescape().  I think
it's better practice, though, to not escape a file name until it's
given to the OS.

I didn't check to see if there were other places where fnameescape()
was applied too often.

Regards,
Gary

Re: [Vim-latex-devel] Custom verbatim-like environment

[rocku <ro...@gm...>]

Aditya Mahajan pisze:
>> I don't want to use the listings package as it would be just overkill to
>> what I am trying to do. I thought more of a workaround, possibly some
>> patch to latex-suite to force verbatim-like behavior to my 'code'
>> environment. I scanned throught the sources, but couldn't figure out how
>> latex-suite ignores verbatim environment. I am not familiar with vim's
>> script language, though.
> 
> You can you %stopzone to avoid the syntax highlighting from overrunning. 
> For example
> 
> \begin{code}
> $whatever
> \end{code}%stopzone

Thanks, that solved it. Altought I have to put %stopzone on the next
line because otherwise fancyvrb prints a error:

error| FancyVerb Error: Extraneous input ` %stopzone\end{}' between
\end{code} and line end


> should work. The syntax highlighting inside the code is still wrong, but 
> at least it will not overflow.
> 
> Another option is to open $VIMRUNTIME/syntax/tex.vim and search for 
> verbatim. You will see a sequence of lines like.
> 
> syn region texZone        start="\\begin{verbatim}"
> end="\\end{verbatim}\|%stopzone\>"    contains=@Spell
> 
> Add another similar line replacing verbatim with code. That will make 
> the code environment behave like the verbatim environment.

I also tried this and it works! I'll stick to this solution.

Thanks!

--
rocku

Re: [Vim-latex-devel] Custom verbatim-like environment

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

On Fri, 21 Aug 2009, rocku wrote:

> Ted Pavlic pisze:
>> Without giving it much thought, try something like...
>>
>> \begin{verbatim}
>> \endverbatim
>> \begin{code}
>> ...
>> \end{code}
>> \verbatim
>> \end{verbatim}
>
> This does not work, I receive the following after \ll in vim (using
> texlive):
>
> || pdfTeX warning (ext4): destinati
> |669 error| Extra \endgroup.
>
>
> |669 error| \begin{document} ended by \end{code}.
> |669 error| Extra \endgroup.
> |671 error| \begin{document} ended by \end{verbatim}.
> |671 error| Extra \endgroup.
> || Emergency stop.
> ||  ==> Fatal error occurred, no output PDF file produced!
>
>
> I don't want to use the listings package as it would be just overkill to
> what I am trying to do. I thought more of a workaround, possibly some
> patch to latex-suite to force verbatim-like behavior to my 'code'
> environment. I scanned throught the sources, but couldn't figure out how
> latex-suite ignores verbatim environment. I am not familiar with vim's
> script language, though.

You can you %stopzone to avoid the syntax highlighting from overrunning. 
For example

\begin{code}
$whatever
\end{code}%stopzone

should work. The syntax highlighting inside the code is still wrong, but 
at least it will not overflow.

Another option is to open $VIMRUNTIME/syntax/tex.vim and search for 
verbatim. You will see a sequence of lines like.

syn region texZone		start="\\begin{verbatim}"
end="\\end{verbatim}\|%stopzone\>"	contains=@Spell

Add another similar line replacing verbatim with code. That will make the 
code environment behave like the verbatim environment.

Aditya

Re: [Vim-latex-devel] Custom verbatim-like environment

[rocku <ro...@gm...>]

Ted Pavlic pisze:
> Without giving it much thought, try something like...
> 
> \begin{verbatim}
> \endverbatim
> \begin{code}
> ...
> \end{code}
> \verbatim
> \end{verbatim}

This does not work, I receive the following after \ll in vim (using 
texlive):

|| pdfTeX warning (ext4): destinati
|669 error| Extra \endgroup. 
 

|669 error| \begin{document} ended by \end{code}.
|669 error| Extra \endgroup.
|671 error| \begin{document} ended by \end{verbatim}.
|671 error| Extra \endgroup.
|| Emergency stop.
||  ==> Fatal error occurred, no output PDF file produced!


I don't want to use the listings package as it would be just overkill to 
what I am trying to do. I thought more of a workaround, possibly some 
patch to latex-suite to force verbatim-like behavior to my 'code' 
environment. I scanned throught the sources, but couldn't figure out how 
latex-suite ignores verbatim environment. I am not familiar with vim's 
script language, though.

--
rocku

Re: [Vim-latex-devel] Custom verbatim-like environment

[Ted P. <te...@te...>]

Also, check out the "listings" package, which provides some alternate 
ways to do what you're doing.

--Ted

On 8/21/09 2:52 PM, rocku wrote:
>
> Hi,
> I defined a custom 'code' environment using fancyvrb package. I would
> like this environment to be treated by latex-suite just like the
> verbatim environment, that is -- turn off all special characters effect
> inside it. Currently when I put code inside, then for example the '$'
> character breaks latex-suite outside of my 'code' environment. Is there
> a way to fix this?
>
> --
> rocku
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

-- 
Ted Pavlic <te...@te...>

   Please visit my 2009 d'Feet ALS walk page:
         http://web.alsa.org/goto/tedp
   My family appreciates your support in the fight to defeat ALS.

Re: [Vim-latex-devel] Custom verbatim-like environment

[Ted P. <te...@te...>]

Without giving it much thought, try something like...

\begin{verbatim}
\endverbatim
\begin{code}
...
\end{code}
\verbatim
\end{verbatim}

That is, recall that...

\begin{verbatim}

is LaTeX's way of saying

\verbatim

and...

\end{verbatim}

is LaTeX's way of saying

\endverbatim

except the \begin and \end macros add some extra protection.

Vim-LaTeX only looks for the \begin and \end varieties, and so it 
shouldn't "see" the \endverbatim and the \verbatim, but LaTeX will.

--Ted

On 8/21/09 2:52 PM, rocku wrote:
>
> Hi,
> I defined a custom 'code' environment using fancyvrb package. I would
> like this environment to be treated by latex-suite just like the
> verbatim environment, that is -- turn off all special characters effect
> inside it. Currently when I put code inside, then for example the '$'
> character breaks latex-suite outside of my 'code' environment. Is there
> a way to fix this?
>
> --
> rocku
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

-- 
Ted Pavlic <te...@te...>

   Please visit my 2009 d'Feet ALS walk page:
         http://web.alsa.org/goto/tedp
   My family appreciates your support in the fight to defeat ALS.

[Vim-latex-devel] Custom verbatim-like environment

[rocku <ro...@gm...>]

Hi,
I defined a custom 'code' environment using fancyvrb package. I would 
like this environment to be treated by latex-suite just like the 
verbatim environment, that is -- turn off all special characters effect 
inside it. Currently when I put code inside, then for example the '$' 
character breaks latex-suite outside of my 'code' environment. Is there 
a way to fix this?

--
rocku

[Vim-latex-devel] three letter sequences to insert environments

[Chuck Pepe-R. <cp...@mi...>]

I am looking for advice concerning how to change the default mapping for the
"e" key so that I can use three letter sequences to insert environments.
Right now as soon as I type "E" the cursor is sent to the end of the word it
is positioned in or the end of the next word if it was already positioned at
the end of a word.
Thanks,
- Chuck

Re: [Vim-latex-devel] F5--->equation environment

[Till M. <ope...@ti...>]

On Wed, Aug 12, 2009 at 03:04:38PM +0200, Alexander Stefanescu wrote:

> This log message says:
> >  Bug: In vim7, 'exe pos' doesn't seem to always work. Sometimes it leads to
> >       a spurious double-quote being inserted into the text. I have no idea
> >       why this happens. However, using vim's native setpos() when available
> >       seems to not have this problem.
> 
> While using setpos() instead of exe pos obviously doesn't trigger the 
> problem any more, this might turn up any time again, as vim-latex uses 
> input() with \n constantly. Therefore I wouldn't consider this bug fixed 
> yet, even if it's working at the moment.
> 
> This should probably be investigated by a more experienced vim-latex 
> developer, and if it's indeed a bug in input(), it needs to be fixed 
> upstream. I'll leave the upstream reporting in the capable hands of the 
> aforementioned experienced vim-latex developer ;)

Unfortunately we there is no such vim-latex developer currently
available. I mainly apply patches and sometimes try to fix issues, that
I can easily reproduce. Imho the best way to go is if you could create a
small example vim script that reproduces the bug that you suspect to be
in input(), then this can be reported easily at vim upstream.

Regards
Till

Re: [Vim-latex-devel] Spell check not working in tex mode

[Raffi K. <kha...@cs...>]

On Aug 16, 2009, at 7:25 PM, Till Maas wrote:

> On Sun, Aug 16, 2009 at 06:04:29PM -0400, Raffi Khatchadourian wrote:
>> On Aug 16, 2009, at 3:17 PM, Till Maas wrote:
>>
>>> On Sat, Aug 15, 2009 at 04:44:41PM -0400, Raffi Khatchadourian  
>>> wrote:
>>>> Sorry, I should have mentioned that spell was being set in  
>>>> my .vimrc
>>>> file. I've tried creating the tex.vim file and adding the suggested
>>>> line setlocal spell. What I just discovered is that the spell
>>>> underlining works for certain tex files but not others! That's very
>>>> strange. Any help would be greatly appreciated, thanks!
>>>
>>> Someone might help you a lot easier, if you provide an minimal  
>>> example
>>> tex file for which the spell checking does not work.
>>
>> Well, this was an interesting exercise! It seems that the spell check
>> only works when certain environments and commands are used. For  
>> example,
>> the spell check works fine when the \begin{document} and  
>> \end{document}
>> commands are present. It also works when the \section{...} and
>
> The problem is afaics not vim-latex related, but maybe somehow  
> hidden in
> the tex syntax rules shipped with vim. This is a workaround that works
> here on Fedora 10:
>
> :syntax spell toplevel
>
> References:
> http://vimdoc.sourceforge.net/htmldoc/syntax.html#:syn-spell
> :help spell-syntax
>
> Nevertheless it would be nice if you could forward this to the tex
> syntax file maintainer, but I do not know how to get in contact with
> him.

Thanks for the advice Till. That did the trick on my system. I will  
try to get in contact with the maintainer.

Raffi

[Vim-latex-devel] ref F9 key does not work

[YueJun Y. <yj...@gm...>]

Hi all
I am using Fedora 11. When I press F9 at a \ref{, a new window 
'_outline_' came out and the equations list are shown there (folded). 
However, when I tried to open folder using 'Tab' key. It does not work. 
I have to use 'zo' command. Then I choose the equation I want to refer 
and press 'enter'. Nothing comes out. Cursor stays on the equation I 
chose. And the \ref{ is not completed.
Anybody has an idea?

-- 
Yue-Jun Yin (Eugene)
PhD Candidate
Civil&  Environmental Engineering Dept.
Michigan Tech University
1400 Townsend Dr.
Houghton, MI 49931 USA
phone:(908)998-2573
email:yu...@mt...
http://www.cee.mtu.edu/~yuejuny/