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

[Vim-latex-devel] question mark

[yuejun y. <yj...@gm...>]

Hi
when i input a question mark (?) in macvim, it will be automatically replaced by a dollar sign ($). anyone knows how this happens? thanks.
YJ

Re: [Vim-latex-devel] citation completion goes to wrong window with vsplit

[Gerd W. <ger...@ma...>]

I think some bug still remains in the official latex-suite. I tested only 
my version. When Tex_WordComplete is invoked, the window number is not 
restored. See also

https://github.com/gerw/vim-latex-suite/commit/5971587dfc9389fd688b267cc90455b604c3b301

Best Regards
Gerd

On Fri, 16 Nov 2012, Alessandro Pezzoni wrote:

> 2012/11/16 Gerd Wachsmuth <ger...@ma...>:
>> latex-suite does not have a version number (any more). So the question
>> reduces to "Where (and possibly when) did you get latex-suite from?".
>
> Well, he did say "as distributed under Fedora"...
> By looking for Fedora packages I came to this page [1] where, while
> it's not really clear how to get a version info from there, I found a
> link to their build script repository for vim-latex. There is a
> changelog in the build script, from which I gather that they use git
> snapshots. In particular, the one corresponding to the version
> Grossfield is using is:
>
> 1.8.23-6.20110214.1049-git089726a
>
> So he has a git snapshot from a bit more than one year and a half ago.
> By the way, there is a newer entry (in the script for Fedora 17, the
> current stable release) dated 2012-01-25 saying that they updated that
> one to:
>
> 1.8.23-7.20120125.768-git8b62284
>
> I don't have any idea about the issue at hand, though.
>
> Alessandro
>
> [1] https://admin.fedoraproject.org/pkgdb/acls/name/vim-latex?_csrf_token=75695c0b53d7e1dbefa6eca5638f5eb988da891e
>
>
>

Re: [Vim-latex-devel] citation completion goes to wrong window with vsplit

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

On Fri, Nov 16, 2012 at 06:02:20PM +0100, Alessandro Pezzoni wrote:
> 2012/11/16 Gerd Wachsmuth <ger...@ma...>:
> > latex-suite does not have a version number (any more). So the question
> > reduces to "Where (and possibly when) did you get latex-suite from?".

> So he has a git snapshot from a bit more than one year and a half ago.
> By the way, there is a newer entry (in the script for Fedora 17, the
> current stable release) dated 2012-01-25 saying that they updated that
> one to:
> 
> 1.8.23-7.20120125.768-git8b62284

There will be an updated package in the updates-testing repository soon:
https://admin.fedoraproject.org/updates/vim-latex-1.8.23-9.20121116.784.git1c17b37.fc17

Regards
Till

Re: [Vim-latex-devel] citation completion goes to wrong window with vsplit

[Alessandro P. <ale...@la...>]

2012/11/16 Gerd Wachsmuth <ger...@ma...>:
> latex-suite does not have a version number (any more). So the question
> reduces to "Where (and possibly when) did you get latex-suite from?".

Well, he did say "as distributed under Fedora"...
By looking for Fedora packages I came to this page [1] where, while
it's not really clear how to get a version info from there, I found a
link to their build script repository for vim-latex. There is a
changelog in the build script, from which I gather that they use git
snapshots. In particular, the one corresponding to the version
Grossfield is using is:

1.8.23-6.20110214.1049-git089726a

So he has a git snapshot from a bit more than one year and a half ago.
By the way, there is a newer entry (in the script for Fedora 17, the
current stable release) dated 2012-01-25 saying that they updated that
one to:

1.8.23-7.20120125.768-git8b62284

I don't have any idea about the issue at hand, though.

Alessandro

[1] https://admin.fedoraproject.org/pkgdb/acls/name/vim-latex?_csrf_token=75695c0b53d7e1dbefa6eca5638f5eb988da891e

Re: [Vim-latex-devel] citation completion goes to wrong window with vsplit

[Gerd W. <ger...@ma...>]

latex-suite does not have a version number (any more). So the question 
reduces to "Where (and possibly when) did you get latex-suite from?".

Gerd

On 11/16/2012 02:50 PM, Raniere Gaia Silva wrote:
> Gerd,
> sorry for the stupid question, but how I can get the latex-suite version?
>
> Raniere
>
> On Fri, Nov 16, 2012 at 10:57 AM, Gerd Wachsmuth
> <ger...@ma...> wrote:
>> For me this works as expected. Which version of latex-suite do you use?
>>
>> On 11/16/2012 01:44 PM, Alan Grossfield wrote:
>>> When I write longish latex documents, I often break them into pieces
>>> (using \input) and keep multiple files open using gvim's vsplit
>>> command. I've noticed that if I do this and use F9 to invoke
>>> completion (for example on a \cite{}) the text is always inserted in
>>> the leftmost window, regardless of which window I invoked the
>>> completion from.  If the same file is opened in both windows, it
>>> seems to work correctly, and it works correctly if the completion
>>> command is invoked from the left side window.  It's only if the
>>> command is invoked from a different window that this breaks.
>>
>>
>> ------------------------------------------------------------------------------
>> Monitor your physical, virtual and cloud infrastructure from a single
>> web console. Get in-depth insight into apps, servers, databases, vmware,
>> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
>> Pricing starts from $795 for 25 servers or applications!
>> http://p.sf.net/sfu/zoho_dev2dev_nov
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] citation completion goes to wrong window with vsplit

[Raniere G. S. <r.g...@gm...>]

Gerd,
sorry for the stupid question, but how I can get the latex-suite version?

Raniere

On Fri, Nov 16, 2012 at 10:57 AM, Gerd Wachsmuth
<ger...@ma...> wrote:
> For me this works as expected. Which version of latex-suite do you use?
>
> On 11/16/2012 01:44 PM, Alan Grossfield wrote:
>> When I write longish latex documents, I often break them into pieces
>> (using \input) and keep multiple files open using gvim's vsplit
>> command. I've noticed that if I do this and use F9 to invoke
>> completion (for example on a \cite{}) the text is always inserted in
>> the leftmost window, regardless of which window I invoked the
>> completion from.  If the same file is opened in both windows, it
>> seems to work correctly, and it works correctly if the completion
>> command is invoked from the left side window.  It's only if the
>> command is invoked from a different window that this breaks.
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] citation completion goes to wrong window with vsplit

[Gerd W. <ger...@ma...>]

For me this works as expected. Which version of latex-suite do you use?

On 11/16/2012 01:44 PM, Alan Grossfield wrote:
> When I write longish latex documents, I often break them into pieces
> (using \input) and keep multiple files open using gvim's vsplit
> command. I've noticed that if I do this and use F9 to invoke
> completion (for example on a \cite{}) the text is always inserted in
> the leftmost window, regardless of which window I invoked the
> completion from.  If the same file is opened in both windows, it
> seems to work correctly, and it works correctly if the completion
> command is invoked from the left side window.  It's only if the
> command is invoked from a different window that this breaks.

Re: [Vim-latex-devel] citation completion goes to wrong window with vsplit

[Raniere G. S. <r.g...@gm...>]

Hi Alan,
the same problem you report have been reported some time ago by Jonas
but I think no one have found a solution.

Raniere

> On Tue, Jul 10, 2012 at 11:45 AM, Jonas Diemer <di...@gm...> wrote:
> > Hi,
> >
> > I usually have two windows open (project plugin and main text). When I
> > do a F9 completion (ref/cite), the completed text is erraneously
> > pasted into the wrong window (the project window).
> >
> > How do I fix this?
> >
> > Regards
> > Jonas
> >
> > ------------------------------
> ------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Vim-latex-devel mailing list
> > Vim...@li...
> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

On Fri, Nov 16, 2012 at 10:44 AM, Alan Grossfield <agr...@gm...> wrote:
> Hi,
>
> When I write longish latex documents, I often break them into pieces (using \input) and keep multiple files open using gvim's vsplit command. I've noticed that if I do this and use F9 to invoke completion (for example on a \cite{}) the text is always inserted in the leftmost window, regardless of which window I invoked the completion from.  If the same file is opened in both windows, it seems to work correctly, and it works correctly if the completion command is invoked from the left side window.  It's only if the command is invoked from a different window that this breaks.
>
> I realized this is a bit of a corner case (and overall I love vim-latex), but this is a bit of a nuisance.
>
> vim: 7.3.315 (as distributed under Fedora)
> vim-latex: 1.8.23-6 (as distributed under Fedora)
>
> Alan
> ___________________________________
> Dr. Alan Grossfield
> Assistant Professor
> Department of Biochemistry and Biophysics
> University of Rochester Medical Center
> 610 Elmwood Ave, Box 712
> Rochester, NY 14642
> Phone: 585 276 4193
> http://membrane.urmc.rochester.edu
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

[Vim-latex-devel] citation completion goes to wrong window with vsplit

[Alan G. <agr...@gm...>]

Hi,

When I write longish latex documents, I often break them into pieces (using \input) and keep multiple files open using gvim's vsplit command. I've noticed that if I do this and use F9 to invoke completion (for example on a \cite{}) the text is always inserted in the leftmost window, regardless of which window I invoked the completion from.  If the same file is opened in both windows, it seems to work correctly, and it works correctly if the completion command is invoked from the left side window.  It's only if the command is invoked from a different window that this breaks.

I realized this is a bit of a corner case (and overall I love vim-latex), but this is a bit of a nuisance.

vim: 7.3.315 (as distributed under Fedora)
vim-latex: 1.8.23-6 (as distributed under Fedora)

Alan
___________________________________
Dr. Alan Grossfield
Assistant Professor
Department of Biochemistry and Biophysics
University of Rochester Medical Center
610 Elmwood Ave, Box 712
Rochester, NY 14642
Phone: 585 276 4193
http://membrane.urmc.rochester.edu

Re: [Vim-latex-devel] [BUGREPORT] -output-directory isn't handled

[Alessandro P. <ale...@la...>]

I'm sorry, you clearly don't have pipes in your 'g:Tex_CompileRule_pdf'.
Still, I can confirm that latexsuite relies on vim's ':make' command.
In particular, it sets the 'makeprg' and 'errorformat' variables to
appropriate values, so that calling ':make' gives:
" [...]
4. The program given with the 'makeprg' option is
    started (default "make") with the optional
    [arguments] and the output is saved in the
    errorfile (for Unix it is also echoed on the
    screen).
5. The errorfile is read using 'errorformat'.
[...] "
(from vim's "quickfix.txt" help page)

If you set 'g:Tex_CompileRule_pdf' to 'xelatex
-interaction=nonstopmode $*' does vim behave as you expect? If not,
then this is probably an error parsing issue, otherwise this issue is
probably related to the output of your command.

Please, let me know, as I currently am unable to reproduce a xelatex
latexsuite setup.

Alessandro

Re: [Vim-latex-devel] [BUGREPORT] -output-directory isn't handled

[Alessandro P. <ale...@la...>]

2012/11/11 Christian Buhtz <ex...@gm...>:
> Devendra Ghate schrieb am Sonntag, 11. November 2012 um 14:45:
>> I understand the problem now. If you add an empty 'file.tex.latexmain'
>> (here file.tex is the one we are trying to compile), it should work. If you
>> already have the 'file.tex.latexmain', then there is some other issue.
>
> Sorry, now I didn't understand you? What is "latexmain"? Where should I
> put it? Why?

If you are not compiling a file called "main.tex", e.g. if you are
dividing your document in multiple files, then creating a (possibly
empty) file with the same name as your main file with a "latexmain"
suffix will tell latexsuite to compile that file. You can put settings
specific to your project in that file, too. For more info, see the
manual [1].

> xelatex create and use the output directory very well. There is no
> problem.
> The problem is that the vim-latexsuite doesn't find the log file because
> it is in the output-directory, too.

Probably (I'm not familiar with the code) latexsuite is relying on
parsing the output of your compilation command, which gets eaten up by
your last pipe. I think that latexsuite is actually relying on vim for
this, which is known to be quite flaky at supporting external programs
(by design). You can try to see if any of the methods suggested in
this [2] blog post let you do what you want in a cleaner way. Note
that the "rubber" link is dead, but you can find it on launchpad [3].
I will try to have a closer look at your issue later today, when I'll
have more time.

> The latexsuite doesn't give any shit on the use of -output-directory.
Please, keep in mind that people here are trying to help you (out of
their spare time).

Alessandro

[1] http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project.html
[2] http://phaseportrait.blogspot.it/2008/03/fixing-vim-latex-compiler-error.html
[3] https://launchpad.net/rubber

Re: [Vim-latex-devel] [BUGREPORT] -output-directory isn't handled

[Christian B. <ex...@gm...>]

Devendra Ghate schrieb am Sonntag, 11. November 2012 um 14:45:
> I understand the problem now. If you add an empty 'file.tex.latexmain'
> (here file.tex is the one we are trying to compile), it should work. If you
> already have the 'file.tex.latexmain', then there is some other issue.

Sorry, now I didn't understand you? What is "latexmain"? Where should I
put it? Why?

xelatex create and use the output directory very well. There is no
problem.
The problem is that the vim-latexsuite doesn't find the log file because
it is in the output-directory, too.
The latexsuite doesn't give any shit on the use of -output-directory.

Re: [Vim-latex-devel] [BUGREPORT] -output-directory isn't handled

[Devendra G. <dev...@gm...>]

Christian,

I understand the problem now. If you add an empty 'file.tex.latexmain'
(here file.tex is the one we are trying to compile), it should work. If you
already have the 'file.tex.latexmain', then there is some other issue.

Do let me know if this solves the problem.

Devendra


On 11 November 2012 17:03, Christian Buhtz <ex...@gm...> wrote:

> I am using vim-latexsuite on Kubuntu 12.10 32bit.
>
> This is my compile rule
> [.vimrc]
> let g:Tex_CompileRule_pdf='mkdir -p _out && xelatex -output-directory=_out
> -interaction=nonstopmode $* && mv _out/$*.pdf .'
> [/.vimrc]
>
> You see I am using -output-directory to bundle all output-files in a
> subdirectorie. It is needed because no human need this files. Only the
> machine itself (latex compiler, etc) need and use them. So they don't
> have to appear in my document directory.
>
> But as I see the latexsuite is not able to handle this.
> It didn't show me the error-log inside vim because it didn't find the
> error log.
> And maybe it take an negative effect on some other features of vim-latex
> that I doesn't know currently.
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>



-- 
Cheers,
Devendra.

Re: [Vim-latex-devel] [BUGREPORT] -output-directory isn't handled

[Devendra G. <dev...@gm...>]

Christian,

What do you mean by "not handle it"?

1. The output directory being generated?
2. Are the output PDF files being generated by xelatex in the output
directory?
3. OR the output files are not being moved to the current folder by mv.

Regards,
Devendra


On 11 November 2012 17:03, Christian Buhtz <ex...@gm...> wrote:

> I am using vim-latexsuite on Kubuntu 12.10 32bit.
>
> This is my compile rule
> [.vimrc]
> let g:Tex_CompileRule_pdf='mkdir -p _out && xelatex -output-directory=_out
> -interaction=nonstopmode $* && mv _out/$*.pdf .'
> [/.vimrc]
>
> You see I am using -output-directory to bundle all output-files in a
> subdirectorie. It is needed because no human need this files. Only the
> machine itself (latex compiler, etc) need and use them. So they don't
> have to appear in my document directory.
>
> But as I see the latexsuite is not able to handle this.
> It didn't show me the error-log inside vim because it didn't find the
> error log.
> And maybe it take an negative effect on some other features of vim-latex
> that I doesn't know currently.
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_nov
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>



-- 
Cheers,
Devendra.

[Vim-latex-devel] [BUGREPORT] -output-directory isn't handled

[Christian B. <ex...@gm...>]

I am using vim-latexsuite on Kubuntu 12.10 32bit.

This is my compile rule
[.vimrc]
let g:Tex_CompileRule_pdf='mkdir -p _out && xelatex -output-directory=_out -interaction=nonstopmode $* && mv _out/$*.pdf .'
[/.vimrc]

You see I am using -output-directory to bundle all output-files in a
subdirectorie. It is needed because no human need this files. Only the
machine itself (latex compiler, etc) need and use them. So they don't
have to appear in my document directory.

But as I see the latexsuite is not able to handle this.
It didn't show me the error-log inside vim because it didn't find the
error log.
And maybe it take an negative effect on some other features of vim-latex
that I doesn't know currently.

[Vim-latex-devel] [ vim-latex-Patches-3315923 ] Biblatex-Support: recognize addbibresource

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

Patches item #3315923, was opened at 2011-06-13 13:37
Message generated for change (Comment added) made by tmaas
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3315923&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: Kay Smarczewski ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Biblatex-Support: recognize addbibresource

Initial Comment:
When using biblatex the bib file is included by 
\addbibresource{library.bib}
Vim-Latex does not recognize this command and so the outline does not work.

The attached tiny patch replaces the search functions in the texviewer. It is a quite simple patch, just works for this special case and makes latex suite recognize the bib file.

The diff is against the actual git master branch.

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

>Comment By: Till Maas (tmaas)
Date: 2012-10-31 15:56

Message:
The patch is not taking into account that \addbibresource can have an
optional argument, e.g. used like \addbibressource[foo=bar]{baz}

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

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

[Vim-latex-devel] [ vim-latex-Patches-3316255 ] Included bibliography

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

Patches item #3316255, was opened at 2011-06-14 06:51
Message generated for change (Comment added) made by tmaas
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3316255&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: Kay Smarczewski ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Included bibliography

Initial Comment:
My bibliography is included by a custom .sty package or an usual included tex file. Latex-Suite only searches in the main file for bibliographies. Additionally, the patch extrends the bibfile search to include the biblatex commands addbibresource and printbibliography.

The attached patch implements this feature. It is rarely tested but it works for me. It is diffed against the current git master branch.

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

>Comment By: Till Maas (tmaas)
Date: 2012-10-31 15:55

Message:
The patch is not taking into account that \addbibresource can have an
optional argument, e.g. used like \addbibressource[foo=bar]{baz}

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

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

[Vim-latex-devel] [ vim-latex-Patches-3529927 ] \iota IMAP is missing from ftplugin/latex-suite/main.vim

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

Patches item #3529927, was opened at 2012-05-26 02:42
Message generated for change (Comment added) made by tmaas
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3529927&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: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Alessandro Pezzoni (donbex)
Assigned to: Nobody/Anonymous (nobody)
Summary: \iota IMAP is missing from ftplugin/latex-suite/main.vim

Initial Comment:
As per summary, the IMAP for \iota is missing. I am attaching a patch which fixes this (some time ago I tried submitting it to the mailing list as suggested on the vim-latex website, to no avail).

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

>Comment By: Till Maas (tmaas)
Date: 2012-10-31 15:44

Message:
applied with proper whitespace in 40be6efa1547c48764aa69e4e4a216d438f14688

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

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

Re: [Vim-latex-devel] [SPAM] docs: inverse searching requires shift-click in okular

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

On Fri, Oct 26, 2012 at 05:07:28PM -0400, Dan Stahlke wrote:
> I sent this message this morning but it was blocked as spam.  Second try 
> now...
> 
> In section 7.3 of the manual, titled "Inverse Searching", it says that 
> inverse search is triggered by double clicking in the PDF viewer.  In 
> fact, in okular you need to do a shift-click.  This took me an hour to 
> figure out, so maybe there should be a note about this in the docs.

Thank you, I just changed the documentation.

Regards
Till

[Vim-latex-devel] [ vim-latex-Patches-3573601 ] Changed begin center end center to centering in figures

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

Patches item #3573601, was opened at 2012-10-01 18:01
Message generated for change (Comment added) made by tmaas
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3573601&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: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: cako ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Changed begin center end center to centering in figures

Initial Comment:
In figure environments, \centering should be preferred over the center environment; the latter leaves unwated vertical space. The patch reflects this fact.

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

>Comment By: Till Maas (tmaas)
Date: 2012-10-31 10:53

Message:
commited in 2da4de8caf335aab6e0c29c9d1e582a52809279a

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

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

[Vim-latex-devel] Forward search with sumatrapdf

[Jorge R. <sk...@gm...>]

Hi all,

I previously thought it was necessary to patch vim-latex in order to
have forward search when using sumatrapdf in windows, but
after checking the options of sumatrapdf I realize that it is much
easier. I just defined a function:

 function! MyForwardSearch()
    let target = 'main.pdf'
    let cmd = g:SumatraPdfLoc .  " -reuse-instance -forward-search " .
expand('%:p') . " " . line('.') . " " . target
    let execString = 'silent! !start ' . cmd
    exe execString
  endfunction
  nnoremap <Leader>la :<C-U>call MyForwardSearch()<CR>

here
g:SumatraPdfLoc is a string to where sumatra is located "c:\....\sumatrapdf.exe"
target is the pdf that is produced

I couldn't find a way of doing this directly with vim-latex without
defining this function and mapping.
Would it be possible to incorporate similar changes to this directly
into vim-latex or vim-latex already supports this and I have something
wrong with my configuration?


Thanks,

Jorge

[Vim-latex-devel] Thank you for adding me

[Gemechu F. <gem...@gm...>]

In the installation of vim-latex from
 http://vim-latex.sourceforge.net/index.php?subject=download&title=Download
>From step 3 and 4
helptags ~/.vim/doc     (for *nix users)
 semicolon is missing and makes newbies  like me frustrated. It'll be
easier for us if you include it and write like this
*:*helptags ~/.vim/doc     (for *nix users)

Regards,
-- 
Gemechu Fanta,
Addis Ababa University, Physics Department
P. O. Box 1376
Tel:  +251-911-96-14-82 (mobile)
Skype: gemechufanta
E.mail: gem...@gm...
           gem...@gm...

"The truth will set you free."

[Vim-latex-devel] [BUG REPORT] <F5> in preamble causes error

[Christoph L. <c_l...@gm...>]

Hello everyone,

I've never filed a bug report to a mailing list before, so please
excuse this possibly poor report. I hope this issue has not been filed
before.


DESCRIPTION

Normally when being in the preamble of a LaTeX document and hitting F5,
a line "\usepackage{XXX}" is inserted. However I am shown the error
messages:

Error detected while processing function
Tex_FastEnvironmentInsert..Tex_package_from_line: line    9: E117:
Unknown function: Tex_pack_one

In the main part of a document everything is as expected, namely F5
inserts an environment.


SOURCE OF THE ERROR

The source of the error is, that I have set
let g:Tex_PackagesMenu = 0
in my ~/.vimrc file. When I leave this setting as it is, everything is
fine.

g:Tex_PackagesMenu = 0 prevents the script packages.vim from loading
due to the lines 9 to 13:

" avoid reinclusion.
if !g:Tex_PackagesMenu || exists('s:doneOnce')
	finish
endif
let s:doneOnce = 1


POSSIBLE FIX

I do not think that this behaviour is intended, so the easiest fix of
the problem would probably be to change the above lines to

" avoid reinclusion.
if exists('s:doneOnce')
	finish
endif
let s:doneOnce = 1


Best wishes
Christoph Lehmann

Re: [Vim-latex-devel] \label command location in macro

[Gerd W. <ger...@ma...>]

> So
> 1. Why latex-suite behaves differently on my computer other than the
> "default" behavior?
Because the documentation is not up to date.

> 2. Is there any way to let the \label<++> be placed ALWAYS at the first
> line of an environment? I know I can
> customize them one by one, but I have no idea how to deal with the new
> environment defined in a specific
> tex file.
Just put something like

let g:Tex_Env_theorem = 
"\\begin{theorem}\<CR>\label{<++>}\<CR><++>\<CR>\\end{theorem}\<CR><++>"

in your ~/.vim/ftplugins/tex.vim

Btw:
There is a patch that allows customization of these macros at sourceforge

http://sourceforge.net/tracker/?func=detail&aid=3189887&group_id=52322&atid=466458

However, it seems that nobody tends to incorporate these patches. (For 
this reason, I published my patched version of latex-suite on 
https://github.com/gerw/vim-latex-suite)


Regards
Gerd

[Vim-latex-devel] \label command location in macro

[Peng S. <sha...@gm...>]

Hi. I have been using latex-suite for a couple of years and until recently
I noticed an interesting problem about the location of \label{<++>} inserted
in a macro.

After I input "theorem", if I press <F5> then the following macro is 
inserted:

\begin{theorem}

     \label{<++>}
\end{theorem}<++>

I just noticed that in the online documentation
http://vim-latex.sourceforge.net/documentation/latex-suite/customizing-macros.html

it mentioned that

\begin{theorem}
      \label{<++>}<++>
\end{theorem}<++>

is indeed the "default" behavior of latex-suite.  I always prefer the 
"default" mode since
I am having a few problems when the label command is placed at the end 
of theorem environment.

So
1. Why latex-suite behaves differently on my computer other than the 
"default" behavior?
2. Is there any way to let the \label<++> be placed ALWAYS at the first 
line of an environment? I know I can
customize them one by one, but I have no idea how to deal with the new 
environment defined in a specific
tex file.

Thanks

-- 
Peng Shao