On 08/01/2010 21:49, Frank Küster wrote:
> (and similar for TEXMFSYSCONFIG). But that implies that user-changed
> files there (even files that would be created by texconfig, but have not
> yet been) will be respected. And I know from discussions with Thomas
> that the tree was always intended as
Reinhard Kotucha wrote:
> On 5 January 2010 Manuel Pégourié-Gonnard wrote:
>
> > Hum, that's probably because I always forget they exist :-) Do you
> > see any practical use case for configuration files here? I'm
> > slightly reluctant to add yet another level of configuration files
> > for t
On 6 January 2010 Norbert Preining wrote:
> On Di, 05 Jan 2010, Reinhard Kotucha wrote:
>> AFAIK these directories contain only files generated by a program.
> Well not only, tlmgr stores data there (updmap.cfg),
Norbert, this is exactly what I expect. I said that these directories
contain
On Di, 05 Jan 2010, Reinhard Kotucha wrote:
> AFAIK these directories contain only files generated by a program.
Well not only, tlmgr stores data there (updmap.cfg), and every user
can copy stuff there and overrule other files.
But Manuel, no problem if you don't want to add it, that is less
a pr
On 05/01/2010 18:08, Manuel Pégourié-Gonnard wrote:
> I'll probably do that.
>
See texdoc 0.62, just commited to TeX Live. Now support_zipped is completely
gone, the relevant option is actually zipext_list: by default it is empty. You
just need to set it to whatever extensions you need, and define
On 5 January 2010 Manuel Pégourié-Gonnard wrote:
> On 05/01/2010 16:54, Norbert Preining wrote:
>> --
>> One more thing: I was a bit puzzled that texdoc does not look into
>> TEXMFSYSCONFIG or TEXMFCONFIG /texdoc/texdoc.cnf
>> In upstream texlive that would be
>> .../
6 matches
Mail list logo
