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

Re: [Vim-latex-devel] More about F9 completion in multi-directory situation

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

> Thanks Ted, but actually I don't even compile to ps =). dvi for editing,
> pdf for final submissions for me.

In that case, get rid of the ps compile target. You'll never need it.

(interesting that you never have to worry about the latex vs pdflatex 
image problem... I suppose you always keep a pdflatex-compatible version 
around and a latex-compatible version around manually (I have a Makefile 
that automatically converts as needed))

--Ted

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

Re: [Vim-latex-devel] More about F9 completion in multi-directory situation

[Ng Oon-Ee <ng...@gm...>]

On Wed, 2011-02-23 at 18:39 -0500, Ted Pavlic wrote:
> > let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
> 
> On an unrelated subject, you should probably add -G0 after the -Ppdf...
> 
> dvips -Ppdf -G0 -o $*.ps $*.dvi
> 
> That will help prevent any problems when converting from CMR fonts to 
> Adobe fonts (but the -G0 must come after the -Ppdf).
> 
> Additionally, I notice that you do not have a FormatDependency line:
> 
> let g:Tex_FormatDependency_ps = 'dvi,ps'
> 
> Without that line, if you try to build a ps, the initial dvi will never 
> be built.
> 
> See
> 
> :help compiler-dependency
> 
> or search for FormatDependency under:
> 
> :help latex-suite
> 
> Best --
> 
> --Ted
> 
Thanks Ted, but actually I don't even compile to ps =). dvi for editing,
pdf for final submissions for me.

Re: [Vim-latex-devel] More about F9 completion in multi-directory situation

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

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

On an unrelated subject, you should probably add -G0 after the -Ppdf...

dvips -Ppdf -G0 -o $*.ps $*.dvi

That will help prevent any problems when converting from CMR fonts to 
Adobe fonts (but the -G0 must come after the -Ppdf).

Additionally, I notice that you do not have a FormatDependency line:

let g:Tex_FormatDependency_ps = 'dvi,ps'

Without that line, if you try to build a ps, the initial dvi will never 
be built.

See

:help compiler-dependency

or search for FormatDependency under:

:help latex-suite

Best --

--Ted

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

Re: [Vim-latex-devel] More about F9 completion in multi-directory situation

[Ng Oon-Ee <ng...@gm...>]

On Wed, 2011-02-23 at 08:12 +0100, Gerd Wachsmuth wrote:
> > INSTRUCTIONS:-
> >
> > Test 1-
> > 1. edit chap1/chap1.tex
> > 2. Type \cite{ then press F9
> > 3. Should show up as 0 results.
> > 4. Run :edit ../main.tex
> > 5. Type \cite{ then press F9
> > 6. Results show. Undo everything, then :edit chap1/chap1.tex
> > 7. Typing \cite{ then pressing F9 now shows results.
> >
> > Test 2-
> > Step 1-4 as above
> > 5. Type \cite{marr then press F9
> > 6. Only one of the two results show. Undo everything,
> > then :edit /chap1/chap1.tex
> > 7. Typing \cite{ then pressing F9 only shows the previous result (ie.
> > not both results as in test 1 above)
> 
> I can't reproduce this. Staying in the main directory, both
> 
> gvim chap1/chap1.tex
> 
> and
> 
> cd chap1/; gvim chap1.tex
> 
> does not result in this bug. Which version of the latex-suite do you use? 
> What variables do you set?
> 
> Regards
> Gerd

I'm using a git version, grabbed it on 16th Feb 2011. I've got a fairly
long .vimrc, should I attach it here? My tex.vim is

let g:Tex_DefaultTargetFormat = 'dvi'
let g:Tex_MultipleCompileFormats = 'dvi,pdf'
let g:Tex_ViewRule_ps = 'gnome-open'
let g:Tex_ViewRule_pdf = 'okular'
let g:Tex_ViewRule_dvi = 'okular'
let g:Tex_UseEditorSettingInDVIViewer = 1
let g:Tex_CompileRule_dvi = 'latex -interaction=nonstopmode
--src-specials $*'
let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
let g:Tex_CompileRule_pdf = 'pdflatex -interaction=nonstopmode
-synctex=1 $*'
set iskeyword+=:

[Vim-latex-devel] [ vim-latex-Patches-3189887 ] More customizations of envmacros

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

Patches item #3189887, was opened at 2011-02-23 08:12
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3189887&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: More customizations of envmacros

Initial Comment:
With this patch, envmacros.vim allows more customizations.

1.
let g:Tex_EnvLabelprefix_equation = "eq:"
=> labels in equations have the prefix eq:

this works for:
figure,table,theorem,definition,lemma,proposition,corollary,assumption,remark,equation,eqnarray,align,multline


2.
let g:Tex_EnvEndWithCR = 0
=>
completed environments end with:

\end{env-type}
<++>

instead of

\end{env-type}<++>

This saves one CR ;)


3.
let g:Tex_LabelAfterContent = 0
=>
Put the label before the content of an environment, e.g.

\begin{equation}
        \label{eq:<++>}
        <++>
\end{equation}
<++>


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

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

Re: [Vim-latex-devel] Patch: More customizations of envmacros

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

> I noticed that Till has been reviewing a lot of patches on the Patch tracker 
> on the Vim-LaTeX website at Sourceforge. It might be a nice idea to post this 
> there too (it's too bad that tracker doesn't post to the list -- to give the 
> best of both worlds).
I was not aware of this possibility - I will post it on sf, too.

Re: [Vim-latex-devel] F9-Completion, was: Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

Hi,

On Tue, 22 Feb 2011, Simon Quittek wrote:

> Hello Gerd,
>
> I think, your ideas are very good, and since I use/would like to use F9
> much more often, I welcome improvement!
> Just to make sure to understand from the users view: instead of typing
> "\eqref{eq<F9>" and then looking through the list to find the right 
label
> (e.g. "eq:maxwell"), you type the number "(2.4)<F9>" (which has label
> "eq:maxwell" before compilation into the aux-file) and it is expanded
> automatically into "\eqref{eq:maxwell}".
>
> As far as I see, if you want to ref an equation this way, you have to do
> the compilation first, and the numbers probably will change after each
> compilation. In case of a replacement, this means you need to have:
> 1) the up-to-date pdf/dvi file open all the time and
> 2) knowledge of the numbers, even if they are far away in the document.
>
> For this reasons I would _strongly_ prefer to be able to choose which 
way
> to use at all times.
> Your method is very convenient, nonetheless and I would very much like 
to
> use it!
With my aux-based completion, both methods work:
\eqref{eq:max<F9> => \eqref{eq:maxwell}
(4.1) => \eqref{eq:maxwell}


On Tue, 22 Feb 2011, Ted wrote:

> It's too restrictive for me to need to have the PDF visible at every 
time I edit. It's nice sometimes to see a numbered equation, realize you
> want a reference to it, and quickly add a reference without figuring out 
its label. However, normally when I'm referring to equations in-line
> with text, I'm writing that text soon after I generated the equation 
label (and in close proximity). Moreover, I use a label that has some
> useful meaning. For example, a reference to Newton's Second Law could be 
"eq:n2l", and I wouldn't have to open up a PDF to find it.
See above, you can also use the label-based variant, but there is no line 
of
context of the tex-file shown.


A comparision: \ref{<F9> with the current tex-based completion results in
something like

2. Modeling of Solid mechanics<<<1
>      sec:introduction_mechanics               <Dissertation.tex>
:        \chapter{Modeling of Solid mechanics}
     2.1. Linear Elasticity<<<2
>          sec:elasticity               <Dissertation.tex>
:            \section{Linear Elasticity}
>          fig:sketch_of_deformation            <Dissertation.tex>
:            Sketch of the undeformed and deformed domain.
>          eq:definition_of_gradient            <Dissertation.tex>
:

the aux-based completion produces:

2 Modeling of Solid mechanics<<<1
>  sec:introduction_mechanics
:    chapter.2
   2.1 Linear Elasticity<<<2
>    sec:elasticity
:      section.2.1
>    fig:sketch_of_deformation
:      figure.2.1
>    eq:definition_of_gradient
:      (2.1)

The aux-based completion does not output the filenames, since I didn't see 
any
need for them.


> So I can see some cases where the aux-based completion would be 
convenient, but I think most people would need the tex-based completion 
most of
> the time.
After giving some clearance, that you still use the labels for completion, 
did
you still think, that one needs the tex-based completion?

> A lot of people (especially when journals setup theorem-like 
environments for you) won't know the counter name. I suppose they could 
assume
> they know the first letter of the counter and use F9 to figure out the 
rest<?>.
Yes, that works.

Regards

Re: [Vim-latex-devel] More about F9 completion in multi-directory situation

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

> INSTRUCTIONS:-
>
> Test 1-
> 1. edit chap1/chap1.tex
> 2. Type \cite{ then press F9
> 3. Should show up as 0 results.
> 4. Run :edit ../main.tex
> 5. Type \cite{ then press F9
> 6. Results show. Undo everything, then :edit chap1/chap1.tex
> 7. Typing \cite{ then pressing F9 now shows results.
>
> Test 2-
> Step 1-4 as above
> 5. Type \cite{marr then press F9
> 6. Only one of the two results show. Undo everything,
> then :edit /chap1/chap1.tex
> 7. Typing \cite{ then pressing F9 only shows the previous result (ie.
> not both results as in test 1 above)

I can't reproduce this. Staying in the main directory, both

gvim chap1/chap1.tex

and

cd chap1/; gvim chap1.tex

does not result in this bug. Which version of the latex-suite do you use? 
What variables do you set?

Regards
Gerd

Re: [Vim-latex-devel] Patch: More customizations of envmacros

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

I noticed that Till has been reviewing a lot of patches on the Patch 
tracker on the Vim-LaTeX website at Sourceforge. It might be a nice idea 
to post this there too (it's too bad that tracker doesn't post to the 
list -- to give the best of both worlds).

(with regard to this patch, at first glance, it makes sense to be a 
helpful addition)

--Ted

On 02/22/2011 07:52 AM, Gerd Wachsmuth wrote:
> Hi,
>
> with this patch, envmacros.vim allows more customizations.
>
> 1.
> let g:Tex_EnvLabelprefix_equation = "eq:"
> => labels in equations have the prefix eq:
>
> this works for:
> figure,table,theorem,definition,lemma,proposition,corollary,assumption,remark,equation,eqnarray,align,multline
>
>
>
> 2.
> let g:Tex_EnvEndWithCR = 0
> =>
> completed environments end with:
>
> \end{env-type}
> <++>
>
> instead of
>
> \end{env-type}<++>
>
> This saves one CR ;)
>
>
> 3.
> let g:Tex_LabelAfterContent = 0
> =>
> Put the label before the content of an environment, e.g.
>
> \begin{equation}
> \label{eq:<++>}
> <++>
> \end{equation}
> <++>
>
>
> Feel free to comment.
>
>
>
> ------------------------------------------------------------------------------
> Index, Search&  Analyze Logs and other IT data in Real-Time with Splunk
> Collect, index and harness all the fast moving IT data generated by your
> applications, servers and devices whether physical, virtual or in the cloud.
> Deliver compliance at lower cost and gain new business insights.
> Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
>
>
>
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

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

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

Re: [Vim-latex-devel] F9-Completion, was: Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

> In which situation you need to stick to the old tex-based completion? I
> used my aux-based completion since one or two months and I never missed
> the tex-based completion.

It's too restrictive for me to need to have the PDF visible at every 
time I edit. It's nice sometimes to see a numbered equation, realize you 
want a reference to it, and quickly add a reference without figuring out 
its label. However, normally when I'm referring to equations in-line 
with text, I'm writing that text soon after I generated the equation 
label (and in close proximity). Moreover, I use a label that has some 
useful meaning. For example, a reference to Newton's Second Law could be 
"eq:n2l", and I wouldn't have to open up a PDF to find it.

So I can see some cases where the aux-based completion would be 
convenient, but I think most people would need the tex-based completion 
most of the time.

>> I'm a little confused (I haven't looked at the script) about how the
>> completer picks the \*ref you want. Some people are going to use the
>> \*refs provided by the cleveref package. Others (like me) are going to
>> use \autoref nearly everywhere but other variants (\Autoref) in some
>> places and \ref in some other cases (after "and", for example), and I
>> would never ever use \eqref. How could I configure?
> Currently, this can't be customized, but it is surely possible.

So long as...

\ref{thm.4.5<F9>
\autoref{thm.4.5<F9>
\ScoobyDooRef{thm.4.5<F9>

all leave their macros in tact, then it wouldn't be a problem. People 
who don't like your choices can type their own choices and just use F9 
to fill in the labels.

>> For one, how is the average user going to know for sure
>> exactly which AUX name to use (thm.4.5 vs theorem.4.5)?
> You have to use the name of the latex counter.

A lot of people (especially when journals setup theorem-like 
environments for you) won't know the counter name. I suppose they could 
assume they know the first letter of the counter and use F9 to figure 
out the rest<?>.

> Because I can type (2.2) faster than equation.2.2.

But, as you say, the counter.number still works.

>> Furthermore, I think I would much rather type...
>>
>> \autoref{theorem.4.5<F9>}
>>
>> and have that replaced with
>>
>> \autoref{thm:a_nice_theorem}
> This does work.

And leaves the macro (whatever it is called) in tact? Does the macro 
have to end in "ref" or will the completion be activated for any curly 
brace?

--Ted


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

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

[Vim-latex-devel] Input completion undesired behavior

[Thomas K. <thk...@gm...>]

Hi,

I think I just found a rather unpleasant behavior in vim-latex.

I have a multiple-file setup.

thesis.tex
Chapters/
     doc1.tex
     doc2.tex
tables/
     1.tex
     2.tex
     3.tex
figures/
     1.pdf
     2.pdf
     3.pdf

I am in doc1.tex. my pwd is ROOT.

I type (C is the cursor in insert mode, delimiterMate automatically 
closes the braces i type, hence the "{}"):
\input{C}

Now pressing F9 opens a __Choose_File__ window and shows me the files of 
the ROOT/Chapters. pwd switched to ROOT/Chapters as well.
I select "../", move down to "tables/" and select it. last i select 
1.tex. vim-latex replaces the cursor with "1.tex". the problem is 
though, that my pwd is now ROOT/Chapters.
Why is this a problem? Because other plugins pick up on the pwd (i.e. 
nerdtree, command-t,...) and I don't see a reason to change pwd in such 
a use case to be honest.

Best,
Thomas

Re: [Vim-latex-devel] F9-Completion, was: Multiple file latex projects, finds correct filename but doesn't compile in right directory?

[Simon Q. <sim...@gm...>]

Hello Gerd,

I think, your ideas are very good, and since I use/would like to use F9 
much more often, I welcome improvement!
Just to make sure to understand from the users view: instead of typing 
"\eqref{eq<F9>" and then looking through the list to find the right label 
(e.g. "eq:maxwell"), you type the number "(2.4)<F9>" (which has label 
"eq:maxwell" before compilation into the aux-file) and it is expanded 
automatically into "\eqref{eq:maxwell}".

As far as I see, if you want to ref an equation this way, you have to do 
the compilation first, and the numbers probably will change after each 
compilation. In case of a replacement, this means you need to have:
1) the up-to-date pdf/dvi file open all the time and
2) knowledge of the numbers, even if they are far away in the document.

For this reasons I would _strongly_ prefer to be able to choose which way 
to use at all times.
Your method is very convenient, nonetheless and I would very much like to 
use it!

All the best,
Simon

Gerd Wachsmuth wrote:
>> I can see how someone editing a single
>> document would often want to complete both ways.
> In which situation you need to stick to the old tex-based completion? I
> used my aux-based completion since one or two months and I never missed
> the tex-based completion.
>
> The only advantage of the tex-based completion is, that you see some
> neighbourhood (one line before or after) of the \label, but mostly this
> contained no information for me.
>
>
>>> Typing (3.4)<F9>   results in \eqref{eq:a_beautiful_equation}
>>
>> [ Note: The need for \eqref can be mitigated with varioref's
>> \labelformat and/or hyperref's \autoref. There is absolutely no reason
>> that equations need to be handled differently within the main LaTeX
>> content than any other reference. ]
>>
>>> Moreover, I also works for theorems etc. Typing theorem.4.5 results in
>>> \autoref{thm:a_nice_theorem}
>>
>> I'm a little confused (I haven't looked at the script) about how the
>> completer picks the \*ref you want. Some people are going to use the
>> \*refs provided by the cleveref package. Others (like me) are going to
>> use \autoref nearly everywhere but other variants (\Autoref) in some
>> places and \ref in some other cases (after "and", for example), and I
>> would never ever use \eqref. How could I configure?
> Currently, this can't be customized, but it is surely possible.
>
>> I also am confused about using "theorem.4.5" some places and "(3.4)"
>> other places.
> For referencing equations you type (equation.number). This does work also
> with (A.1) or (12.23c).
>
> For referencing something which is not an equation you type
> latex-counter-name.number, e.g. section.2 or subsection.2.12,...
>
>> For one, how is the average user going to know for sure
>> exactly which AUX name to use (thm.4.5 vs theorem.4.5)?
> You have to use the name of the latex counter.
>
>> And why the different handling of equations?
> Because I can type (2.2) faster than equation.2.2.
>
>> Furthermore, I think I would much rather type...
>>
>> \autoref{theorem.4.5<F9>}
>>
>> and have that replaced with
>>
>> \autoref{thm:a_nice_theorem}
> This does work.
>
>
> Gerd
>
> ------------------------------------------------------------------------------
> Index, Search&  Analyze Logs and other IT data in Real-Time with Splunk
> Collect, index and harness all the fast moving IT data generated by your
> applications, servers and devices whether physical, virtual or in the cloud.
> Deliver compliance at lower cost and gain new business insights.
> Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] More about F9 completion in multi-directory situation

[Ng Oon-Ee <ng...@gm...>]

On Tue, 2011-02-22 at 11:49 +0100, Gerd Wachsmuth wrote:
> > Sorry for being unclear, I was referring in the first paragraph to a
> > bug with using main.latexmain, which I fixed by using
> > main.tex.latexmain.
> >
> > My primary question (the rest of the email) was about a bug I
> > experienced when using main.tex.latexmain.
> 
> I can't reproduce this bug. Maybe you can poste a minimal (not) working 
> example? Maybe this bug is influenced by the settings of the variables 
> Tex_UseOutlineCompletion and Tex_UsePython.
> 
> Regards
> Gerd

Ah, didn't realize my previous email was reply to you only and not to
the list. Added the list back to CC.

Here's my minimal example. There's also a blank main.tex.latexmain.
Instructions at the bottom of the email.

main.tex

\documentclass{report}  
\usepackage{natbib}
\begin{document}
\input{chap1/chap1.tex}
\bibliographystyle{agsm}
\bibliography{thesisrefs}
\end{document}

chap1/chap1.tex

\chapter{Introduction}
\section{First section}

thesisrefs.bib

@techreport{marr_theory_1977,
	title = {A Theory of Human Stereo Vision.},
	author = {D. Marr and T. Poggio},
	month = nov,
	year = {1977}
},
@article{grimson_computer_1981,
	title = {A Computer Implementation of a Theory of Human Stereo Vision},
	volume = {292},
	journal = {Philosophical Transactions of the Royal Society of London.
Series B, Biological Sciences},
	author = {W. E. L. Grimson},
	month = may,
	year = {1981},
	pages = {217--253}
}


INSTRUCTIONS:-

Test 1-
1. edit chap1/chap1.tex
2. Type \cite{ then press F9
3. Should show up as 0 results.
4. Run :edit ../main.tex
5. Type \cite{ then press F9
6. Results show. Undo everything, then :edit chap1/chap1.tex
7. Typing \cite{ then pressing F9 now shows results.

Test 2-
Step 1-4 as above
5. Type \cite{marr then press F9
6. Only one of the two results show. Undo everything,
then :edit /chap1/chap1.tex
7. Typing \cite{ then pressing F9 only shows the previous result (ie.
not both results as in test 1 above)

Re: [Vim-latex-devel] F9-Completion, was: Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

> I can see how someone editing a single
> document would often want to complete both ways.
In which situation you need to stick to the old tex-based completion? I 
used my aux-based completion since one or two months and I never missed 
the tex-based completion.

The only advantage of the tex-based completion is, that you see some 
neighbourhood (one line before or after) of the \label, but mostly this 
contained no information for me.


>> Typing (3.4)<F9>  results in \eqref{eq:a_beautiful_equation}
>
> [ Note: The need for \eqref can be mitigated with varioref's
> \labelformat and/or hyperref's \autoref. There is absolutely no reason
> that equations need to be handled differently within the main LaTeX
> content than any other reference. ]
>
>> Moreover, I also works for theorems etc. Typing theorem.4.5 results in
>> \autoref{thm:a_nice_theorem}
>
> I'm a little confused (I haven't looked at the script) about how the
> completer picks the \*ref you want. Some people are going to use the
> \*refs provided by the cleveref package. Others (like me) are going to
> use \autoref nearly everywhere but other variants (\Autoref) in some
> places and \ref in some other cases (after "and", for example), and I
> would never ever use \eqref. How could I configure?
Currently, this can't be customized, but it is surely possible.

> I also am confused about using "theorem.4.5" some places and "(3.4)"
> other places.
For referencing equations you type (equation.number). This does work also 
with (A.1) or (12.23c).

For referencing something which is not an equation you type 
latex-counter-name.number, e.g. section.2 or subsection.2.12,...

> For one, how is the average user going to know for sure
> exactly which AUX name to use (thm.4.5 vs theorem.4.5)?
You have to use the name of the latex counter.

> And why the different handling of equations?
Because I can type (2.2) faster than equation.2.2.

> Furthermore, I think I would much rather type...
>
> \autoref{theorem.4.5<F9>}
>
> and have that replaced with
>
> \autoref{thm:a_nice_theorem}
This does work.


Gerd

[Vim-latex-devel] Patch: More customizations of envmacros

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

Hi,

with this patch, envmacros.vim allows more customizations.

1.
let g:Tex_EnvLabelprefix_equation = "eq:"
=> labels in equations have the prefix eq:

this works for:
figure,table,theorem,definition,lemma,proposition,corollary,assumption,remark,equation,eqnarray,align,multline


2.
let g:Tex_EnvEndWithCR = 0
=>
completed environments end with:

\end{env-type}
<++>

instead of

\end{env-type}<++>

This saves one CR ;)


3.
let g:Tex_LabelAfterContent = 0
=>
Put the label before the content of an environment, e.g.

\begin{equation}
 	\label{eq:<++>}
 	<++>
\end{equation}
<++>


Feel free to comment.

Re: [Vim-latex-devel] F9-Completion, was: Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

> That's no big deal - the recognizing of the other commands can be easily
> added - just post your problems.

I have no problems with <F9> as I have no desire to ever need such a 
feature.

> Now I will comment my customizations. I patched/rewrote outline.py. Now,
> it
> looks at the aux-file and not at the tex-file. If I write some
> mathematical
> text, then I think "I need equation (3.4)".  Up to now, I needed to look
> in the
> tex-file for the corresponding label. With my patched version, I can do
> the
> following:

This is a very different feature, and so it seems like it should be 
either added as a separate completer or merged (as opposed to replacing) 
with the existing F9 completion. I can see how someone editing a single 
document would often want to complete both ways.

> Typing (3.4)<F9>  results in \eqref{eq:a_beautiful_equation}

[ Note: The need for \eqref can be mitigated with varioref's 
\labelformat and/or hyperref's \autoref. There is absolutely no reason 
that equations need to be handled differently within the main LaTeX 
content than any other reference. ]

> Moreover, I also works for theorems etc. Typing theorem.4.5 results in
> \autoref{thm:a_nice_theorem}

I'm a little confused (I haven't looked at the script) about how the 
completer picks the \*ref you want. Some people are going to use the 
\*refs provided by the cleveref package. Others (like me) are going to 
use \autoref nearly everywhere but other variants (\Autoref) in some 
places and \ref in some other cases (after "and", for example), and I 
would never ever use \eqref. How could I configure?

I also am confused about using "theorem.4.5" some places and "(3.4)" 
other places. For one, how is the average user going to know for sure 
exactly which AUX name to use (thm.4.5 vs theorem.4.5)? And why the 
different handling of equations?

Furthermore, I think I would much rather type...

\autoref{theorem.4.5<F9>}

and have that replaced with

\autoref{thm:a_nice_theorem}

So I think the script could do more by doing less... and that might make 
it play very nice with existing F9 completion (that searches through the 
TeX).

--Ted

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

Re: [Vim-latex-devel] More about F9 completion in multi-directory situation

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

On Tue, 22 Feb 2011, Ng Oon-Ee wrote:

> In a previous thread I mentioned that using main.latexmain breaks <F9>
> completion, where main.tex.latexmain fixes it.
>
> Having used this more in actual writing, I've come across buggy
> behaviour while editing subfiles (chap1/chap1.tex for example), where
> F9 would give an empty list.
>
> Here's the sequence of events:-
>
> 1. Edit chap1/chap1.tex, try F9, doesn't work
> 2. Edit main.tex, try F9, works
> 3. Edit chap1/chap1.tex again, try F9, works
> 4. Try F9 again some time later in chap1/chap1.tex, does not work anymore.
>
> It seems editing main.tex 'caches' the result somehow. If I place
> chap1 in the same directory as main.tex there's no problem, but that
> simply adds to the clutter (I'm doing a PhD thesis, this thing is
> going to grow VERY big esp with all the picture subfolders etc)
>
> Does anyone else on this list have the same workflow as I do
> (multi-directory using .tex.latexmain AND uses F9 completion). Ted is
> obviously an expert but he doesn't use the feature =).

I think, the problem is that Tex_GetMainFileName() returns

/absolute/path/main

and not

/absolute/path/main.tex


Why do you use 'main.latexmain' and not 'main.tex.latexmain'?
Maybe you can use the variable g:Tex_MainFileExpression, see 
ftplugin/latex-suite/main.vim, function Tex_GetMainFileName(...).


Regards
Gerd

Re: [Vim-latex-devel] F9-Completion, was: Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

On Tue, 22 Feb 2011, Ng Oon-Ee wrote:

> On Tue, Feb 22, 2011 at 3:23 PM, Gerd Wachsmuth
> <ger...@ma...> wrote:
>> Hi,
>>
>> I use the F9-completion very often and feel to make some advertising ;)
>> I patched the outline.py, such that it offers a greater gain for me. But
>> first I will take up Ted's arguments.
>
> Interesting work, not immediately useful for me, but you never know.
>
> Any reason why your patches aren't submitted upstream?
Because I did not publish them _yet_. I will prepare several patches in 
the next days.


I forgot one question:
Should my new aux-based completion _replace_ the old tex-based completion 
or should it be offered as a new _alternative_, choosable by the user???

Regards
Gerd

Re: [Vim-latex-devel] dev directory

[Germain V. <ger...@un...>]

Hi

In a terminal, in the ~/dev directory if I do 

"pdflatex mytexfile.tex" => no problem

I open mytexfile.tex with gvim and hit \ll => nothing append 

I open mytexfile.tex with gvim and hit ":!pdflatex mytexfile.tex" it
works.

I look at swp files or vim error file in my ~ directory but I do not
find anything.

Usually I put that line in my .vimrc file :
let g:Tex_CompileRule_pdf="pdflatex -shell-escape
-interaction=nonstopmode $*"

I tried also that one but it do not change anything :

let g:Tex_CompileRule_pdf="pdflatex $*"

Germain 


-------- Message initial --------
De: Mike Richman <ri...@um...>
À: Germain Vallverdu <ger...@un...>
Cc: vim...@li...
<vim...@li...>
Sujet: Re: [Vim-latex-devel] dev directory
Date: Mon, 21 Feb 2011 11:25:26 -0500

On Mon, Feb 21, 2011 at 11:06 AM, Germain Vallverdu
<ger...@un...> wrote:
> Hi,
>
> First thanks a lot for your vim-latex plugins.
>
> I had got a strange behavior. My OS is an linux ubuntu. In my home
> directory I have a directory named "dev" where I put current jobs which
> are not achieved. If I write latex file inside the "dev" directory the
> compilation abort without any error message. It just seems to start and
> stop just at begin. Latex file like .log .aux or other are not modified.
> I do not know if the name of the directory is the origin but I do not
> have that problem in neither other directory ... If y copy my latex
> source in another directory or in a subdirectory of the directory "dev"
> it works well.
>
> But at the end, I can simply rename my directory :)
>
> Thanks
>
> Germain
>

Hi Germain,

That is strange behavior.  I created a directory ~/dev, wrote a
minimal LaTeX input, and it compiles fine on both the command line and
in gvim with \ll.

What happens if you try running "latex" or "pdflatex" on your source
code from the command line?

-Mike Richman

-- 
Maître de Conférence
Université de Pau et des pays de l'Adour
Institut Pluridisciplinaire de Recherche sur l'Environnement et les Matériaux
Équipe de Chimie Physique
email  : ger...@un...
Tel    : 05 59 40 78 51
page   : http://gvallver.perso.univ-pau.fr

[Vim-latex-devel] More about F9 completion in multi-directory situation

[Ng Oon-Ee <ng...@gm...>]

In a previous thread I mentioned that using main.latexmain breaks <F9>
completion, where main.tex.latexmain fixes it.

Having used this more in actual writing, I've come across buggy
behaviour while editing subfiles (chap1/chap1.tex for example), where
F9 would give an empty list.

Here's the sequence of events:-

1. Edit chap1/chap1.tex, try F9, doesn't work
2. Edit main.tex, try F9, works
3. Edit chap1/chap1.tex again, try F9, works
4. Try F9 again some time later in chap1/chap1.tex, does not work anymore.

It seems editing main.tex 'caches' the result somehow. If I place
chap1 in the same directory as main.tex there's no problem, but that
simply adds to the clutter (I'm doing a PhD thesis, this thing is
going to grow VERY big esp with all the picture subfolders etc)

Does anyone else on this list have the same workflow as I do
(multi-directory using .tex.latexmain AND uses F9 completion). Ted is
obviously an expert but he doesn't use the feature =).

Re: [Vim-latex-devel] F9-Completion, was: Multiple file latex projects, finds correct filename but doesn't compile in right directory?

[Ng Oon-Ee <ng...@gm...>]

On Tue, Feb 22, 2011 at 3:23 PM, Gerd Wachsmuth
<ger...@ma...> wrote:
> Hi,
>
> I use the F9-completion very often and feel to make some advertising ;)
> I patched the outline.py, such that it offers a greater gain for me. But
> first I will take up Ted's arguments.

Interesting work, not immediately useful for me, but you never know.

Any reason why your patches aren't submitted upstream?

[Vim-latex-devel] F9-Completion, was: Multiple file latex projects, finds correct filename but doesn't compile in right directory?

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

Hi,

I use the F9-completion very often and feel to make some advertising ;)
I patched the outline.py, such that it offers a greater gain for me. But 
first I will take up Ted's arguments.

> > Additionally \citep, \citet, \citeauthor, etc... Not sure if they 
would
> > match whatever pattern triggers the F9 completion... But I never use
> > \cite (in favor of the natbib variaties) and almost never use \ref (in
> > favor of hyperref's \autoref), and so F9 is potentially unhelpful.
That's no big deal - the recognizing of the other commands can be easily 
added - just post your problems.

> Moreover, doesn't F9 depend on a Python script? One of the big reasons I
> use Vim is that I can wall myself off from depending on other tools (and
> maximize my portability).
For me it is no problem that F9 depends on Python. I use my ViM 
configuration at three linux machines, all offering Python in ViM. Does 
Python+ViM works in
Windows?

> So I guess those are my reasons why completion doesn't concern me...
>
> -) F9 is uncomfortably far from any other key on the keyboard... would
> have preferred a command-mode combination, maybe...
You guessed it already - remapping is everything ;)

> -) Questionable support for \autoref (and custom variants, like
> \Autoref, \Autorefs, and \autorefs)
>
> -) Questionable support for natbib \citep, \citet, and friends
>
> -) Dependence on Python
See above.


Now I will comment my customizations. I patched/rewrote outline.py. Now, 
it
looks at the aux-file and not at the tex-file. If I write some 
mathematical
text, then I think "I need equation (3.4)".  Up to now, I needed to look 
in the
tex-file for the corresponding label. With my patched version, I can do 
the
following:

Typing (3.4)<F9> results in \eqref{eq:a_beautiful_equation}

Moreover, I also works for theorems etc. Typing theorem.4.5 results in
\autoref{thm:a_nice_theorem}

You can find these patch in my github-vim-configuration
https://github.com/gerw/vim-conf-gerw.  You need the files
bundle/vim-latex-suite/ftplugin/latex-suite/{auxoutline.py,texviewer.vim}. 
I
the next days I may publish a patch for latex-suite, depending on the 
response
here.

Gerd

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

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

>>         That's valuable clutter though. There are BBL files in there to
>> inspect/change; there are AUX files for other tools to use; etc. Not
>> only that, having the AUX available allows for quicker edits later.
>> Imagine you have a large book that takes a few seconds each pass... If
>> you changed a single typo somewhere, you wouldn't want to run every pass
>> again. So I guess one man's trash is... :)
>
> Are you saying you inspect these files by hand, regularly?  I almost
> never have, and I never change them manually.  So keeping them around,
> but out of sight, seems desirable.

	When crafting customized BST files for journals with strange 
conventions (and no natbib-compatible BST provided), it is instructive 
to take a look at the BBL. Moreover, there are plenty of tools 
(authorindex, for example, and other things you can do with makeindex) 
that are not presently integrated into Vim-LaTeX. My own build 
environment uses them (and thus uses the files).

	Most importantly, on my large projects, it would be ridiculous to 
delete the auxiliary files every time as it would greatly increase the 
build time. Plus, it would make \includeonly impractical (which is 
another reason why the -jobname solution makes more sense to me if you 
really can't stand the auxiliary files... but I don't mind having extra 
files in my project directory; it's a project directory after all).

(I know that you copy your .build/* files into the working directory 
before your DVI is built, but that is going to cause problems on the 
second or third times your DVI gets rebuilt... because it will squash 
the updated aux files in the working directory with the old copies from 
.build... so your solution needs tweaking (see comments below))

(plus, I think your solution breaks forward searching that requires the 
availability of source specials to the PDF viewer you are using... and 
there's no easy way to deal with that without adjusting ViewRules)

> I've tried to configure this before, but had no luck.  Based on
> latex-suite.txt, I thought the following would do the trick:
>
> let g:Tex_DefaultTargetFormat='pdf'
> let g:Tex_MultipleCompileFormats='dvi,ps,pdf'

This is not correct. You only want to do multiple compilations on the 
dvi. So set:

g:Tex_MultipleCompileFormat='dvi'

The dependency line (below) will run your ps and pdf conversion as 
needed after compiling multiple times. You only need to include pdf in 
MultipleCompileFormat if you want to run pdflatex multiple times. You 
are using latex->dvips->ps2pdf, and so you only care about running latex 
multiple times (to generate the right DVI).

[ Sometimes it is easier to debug these things when you run \ll in vim 
(as opposed to gvim) where it's easier to see the junk that dumps to the 
console. ]

> let g:Tex_FormatDependency_pdf='dvi,ps,pdf'
> let g:Tex_CompileRule_dvi='mkdir -p .build&&  cp .build/* . ;'
>              \.'latex -interaction=nonstopmode -shell-escape $*.tex'

Because latex may be run multiple times in a row, you need to copy the 
aux files back to .build after the latex. For example (replace the "ETC" 
as necessary):

let g:Tex_CompileRule_dvi='mkdir -p .build&&  cp .build/* .;'
              \.'latex -interaction=nonstopmode -shell-escape $*.tex'
              \.'&& cp $*.aux $*.bbl $*.ETC $*.ETC .build'

That way you don't squash updated aux files.

> let g:Tex_CompileRule_ps='dvips -P pdf -q  $*.dvi&&  rm -f $*.dvi'

I like to keep the DVI file around just in case there's a strange 
DVI->PDF conversion issue that I need to investigate (e.g., CMR->Adobe 
font conversion issues, which can often be eliminated by changing your 
dvips line to include -G0 and -Ppdf (I forget the correct order though; 
see "man dvips" and on-line))).

> let g:Tex_CompileRule_pdf='ps2pdf $*.ps'
>              \.'&&  rm -f $*.ps'
>              \.'&&  mv *.aux *.bbl *.bl *.blg *.lof *.log *.lot *.nav *.out '
>              \.'      *.snm *.toc .build/'
>
> But when I set it this way, it just compiles the dvi file and then
> stops.  What am I missing?

You might want to change each * to $*. However, you're still missing aux 
files like ".bm" that you'd get with (e.g.) powerdot presentations. And 
you're missing the aux files generated by authorindex... and any other 
indexing package you use (glossaries, etc.). It's hard to hit all of the 
aux files considering that each package can generate new aux files. So 
it's hard to mask them all off. Instead, it might be better to move 
EVERYTHING into .build and then move the stuff you want to keep (e.g., 
tex, eps, and pdf) back...

With those tweaks, your configuration works for me.

--Ted

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

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

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

Hi Ted,

On Mon, Feb 21, 2011 at 12:18 PM, Ted Pavlic <te...@te...> wrote:
> Mike --
>
>> I always sort of just took the auxiliary files for granted, but now I
>> like the idea of avoiding the clutter.
>
>        That's valuable clutter though. There are BBL files in there to
> inspect/change; there are AUX files for other tools to use; etc. Not
> only that, having the AUX available allows for quicker edits later.
> Imagine you have a large book that takes a few seconds each pass... If
> you changed a single typo somewhere, you wouldn't want to run every pass
> again. So I guess one man's trash is... :)

Are you saying you inspect these files by hand, regularly?  I almost
never have, and I never change them manually.  So keeping them around,
but out of sight, seems desirable.

>> let g:Tex_DefaultTargetFormat='pdf'
>> let g:Tex_MultipleCompileFormats='pdf'
>> let g:Tex_CompileRule_pdf='mkdir -p .build'
>
> Does that solution still allow LaTeX to automatically run BibTeX and
> makeindex as needed? It seems like it would break BBL/index generation. <?>

Good point, in fact it does break BibTeX et al.

>
> Because you're doing dvi->ps->pdf (as everyone should be (at least those
> who don't mind some of the (usually minor) issues with using
> transparency in EPS images)), it seems like there would be a better way.
> You can configure LaTeX to do the dvi,ps,pdf sequence for you, but you
> can add your cleanup stuff to the PDF rule. That way your AUX files
> stick around for Vim-LaTeX, and they disappear only at the very end when
> the final PDF is produced.

I've tried to configure this before, but had no luck.  Based on
latex-suite.txt, I thought the following would do the trick:

let g:Tex_DefaultTargetFormat='pdf'
let g:Tex_MultipleCompileFormats='dvi,ps,pdf'
let g:Tex_FormatDependency_pdf='dvi,ps,pdf'
let g:Tex_CompileRule_dvi='mkdir -p .build && cp .build/* . ;'
            \.'latex -interaction=nonstopmode -shell-escape $*.tex'
let g:Tex_CompileRule_ps='dvips -P pdf -q  $*.dvi && rm -f $*.dvi'
let g:Tex_CompileRule_pdf='ps2pdf $*.ps'
            \.'&& rm -f $*.ps'
            \.'&& mv *.aux *.bbl *.bl *.blg *.lof *.log *.lot *.nav *.out '
            \.'      *.snm *.toc .build/'

But when I set it this way, it just compiles the dvi file and then
stops.  What am I missing?

>
> Just a thought...
> --Ted
>
> --
> Ted Pavlic <te...@te...>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>

Re: [Vim-latex-devel] Able to do compilation in a sub-directory?

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

Mike --

> I always sort of just took the auxiliary files for granted, but now I
> like the idea of avoiding the clutter.

	That's valuable clutter though. There are BBL files in there to 
inspect/change; there are AUX files for other tools to use; etc. Not 
only that, having the AUX available allows for quicker edits later. 
Imagine you have a large book that takes a few seconds each pass... If 
you changed a single typo somewhere, you wouldn't want to run every pass 
again. So I guess one man's trash is... :)

	Having said that, the "jobname" option discussed earlier is a nice 
compromise. LaTeX still has the AUX files available tucked away out of 
sight, and so subsequent builds are efficient while the main working 
directory is relatively clean.

> let g:Tex_DefaultTargetFormat='pdf'
> let g:Tex_MultipleCompileFormats='pdf'
> let g:Tex_CompileRule_pdf='mkdir -p .build'

Does that solution still allow LaTeX to automatically run BibTeX and 
makeindex as needed? It seems like it would break BBL/index generation. <?>

Because you're doing dvi->ps->pdf (as everyone should be (at least those 
who don't mind some of the (usually minor) issues with using 
transparency in EPS images)), it seems like there would be a better way. 
You can configure LaTeX to do the dvi,ps,pdf sequence for you, but you 
can add your cleanup stuff to the PDF rule. That way your AUX files 
stick around for Vim-LaTeX, and they disappear only at the very end when 
the final PDF is produced.

Just a thought...
--Ted

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