Topic: Collection of LaTeX tools (1 of 15), Read 70 times, 1 File Attachment
Conf: VEDIT Macro Library
From: Fritz Heberlein
Date: Thursday, October 30, 2003 01:03 PM

I have deleted my several LaTeX related contributions from webboard.
I replace the by a collection called vlatex.zip. It contains:


* A TeX Menu, which includes a couple of common LaTeX commands and the original Compile Menu

* related DI1 menus and Vdm's

* Vdm's to start Miktex and Yap, resp.

* Tex.syn: syntax highlighting

* Compiler support: latex.vcs, compile.cnf, and a c-init.vdm made up for use with LaTeX

* a sample help system dealing with issues not covered in the LaTeX manuals of Lamport and Samarin e.a. This is based on Christian Ziemski's DI1pager.vdm (contents still in german, english version coming soon)


Fritz

 
VLATEX.ZIP (38KB)

 


Topic: Collection of LaTeX tools (2 of 15), Read 53 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Sunday, November 23, 2003 12:53 PM

On 10/30/2003 1:03:48 PM, Fritz Heberlein wrote:
>I have deleted my several
>LaTeX related contributions
>from webboard.
>I replace the by a collection
>called vlatex.zip. It
>contains:
>
>
>* A TeX Menu, which includes a
>couple of common LaTeX
>commands and the original
>Compile Menu
>
>* related DI1 menus and Vdm's
>
>* Vdm's to start Miktex and
>Yap, resp.
>
>* Tex.syn: syntax highlighting
>
>* Compiler support: latex.vcs,
>compile.cnf, and a c-init.vdm
>made up for use with LaTeX
>
>* a sample help system dealing
>with issues not covered in the
>LaTeX manuals of Lamport and
>Samarin e.a. This is based on
>Christian Ziemski's
>DI1pager.vdm (contents still
>in german, english version
>coming soon)
>
Thanks Fritz,

for putting all this information at a single place.
Because of the wealth of all this information, I am going to install one at a time.

I have been using your various Miktex commands, although not the latest version. So, here things were as usual.


My first problem is your yap.vdm, which has been enhanced to treat the inverse search feature. Actually, the macro does seem to run fine, the Yap menu appears. In fact typing,
{File, Options, Inverse Search} I do get the Yap,s input dialog box. It gives me two fields. One is locked. The other has "%f%" and "%l%" typed in. It explains that "f" stands for filename and "l" stands for line number.

These are exactly the parametres that I have to transmit to Vedit, so I added vpw.exe into this field. More specifically, I entered
vpw.exe "%f% %l%".

I also did experiment with similar combinations bu could not hit it rigth. I have a hunch that I am missing something very simple.

Looking forward to hearing from you.

Thanks,

-peter.

 


Topic: Re: Collection of LaTeX tools (3 of 15), Read 55 times
Conf: VEDIT Macro Library
From: Fritz Heberlein
Date: Monday, November 24, 2003 07:48 AM

Peter:

> These are exactly the parametres that I have to transmit to Vedit, so
> I added vpw.exe into this field. More specifically, I entered vpw.exe
> "%f% %l%".

Please try

vpw %f -l%l

and add your vedit path before "vpw".

BTW, forward search will work correctly only with miktex version 2.2
or higer.

Fritz


--
Dr. Friedrich Heberlein, Akad. Direktor
Seminar für Klassische Philologie, KU Eichstaett-Ingolstadt
Universitaetsallee 1
D-85071 Eichstaett / Bayern

 


Topic: Re: Collection of LaTeX tools (4 of 15), Read 48 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Wednesday, November 26, 2003 06:08 AM

On 11/24/2003 7:48:17 AM, Fritz Heberlein wrote:
>Peter:
>

>> "%f% %l%".
>
>Please try
>
>vpw %f -l%l
>
>and add your vedit path before
>"vpw".
>

Thanks Fritz,

You were right about using the "quote delimeters".

I adapted your suggestion to:

c:\vedit\vpw -cgoto_line(%l) %f

This solved the problem. In other words, I inserted the Yap place holders into the Vedit command line invocation.

Now, I also have a better feeling of your contribution.
You treated the "Vedit instance" problem. In other words, I have to tell Vedit to open the new file in the same buffer
where I have started from.

Incidentally, what was Professor Ziemsky's reaction to your editing of the C-INIT.VDM macro?


Thnaks again,

-peter.

 


Topic: Collection of LaTeX tools (5 of 15), Read 53 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Sunday, November 30, 2003 02:42 PM

On 10/30/2003 1:03:48 PM, Fritz Heberlein wrote:


>* A TeX Menu, which includes a
>couple of common LaTeX
>commands and the original
>Compile Menu
>
>* related DI1 menus and Vdm's
>
>* Vdm's to start Miktex and
>Yap, resp.
>
>* Tex.syn: syntax highlighting
>
>* Compiler support: latex.vcs,
>compile.cnf, and a c-init.vdm
>made up for use with LaTeX
>
>* a sample help system dealing
>with issues not covered in the
>LaTeX manuals of Lamport and
>Samarin e.a. This is based on
>Christian Ziemski's
>DI1pager.vdm (contents still
>in german, english version
>coming soon)

Fritz,

I did succeed in incorporating your YAP.VDM into my latex menu. Now I can perform an inverse search in Yap!

Although this is only a small part of your macros, I think that it is a significant enhancement of the Vedit-Latex capabilities. Of course thanks to Ted as well for incorporating the instance command into Vedit.
(I also would like to tell Cristian Gerard that it was his macro that started me to think about Inverse Search in Vedit)

Finally, I would like to ask Ted to consider distributing your macros with one of the future releases of Vedit. May be you could combine all your Latex Macros into a, say, FH_LATEX.VDM. Then I would load this macro into one of my Text registers and call them individually as :Label:.
After all, these macros heavily rely on your LATEX.VCS.

PS: I made a harmless adaptation to your YAP.VDM. Specifically, I have replaced c:\vedit\user-mac by
|(USER_MACRO) .



Thanks again,

-peter.

 


Topic: Collection of LaTeX tools (6 of 15), Read 35 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Sunday, March 14, 2004 08:27 PM

On 10/30/2003 1:03:48 PM, Fritz Heberlein wrote:

>* Compiler support: latex.vcs,
>compile.cnf, and a c-init.vdm
>made up for use with LaTeX

Fritz and Christian,

I would like to report an error message that I got trying to compile a Tex file which did not have the .tex extension:

I got the Vedit Compiler Support Error, dialog_input_1 box, with the message;

An unexpected error occured. An error message may be visible..

Indeed, it said: CANNOT FIND |a:/|*.tex

I choose the continue option and after additional error messages, finally, I ended up with the
Latex Warning: Empty 'thebibliography environment' on input line 39.

Note that if I rename the file extension to .tex, The Dialog_Input_1 window does not appear. Your macro treats the Latex Warning in the usual manner.

Thanks and looking forward to hearing from you.

-peter.

 


Topic: Re: Collection of LaTeX tools (7 of 15), Read 31 times
Conf: VEDIT Macro Library
From: Fritz Heberlein
Date: Tuesday, March 16, 2004 09:29 AM

> Indeed, it said: CANNOT FIND |a:/|*.tex
[...]
> Note that if I rename the file extension to .tex, The
Dialog_Input_1 window does not appear.

This is the beginnig of the search code in latex.vcs; the ful code is

//
S("|{|<|a:/|*.tex:|d,| line|b}",#96+CASE+NOERR+COUNT,#97)
//

Therefore, there is no connection with the presence or absence of a
*.tex extension, which, if absent, is added by TeX automatically.

You might want to sent me your *.tex file; i will try to figure out
what's going on here.

Fritz


--

Dr. Friedrich Heberlein, Akad. Direktor
Seminar f. Klassische Philologie,
KU Eichstätt-Ingolstadt / Bayern
D-85071 Eichstaett

 


Topic: Re: Collection of LaTeX tools (8 of 15), Read 31 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Tuesday, March 16, 2004 10:27 AM

On 3/16/2004 9:29:56 AM, Fritz Heberlein wrote:
>> Indeed, it said: CANNOT FIND |a:/|*.tex
>[...]
>> Note that if I rename the file extension to .tex, The
>Dialog_Input_1 window does not
>appear.
>
>This is the beginning of the
>search code in latex.vcs; the
>full code is
>
>//
>S("|{|<|a:/|*.tex:|d,| >Warning:|*input
>line|b}",#96+CASE+NOERR+COUNT,
>#97)
>//
>
>Therefore, there is no
>connection with the presence
>or absence of a
>*.tex extension, which, if
>absent, is added by TeX
>automatically.
>
>You might want to sent me your
>*.tex file; i will try to
>figure out
>what's going on here.
>

Fritz,

Thanks for your kind offer of looking at my .tex file.
I shall upload it later.

At the same time, I would like to ask a question: Does the code segment |a:/|*.tex: include the .tex extension?
It seems to me it does.

I forgot to tell you that I also compiled my Tex template file, ggart2.tpl, using latex.bat. In other words, I typed,

latex ggart2.tpl.

Then I got a latex warning and full compiling. Then I looked at the ggart2.log file and there the extension was .tpl .


I vaguely remember some e-mail/webboard exchanges that we had some time ago. When both of us used emTeX. I also remember, that since emTeX automatically added the .tex extension it was important for Vedit to transmit the filename only. In short, I do not think that MikTeX automatically adds the .tex extension.

I shall check this after I get home. At the same time I wanted to answer your e-mail right away.


Thanks again for all your help.

-peter.



>Bayern
>D-85071 Eichstaett
>
>

 


Topic: Re: Collection of LaTeX tools (9 of 15), Read 37 times
Conf: VEDIT Macro Library
From: Fritz Heberlein
Date: Tuesday, March 16, 2004 11:22 AM

> At the same time, I would like to ask a question: Does the code
> segment |a:/|*.tex: include the .tex extension? It seems to me it
> does.

Yes, of course. But that search is done within vcs.tmp, the
redirected log file for your tex output (i.e., the original
.log). And since LaTeX adds the extension *.tex to any file
that comes without extension, any error or warning message in
vcs.tmp refers to an *.tex file.

Fritz


--

Dr. Friedrich Heberlein, Akad. Direktor
Seminar f. Klassische Philologie,
KU Eichstätt-Ingolstadt / Bayern
D-85071 Eichstaett

 


Topic: Re: Collection of LaTeX tools (10 of 15), Read 42 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Tuesday, March 16, 2004 04:22 PM

On 3/16/2004 11:22:42 AM, Fritz Heberlein wrote:
>> At the same time, I would like to ask a question: Does the code
>> segment |a:/|*.tex: include the .tex extension? It seems to me it
>> does.
>
>Yes, of course. But that
>search is done within vcs.tmp,
>the
>redirected log file for your
>tex output (i.e., the original
>.log). And since LaTeX adds
>the extension *.tex to any
>file

Fritz,

I believe that emTeX adds the extension *.tex. However, I do not believe that MiKTeX does it too.

I just did the following experiment. I took the Gratzer template file, and corrected the Latex Warning. Then I compiled the corrected file using your latex.vcs. It worked like a charm! Then I checked the redirected log file, vcs.tmp, and the extension of the input file/project file was the template extension .tpl. I called the corrected file ggart2_par.tpl. and I shall try to upload it.

I shall also try to upload the original file, ggart2.tpl. Compiling this original file using your latex.vcs results in the heavy error messages that I reported to you before.
Changing the extension to .tex allowed me to compile it with your latex.vcs again. That is to say, with a harmless Latex Warning message.

Looking forward to hearing from you.

-peter.

OOPS. I have trouble with the uploading. I shall try later.





>that comes without extension,
>any error or warning message
>in
>vcs.tmp refers to an *.tex
>file.
>
>Fritz
>
>
>--
>
>Dr. Friedrich Heberlein, Akad.
>Direktor
>Seminar f. Klassische
>Philologie,
>KU Eichstätt-Ingolstadt /
>Bayern
>D-85071 Eichstaett
>
>

 


Topic: Re: Collection of LaTeX tools (11 of 15), Read 33 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Wednesday, March 17, 2004 10:26 AM

On 3/16/2004 11:22:42 AM, Fritz Heberlein wrote:

And since LaTeX adds
>the extension *.tex to any
>file
>that comes without extension,
>any error or warning message
>in
>vcs.tmp refers to an *.tex
>file.

Fritz,

I just realized that in answering your previous e-mail I was a little bit careless. So, let me start all over. I redid my experiments and it turned out that the outcomes are independent of the particular Gratzer file. Here are the details:

I renamed my error free test.tex file to test.tpl. Then I compiled it with the help of C-COMPIl.VDM, which calls your latex.vcs file. This went fine. However, the filename in vcs.tmp did contain the .tpl extension. This seems to contradict your conclusion that "any error or warning message in vcs.tmp refers to a *.tex file" That is to say, it contradicts your conclusion using my setup. So, the next question is whether or not you can repeat this experiment with one of your files.

I also introduced an error into my test.tpl file and tried to compile it with the help of C-COMPIL.VDM. This time I did not get a vcs.tmp file so I could not look for either .tpl or .tex.


Since the Gratzer files which I previously uploaded convey no additional information, I am going to delete them.

Thanks and looking forward to hearing from you.

-peter.

 


Topic: Re: Collection of LaTeX tools (12 of 15), Read 41 times
Conf: VEDIT Macro Library
From: Fritz Heberlein
Date: Wednesday, March 17, 2004 12:24 PM

Peter:

unfortunately i don't know the external program you are using. I only
can tell what will happen if you compile your tex files the
"standard" way, using any of the current TeX distribution like
MikTeX, fptex, tetex .... All of them, as far as i know, use the same
compiler, which adds the extension ".tex" to any input file that
doesn't have an extension.

Please have a look at the following:

(1) Here are some files included in a master file called petron0.tex.
Please note the missing extension in the pathnames:

\include{f:/lva/autoren/petron/ws03/einleitung}
\include{f:/lva/autoren/petron/ws03/uebersicht}
\include{f:/lva/autoren/petron/ws03/gattung}

(2) Here is an extract from the log file petron0.log, redirected to
vcs.tmp. Please note that the pathname do have extensions now:

*** VCS Last Line = 1
This is TeX, Version 3.14159 (MiKTeX 2.1)
(F:/LVA/autoren/petron/ws03/petron0.tex)
(f:/lva/autoren/petron/ws03/einleitung.tex)
(f:/lva/autoren/petron/ws03/uebersicht.tex)
(f:/lva/autoren/petron/ws03/gattung.tex)

These extensions are searched for by latex.vcs.

I have no idea what your external program does. If you compile your
document in the way provided by the vedit compiler support, i.e.
using (a) the command

#124=Reg_Free
Call_File(#124,"|(HOME)/compile/c-compil.vdm")
Reg_Empty(#124)

as integrated in my tex.mnu, (b) a properly set up compile.cnf
containing the DEFCOMPILE specifications, e.g.,

DEFCOMPILE=latex --src-specials --c-style-errors
--interaction=nonstopmode --max-print-line=200
--output-directory=d:\texout -proj.ext

your document will compile successful.

Happy TeXing,

Fritz
--

Dr. Friedrich Heberlein, Akad. Direktor
Seminar f. Klassische Philologie,
KU Eichstätt-Ingolstadt / Bayern
D-85071 Eichstaett

 


Topic: Re: Collection of LaTeX tools (13 of 15), Read 44 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Wednesday, March 17, 2004 07:14 PM

On 3/17/2004 12:24:00 PM, Fritz Heberlein wrote:
>Peter:
>
>unfortunately i don't know the
>external program you are
>using. I only
>can tell what will happen if
>you compile your tex files the
>"standard" way, using any of
>the current TeX distribution
>like
>MikTeX, fptex, tetex .... All
>of them, as far as i know, use
>the same
>compiler, which adds the
>extension ".tex" to any input
>file that
>doesn't have an extension.


Thanks Fritz or the extended instructions.
I sure need them!

I do use MikTeX 2.3 and so far as I know I have taken over all of your stuff.

I am sorry about the confusion that I have caused concerning
your "adds the extension .tex to any input file that doesn't have an extension" statement.I already apologized for this in my previous message. In the message preceding it, I missed your assumption that "doesn't have an extension" . In the meantime I checked out your complete statement and verified that it is correct in my set up.

I am sending this message from work, from a Unix system.
I do not have my PC with me and I can not double check the rest of your conditions. I studied them and I believe that
they are all satisfied.

Now would you do me a favor: Change the .tex extension of one of your latex files to, say, .ltx. Then compile the resulting file and see what happens.

Finally let me describe the vcs.tmp file that I get if I compile my test.tpl file: The second line contains the full pathname of the input file/project file including the extension .tpl. Just to show you that I did my homework here is a more specific description of this line. It is similar to the right side of the DEFCOMPILE= string in my c:\vedit\compile.cnf file. The difference is that "latex"
has been replaced by "Miktex" and "-proj.ext has been replaced by "c:/texvols/test.tpl". (Here the forward slash is not a typo.)

OOPS: I forgot to tell you that I am using Win/98 second edition.

Thanks again,

-peter.

 


Topic: Re: Collection of LaTeX tools (14 of 15), Read 53 times
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Thursday, March 18, 2004 06:30 AM

On 3/17/2004 12:24:00 PM, Fritz Heberlein wrote:
>Peter:
>
>Please have a look at the
>following:
>
>(1) Here are some files
>included in a master file
>called petron0.tex.
>Please note the missing
>extension in the pathnames:
>
>\include{f:/lva/autoren/petron
>/ws03/einleitung}
>\include{f:/lva/autoren/petron
>/ws03/uebersicht}
>\include{f:/lva/autoren/petron
>/ws03/gattung}
>
>(2) Here is an extract from
>the log file petron0.log,
>redirected to
>vcs.tmp. Please note that the
>pathname do have extensions
>now:
>
>*** VCS Last Line = 1
>This is TeX, Version 3.14159
>(MiKTeX 2.1)
>(F:/LVA/autoren/petron/ws03/pe
>tron0.tex)
>(f:/lva/autoren/petron/ws03/ei
>nleitung.tex)
>(f:/lva/autoren/petron/ws03/ue
>bersicht.tex)
>(f:/lva/autoren/petron/ws03/ga
>ttung.tex)
>
>These extensions are searched
>for by latex.vcs.
>
>
>Happy TeXing,

Fritz,

I am studying the second half of your message. Here, I do find a real discrepency between our two set ups!

So, I created a template of my tex file, and called it rejto.tpl. I am going to upload this short file.

I have also made some progress in compiling my "trouble file" within Vedit. Specifically, I did press the Debug button in the Dialog_Input_1 box with the "unexpected error message". This put me into Command mode and I pressed "v".
To my pleasant surprise, I got the vcs.tmp file. I renamed this file to "par_1_vcs.tmp" and I shall also try to upload it. Note that in this file I have no ".tex" extensions at all!

Finally, I have to amend my previous e-mail about my "vcs.tmp" file. I thought that the complete command line sent to Miktex by Vedit, was on the second line of vcs.tmp.
This is wrong: only the filename with extension was on this line.

The complete command line came from the Vedit progress window! This complete command line was a big help for me in trying to diagnose my problem. So, a big thank you to all of you at Vedit for this window. (I consider you as part of the honorary Vedit team)



Thanks again for all your help.

-peter

 


Topic: Re: Collection of LaTeX tools (15 of 15), Read 38 times, 2 File Attachments
Conf: VEDIT Macro Library
From: Peter Rejto
Date: Thursday, March 18, 2004 12:23 PM

Trying to upload.

 
Rejto vcs.tmp file for problem TeX file
  Rejto template for TeX files.