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

[Vim-latex-devel] [ vim-latex-Bugs-3293172 ] okular search doesn't work when default format is pdf

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

Bugs item #3293172, was opened at 2011-04-26 17:32
Message generated for change (Tracker Item Submitted) made by burcin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3293172&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: Burcin Erocal (burcin)
Assigned to: Nobody/Anonymous (nobody)
Summary: okular search doesn't work when default format is pdf

Initial Comment:
The okular search command has the .dvi extension hard coded. A simple change to compiler.vim like the attached patch fixes this.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3293172&group_id=52322

[Vim-latex-devel] Turning latex-suite off

[<ma...@fs...>]

Hi,

I was wondering how to turn off the loading of vim-latex. The problem
is I am at a computer where the admin installed vim-latex and i would
need to turn it off, but it doesn't seem to honour the ususal
did_ftplugin variable. 
What other way is there to disable it?

Thanks in Advance, 
Yours Max 

[Vim-latex-devel] [BUG] When create a new tex file, the "}" will be highlight.

[Zhou Yi C. <bro...@gm...>]

Hi, everyone
  When create a new tex file, the "}" will be highlight. This is
really annoying. I must type another "nohl". I tried to detect where
this happen but it is too difficult for me.

  Anyone has run into this problem?

Regards,
Zhou Yichao

Re: [Vim-latex-devel] "`o" doesn't produce \omiga

[Zhou Yi C. <bro...@gm...>]

We should make use of "`o", since it isn't maped to any Greece character.

I think a good solution is let `&->\wedge `w -> omiga and `o ->
omicron. Anyway let `& and `w both map to \wedge is a huge waste.

> `. also doesn´t produce \cdot as it should either..
Yes. This is in the document. So it is a bug and should be fixed.



On Thu, Mar 31, 2011 at 10:00 PM, Ted Pavlic <te...@te...> wrote:
>>> "`o" doesn't produce \omiga. But I think it should.
>> By default omega is mapped to "`w".
>
> That doesn't appear to be the case. In main.vim, `w is IMAPped to
> \omega, but then it gets overridden right after that with a mapping of
> `w to \wedge (even though there is already a `& mapping to wedge). I
> wonder if this is a bug... it was added deliberately in 2003 with the
> comment 'AUCTEX style'.
>
> However, `W is mapped to \Omega for sure.
>
> I'm not sure there is a clear convention. Some would argue that `o
> should be mapped to omicron, not omega. I think the argument for w is
> that the lowercase omega looks like a w and both omega and w come
> near/at the end of the alphabet... but then there's an argument that
> `z should be mapped to omega.
>
> Maybe this is why the Greeks invented tab completion...
>
> --Ted
>
> --
> Ted Pavlic <te...@te...>
>
> ------------------------------------------------------------------------------
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] The error occur when the template include \usepackage{unicode-math}

[Zhou Yi C. <bro...@gm...>]

Hi, everyone
  I have made a patch about this problem. It just subtitute all the
'-' with '_'.  I use vimgrep to find Tex_.*_options. Only find it is
used in package file. So I think this is pretty safe.

  Hope the maintainer can upload it to the git.

  Thanks.

Regards.
Zhou YiChao.

PATCH:
diff -u latex-suite_old/main.vim latex-suite/main.vim
--- latex-suite_old/main.vim	2011-02-15 04:27:48 +0800
+++ latex-suite/main.vim	2011-04-20 20:55:56 +0800
@@ -313,6 +313,16 @@
 endfun

 " }}}
+
+" Tex_StrTurnHyphen: Replace all the - to _. Let package unicode-math be {{{
+" unicode_math in order to get no error message. ('-' is not allowed as a
+" variable character.)
+fun! Tex_StrTurnHyphen(s)
+	return substitute(a:s, '-', '_', 'g')
+endfun
+
+" }}}
+
 " Tex_CreatePrompt: creates a prompt string {{{
 " Description:
 " Arguments:

diff -u latex-suite_old/packages.vim latex-suite/packages.vim
--- latex-suite_old/packages.vim	2011-02-15 04:27:48 +0800
+++ latex-suite/packages.vim	2011-04-20 20:49:31 +0800
@@ -386,7 +386,7 @@
 		" which contains a list of the options.
 		let j = 1
 		while Tex_Strntok(@a, ',', j) != ''
-			let g:Tex_{Tex_Strntok(@a, ',', j)}_options = options
+			let g:Tex_{Tex_StrTurnHyphen(Tex_Strntok(@a, ',', j))}_options = options
 			let j = j + 1
 		endwhile


On Wed, Mar 30, 2011 at 10:35 PM, Zhou Yi Chao
<bro...@gm...> wrote:
>
> Hi, everyone
>
> It seems that it is package.vim line 389 cause the problem. When \usepackage{unicode-math}, it will do "let g:Tex_unicode-math_options = .....". But vim doesn't allow "-" in it variable name. So the error occurs. I'm not familiar with what is the role of g:Tex_unicode-math_options so I can't fix it.

[Vim-latex-devel] [ vim-latex-Bugs-3288397 ] SECURITY: Include vulnerability in web site

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

Bugs item #3288397, was opened at 2011-04-17 11:46
Message generated for change (Tracker Item Submitted) made by rutsky
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3288397&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: Yes
Submitted By: Vladimir Rutsky (rutsky)
Assigned to: Nobody/Anonymous (nobody)
Summary: SECURITY: Include vulnerability in web site

Initial Comment:
/htdocs/index.php don't sanitize input GET arguments which can lead to exploitation of include vulnerability (http://en.wikipedia.org/wiki/Include_vulnerability).

For example going by this link:
http://vim-latex.sourceforge.net/index.php?subject=../../newsexample/htdocs/include-vuln
Will include script from another project http://newsexample.sourceforge.net/include-vuln.inc and run it's contents under vim-latex project "user". 
According to SourceForge web filesystem documentation (https://sourceforge.net/apps/trac/sourceforge/wiki/Project%20Web%20Filesystem%20Permissions) this can lead to overwriting of vim-latex web site files, and potential hacker can gain control over vim-latex project web site.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3288397&group_id=52322

[Vim-latex-devel] [ vim-latex-Bugs-3288379 ] Typo in documentation: "Th bottom"

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

Bugs item #3288379, was opened at 2011-04-17 11:16
Message generated for change (Tracker Item Submitted) made by rutsky
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3288379&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: Vladimir Rutsky (rutsky)
Assigned to: Nobody/Anonymous (nobody)
Summary: Typo in documentation: "Th bottom"

Initial Comment:
See attached patch for details.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3288379&group_id=52322

[Vim-latex-devel] [PATCH] set makeprg to "make" if there is a Makefile

[Emmanuel G. <gra...@gm...>]

Hi all,

vim-latexsuite checks for a Makefile and set makeprg accordingly only
when Tex_CompileLatex() is called. The problem is when you want to use
the ":make" command : makeprg is set to the default rule (pdflatex),
so it does not use the Makefile.

Here is a small hack to make this feature work (add a check in
Tex_SetTeXCompilerTarget):

diff --git a/vimfiles/ftplugin/latex-suite/compiler.vim
b/vimfiles/ftplugin/latex-suite/compiler.vim
index 08b0509..597293f 100644
--- a/vimfiles/ftplugin/latex-suite/compiler.vim
+++ b/vimfiles/ftplugin/latex-suite/compiler.vim
@@ -24,7 +24,13 @@ function! Tex_SetTeXCompilerTarget(type, target)

        if targetRule != ''
                if a:type == 'Compile'
-                       let &l:makeprg = escape(targetRule,
Tex_GetVarValue('Tex_EscapeChars'))
+            " check if we have a Makefile, and if we want to use it set
+            " makeprg accordingly
+            if Tex_GetVarValue('Tex_UseMakefile') &&
(glob('makefile') != '' || glob('Makefile') != '')
+                let &l:makeprg = 'make $*'
+            else
+                let &l:makeprg = escape(targetRule,
Tex_GetVarValue('Tex_EscapeChars'))
+            endif
                elseif a:type == 'View'
                        let s:viewer = targetRule
                endif

Cheers,
Emmanuel

[Vim-latex-devel] Smart key mappings with vim keymap enabled

[Alexey B. <aba...@gm...>]

Hi.

I'm using vim 7.3 on windows and have the following keymap set up in
my _vimrc file:

set keymap=russian-jcukenwin

When the keymap is ... well ... "activated" (via CTRL-^) smart key
mappings in vim-latex stop working. Is there any way I can have them
back?

Re: [Vim-latex-devel] "`o" doesn't produce \omiga

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

>> "`o" doesn't produce \omiga. But I think it should.
> By default omega is mapped to "`w".

That doesn't appear to be the case. In main.vim, `w is IMAPped to
\omega, but then it gets overridden right after that with a mapping of
`w to \wedge (even though there is already a `& mapping to wedge). I
wonder if this is a bug... it was added deliberately in 2003 with the
comment 'AUCTEX style'.

However, `W is mapped to \Omega for sure.

I'm not sure there is a clear convention. Some would argue that `o
should be mapped to omicron, not omega. I think the argument for w is
that the lowercase omega looks like a w and both omega and w come
near/at the end of the alphabet... but then there's an argument that
`z should be mapped to omega.

Maybe this is why the Greeks invented tab completion...

--Ted

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

Re: [Vim-latex-devel] "`o" doesn't produce \omiga

[Kay S. <kay...@go...>]

On Wed, Mar 30, 2011 at 6:31 PM, Mike Richman <ri...@um...> wrote:
> Is that true?  In latex-suite.txt, it says:
>
> NOTE: Over-riding Latex-Suite Macros
>      ------------------------------
>      If you wish to change these macros from their default values, for example,
>      if you wish to change `w to expand to \omega instead of its default
>      expansion to \wedge, you should use the IMAP function as described in the
>      Using IMAP() [|ls_a_bG|] section.
I had some issues with that quite some time ago. Without having an
working latexsuite enviromnent here I guess that the concerning file
is mathmacros.vim[1] with the lines
exe s:pA2.'omega<Tab>`w             <plug>\omega '
and
exe s:pA3.'Omega<Tab>`W             <plug>\Omega '
pointing `w to omega.

http://vim-latex.git.sourceforge.net/git/gitweb.cgi?p=vim-latex/vim-latex;a=blob_plain;f=vimfiles/ftplugin/latex-suite/mathmacros.vim;hb=HEAD

Kind regards

-- 
Kay Smarczewski
Web: http://www.smarczewski.de

Re: [Vim-latex-devel] "`o" doesn't produce \omiga

[Mike R. <ri...@um...>]

Is that true?  In latex-suite.txt, it says:

NOTE: Over-riding Latex-Suite Macros
      ------------------------------
      If you wish to change these macros from their default values, for example,
      if you wish to change `w to expand to \omega instead of its default
      expansion to \wedge, you should use the IMAP function as described in the
      Using IMAP() [|ls_a_bG|] section.

Could be out of date or something, though.

-Mike Richman


On Wed, Mar 30, 2011 at 11:19 AM, Kay Smarczewski
<kay...@go...> wrote:
> On Wed, Mar 30, 2011 at 4:51 PM, Zhou Yi Chao
> <bro...@gm...> wrote:
>> "`o" doesn't produce \omiga. But I think it should.
> By default omega is mapped to "`w".
>
> Kind regards,
>
> --
> Kay Smarczewski
> Web: http://www.smarczewski.de
> Tel.: +49 175 86 46 704
>
> ------------------------------------------------------------------------------
> Create and publish websites with WebMatrix
> Use the most popular FREE web apps or write code yourself;
> WebMatrix provides all the features you need to develop and
> publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] "`o" doesn't produce \omiga

[Kay S. <kay...@go...>]

On Wed, Mar 30, 2011 at 4:51 PM, Zhou Yi Chao
<bro...@gm...> wrote:
> "`o" doesn't produce \omiga. But I think it should.
By default omega is mapped to "`w".

Kind regards,

-- 
Kay Smarczewski
Web: http://www.smarczewski.de
Tel.: +49 175 86 46 704

Re: [Vim-latex-devel] "`o" doesn't produce \omiga

[Mike R. <ri...@um...>]

I think it should too.  I forget whether it does nothing or expands to
something else by default, but I get \omega by placing the following
in my ~/.vim/ftplugin/tex.vim:

call IMAP (g:Tex_Leader . 'o', '\omega', 'tex')

Hope this helps!

-MIke Richman

On Wed, Mar 30, 2011 at 10:51 AM, Zhou Yi Chao
<bro...@gm...> wrote:
> "`o" doesn't produce \omiga. But I think it should.
>

[Vim-latex-devel] "`o" doesn't produce \omiga

[Zhou Yi C. <bro...@gm...>]

"`o" doesn't produce \omiga. But I think it should.

[Vim-latex-devel] The error occur when the template include \usepackage{unicode-math}

[Zhou Yi C. <bro...@gm...>]

Hi, everyone

It seems that it is package.vim line 389 cause the problem. When
\usepackage{unicode-math}, it will do "let g:Tex_unicode-math_options =
.....". But vim doesn't allow "-" in it variable name. So the error occurs.
I'm not familiar with what is the role of g:Tex_unicode-math_options so I
can't fix it.

Re: [Vim-latex-devel] Just a random idea

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

> I have to write documents with MANY headlines so I was wondering, if it
> would be possible to write a script, that displays "\section{Headline
> 1}" in vim simply as "Headline 1" in another color and maybe centered.

The default syntax highlighting that is packaged with Vim (at least 7.3)
already colors section headings (and you could conceivably change the
color/formatting of sections if you wish).

Look for "syntax/tex.vim" in your system's vimfiles directory. That
syntax definition might give you some ideas on how you can customize how
sections (or even sections that start with "Heading") are displayed.

Furthermore, what do you think of the default folding behaviors in
Vim-LaTeX? Vim-LaTeX knows how to fold by sections, and that grouping
might serve the same purpose as what you're requesting. I know it works
well for me. A document with seven sections looks like it only has seven
lines until I inspect the fold that I'm interested in.

Best --
Ted

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

[Vim-latex-devel] Just a random idea

[Taras K. <tke...@gm...>]

Hi,

first of all: Thank you for all your good work! I want to contribute
somehow and today I had the following idea, which I´d like to realize:

I have to write documents with MANY headlines so I was wondering, if it
would be possible to write a script, that displays "\section{Headline
1}" in vim simply as "Headline 1" in another color and maybe centered.

I´m already reading tutorials and manuals on vim-script, but so far I´m
not sure if this type of functionality is possible..

What do you think about it? Would it work just using vim-script?

Thanks,
 Taras

Re: [Vim-latex-devel] path to latex

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

> Actually I mostly only use MacTeX. I think the ones from ports and fink
> got installed since other applications from fink / ports depend on then.
> Maybe I could have avoided this making them use MacTeX, but I was too
> lazy for this.
> 
> Letting Tex_CompileRule_pdf point to /usr/texbin/pdflatex is fine for me for the moment.

Alternatively, changing your path to prioritize /usr/texbin over /sw and
/opt (as discussed in the MacTeX FAQ) should also work.

(although, on a Mac, you'll either have to change the path in your
environment.plist or (if you are using MacVim) go into your MacVim
settings and ensure it runs itself inside a shell (so you can easily
make changes to your profile/rc files))

--Ted

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

Re: [Vim-latex-devel] path to latex

[Udo H. <udo...@we...>]

Hello Ted,

thanks for your quick and very helpful answer.

On Wed, Mar 23, 2011 at 10:59:29AM -0400, Ted Pavlic wrote:
> > I trying to use latex on Mac OS X with MacVim. I have more than one
> > LaTeX distribution installed (comming from macports, fink and the one
> > comming with TexShop). How can I tell vim-latex-suite which one to use?
> > I guess it must be possible to provide somewhere the path where
> > binaries, classes etc. reside.
> 
> See
> 
> :help latex-suite
> 
> and search for CompileRule. In particular, the section on
> 
> Tex_CompileRule_format
This is what I was looking for.

> provides information on how to specify which command to use to build
> your document. You can specify your format directly, and you can
> probably create a map to easily switch settings as needed.
> 
> I'm a little skeptical about whether you have a good reason to have
> three different distributions. I'm also surprised that TeXShop is
> bundled with its own distribution.
> 
> Ideally, you should just be using MacTeX (which is just TeXLive for Mac):
Actually I mostly only use MacTeX. I think the ones from ports and fink
got installed since other applications from fink / ports depend on then.
Maybe I could have avoided this making them use MacTeX, but I was too
lazy for this.

Letting Tex_CompileRule_pdf point to /usr/texbin/pdflatex is fine for me for the moment.

Thanks, 
Udo

Re: [Vim-latex-devel] path to latex

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

> I trying to use latex on Mac OS X with MacVim. I have more than one
> LaTeX distribution installed (comming from macports, fink and the one
> comming with TexShop). How can I tell vim-latex-suite which one to use?
> I guess it must be possible to provide somewhere the path where
> binaries, classes etc. reside.

See

:help latex-suite

and search for CompileRule. In particular, the section on

Tex_CompileRule_format

provides information on how to specify which command to use to build
your document. You can specify your format directly, and you can
probably create a map to easily switch settings as needed.

I'm a little skeptical about whether you have a good reason to have
three different distributions. I'm also surprised that TeXShop is
bundled with its own distribution.

Ideally, you should just be using MacTeX (which is just TeXLive for Mac):

http://www.tug.org/mactex/

Moreover, if you use MacTeX, it will add a panel to your Mac system
configuration that allows you to quickly switch which distribution you
are pointing to (it just adjusts a symlink from /usr/texbin to the
appropriate distribution). If I remember correctly, it only supports a
couple of non-MacTeX alternatives. However, you may be able to use it as
inspiration for your own setup.

Likewise, you may be interested in this MacTeX FAQ question:

http://www.tug.org/mactex/faq/#qm03

Best --
Ted


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

[Vim-latex-devel] path to latex

[Udo H. <udo...@we...>]

Hello,

I trying to use latex on Mac OS X with MacVim. I have more than one
LaTeX distribution installed (comming from macports, fink and the one
comming with TexShop). How can I tell vim-latex-suite which one to use?
I guess it must be possible to provide somewhere the path where
binaries, classes etc. reside.

Best,
Udo

[Vim-latex-devel] compile fails if compiler/tex.vim isn't the first found file in runtimepath.

[Xavier W. <wea...@gm...>]

in the line 870 of main.vim:
runtime compiler/tex.vim

will fail when the vim-latex is installed into a directory that is not the
first entry in 'runtimepath', maybe use
        runtime! compiler/tex.vim

will be better.

[Vim-latex-devel] [ vim-latex-Bugs-3223395 ] Escaping in Tex_pack_updateall

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

Bugs item #3223395, was opened at 2011-03-18 19:43
Message generated for change (Tracker Item Submitted) made by tukss
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3223395&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: Philipp Edelmann (tukss)
Assigned to: Nobody/Anonymous (nobody)
Summary: Escaping in Tex_pack_updateall

Initial Comment:
The bug occurs when opening a TeX file which is not the .latexmain file in a directory whose path contains an asterisk or any other glob character which happens to expand to multiple paths.

The code in question is from packages.vim:
	if expand('%:p') != fname
		call Tex_Debug(':Tex_pack_updateall: sview '.Tex_EscapeSpaces(fname), 'pack')
		exe 'sview '.Tex_EscapeSpaces(fname)
	else
		call Tex_Debug(':Tex_pack_updateall: split', 'pack')
		split
	endif
		
	call Tex_ScanForPackages()
	q

The call to sview fails because Tex_EscapeSpaces doesn't escape the asterisk in the path. The error in verbose mode is:
    Error detected while processing function Tex_pack_updateall:
    line   29:
    E77: Too many file names

Because splitting the buffer fails, the following call to q closes the original buffer and therefore the instance of vim which was just opened. The user only sees vim close immediately with no error message.

A solution to this problem is to use fnameescape instead of Tex_EscapeSpaces because it properly escapes all characters not only spaces.

I think this problem could also occur at other places where Tex_EscapeSpaces is used in conjunction with asterisks in the path name. Maybe Tex_EscapeSpaces should use fnameescape internally. The problem might be that * expansion might be desired in certain places. I don't know if that is the case anywhere in latexsuite.

I attached a patch that fixes the problem for me.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3223395&group_id=52322

[Vim-latex-devel] [ vim-latex-Bugs-3219297 ] Add doc/tags to .gitignore file

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

Bugs item #3219297, was opened at 2011-03-17 09:41
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3219297&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: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Add doc/tags to .gitignore file

Initial Comment:
When including vim-latex as a submodule, generating the tags file results in a dirty submodule.

Adding doc/tags to the .gitignore file would solve this.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3219297&group_id=52322