|
On 7/1/2002 2:55:12 AM, Fritz wrote
>there should be no problem
>with that. The simplest way is
>to copy the
>relevant sections from the
>compile.mnu to your
>custom.mnu.
Following your suggestion I learned that the {Misc, Compiler support} menu command loads the COMPILE.VDM macro. Hence, I can edit it to my needs.
>You may
>want to check my solution
>(appended here below).
>
Yes, I would very much like to check your tex.mnu. However, your previous message is garbled. I take this had it. Could you please send it again?
>You should make sure, however,
>that you have only one
>tools.mnu (or
>whatever the name of your
>tools menu is). If you have
>one in, say,
>vedit/macros and another in
>vedit/user-mac you will run
>into problems
>(experto crede :))
>
I thought that Vedit looks for the *.mnu file
first, in the vedit\user-mac directory and second, in the home directory and third, in the \vedit\macros directory.
Do you think that there is a similar phylosophy with the COMPILE.CNF file?
Certainly, when I left an old COMPILE.CNF file in my data directory, E:\TeXVols,
Vedit got confused. Then Vedit loaded
the home directory configuration file, which was perfectly OK. So, I was at a loss.
May be Vedit routinely checks for configuration files in the current directory?
It would be nice to know.
I certainly shall repeat this unintended experiment. Then I shall add a personal note
to COMPILE.CNF, saying that "please remove
any old COMPLIE.CNF file from the current directory".
A more ambitious project would be to ask Vedit to do this checking. I guess Vedit in this case would be the C-INIT.VDM macro. At least, it seemed to me that my error messages came from this macro. This macro was recently enhanced by Christian. So, I hope that Christian will have a reaction to this.
Thanks to both of you.
-peter
|
|