[texworks] Project Management type stuff

Paul A Norman paul.a.norman at gmail.com
Fri Oct 15 23:17:03 CEST 2010


Thank you Reinhard,

This has been put forward to me on another forum...

> Putting it more crudely, if you specify a relative, absolute, or partial
> path in a \usepackage command, LaTeX will try to obey it, and won't use
> texmf.cnf.

However from what you are saying, it would appear that a flag has to
be set in  texmf.cnf?

And I take it that  texmf.cnf. is an essential part of all LaTeX distros?

Is it concievable that a dedicated procedure in C++ level of TeXWorks
could, if it proves necessary, alter these flags at a User's specific
request?
Or would that conceivably interfere with their LaTeX disto's tools settings?

Paul

On 16 October 2010 02:04, Reinhard Kotucha <reinhard.kotucha at web.de> wrote:
> On 15 October 2010 Paul A Norman wrote:
>
>  >    a) can packages be accessed by \usepackage{} on relative paths from
>  > the document's directory,
>
> It depends on the setting of openin_any in texmf.cnf.
>
> % Allow TeX \openin, \openout, or \input on filenames starting with `.'
> % (e.g., .rhosts) or outside the current tree (e.g., /etc/passwd)?
> % a (any)        : any file can be opened.
> % r (restricted) : disallow opening "dotfiles".
> % p (paranoid)   : as `r' and disallow going to parent directories, and
> %                  restrict absolute paths to be under $TEXMFOUTPUT.
> openout_any = p
> openin_any = a
>
> Regards,
>  Reinhard
>
> --
> ----------------------------------------------------------------------------
> Reinhard Kotucha                                      Phone: +49-511-3373112
> Marschnerstr. 25
> D-30167 Hannover                              mailto:reinhard.kotucha at web.de
> ----------------------------------------------------------------------------
> Microsoft isn't the answer. Microsoft is the question, and the answer is NO.
> ----------------------------------------------------------------------------
>



More information about the texworks mailing list