Re: environment variable
Reinhard Kotucha <[email protected]>
| Newsgroups | gmane.comp.tex.tetex.general |
|---|---|
| Message-ID | <[email protected]> |
>>>>> "Oliver" == Oliver Grewe <[email protected]> writes: > [...] > when both users are ready, both will checkin with CVS (Concurrent > Versions System) their files and also their latex stuff ! > NOTE: When one of them wants to create a report on > machine-a/part-xy, he will need from part-x and part-y all > latex-files from the other user/users. He (this user) will do an > update in $HOME/machine-a/part-xy and should get all files which > user1 and user2 produced and cheked into CVS. > because he used the $HOME env-variable in the latex -files he is > now able to produce the report(s) for machine 'a' ! But $HOME does nothing else than to expand to /home/<username>. Suppose that everyone has its own $TEXMFHOME tree, it should then be sufficient to create a file "/home/olli/texmf/tex/generic/home.tex" which contains something like \def\HOME{/home/olli} Then in your document you can say \input{home} \input{\HOME/some-file} %% expands to \input{/home/olli/some-file} and the result should be the same as \input{$HOME/some-file} %% expands to \input{/home/olli/some-file} Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:[email protected] ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------