Re: [PATCH] texdoc and xdvi (Re: [Q] gzipped documentations)

2000-02-12 Thread Olaf Weber

Sebastian Rahtz writes:
 Olaf Weber writes:

 Attached patch works with those lines in texmf.cnf:
   TEXDOCSSUFFIX = :.dvi:.ps:.html:.txt
   TEXDOCSCOMPRESS = :.gz:.bz2:.zip:.Z
   TEXDOCEXT = {$TEXDOCSSUFFIX}{$TEXDOCSCOMPRESS}

 texmf.cnf should not be abused as general-purpose info system. Several
 things which used to be in texmf.cnf for some time have been moved
 to mktex.cnf. This was a good thing.

 For what it's worth, I'd like to clean it up some more, and restrict
 texmf.cnf to path information, while other program parameters go to
 something like web2c.cnf.

 Can you or Thomas expound a bit on this? What is wrong with texmf.cnf
 having all sorts of stuff, a Single Stop Shop?

There is my sense of neatness (which is something where tastes
definitely differ).  But for example, an upgrade may have to replace
the texmf.cnf.  The path information part is usually the one with most
local adaptations, so this would make it easier to keep that in place.

-- 
Olaf Weber

Do not meddle in the affairs of sysadmins,
for they are quick to anger and have no need for subtlety.



Re: [PATCH] texdoc and xdvi (Re: [Q] gzipped documentations)

2000-02-09 Thread Sebastian Rahtz

Denis Barbier writes:
  For maximal customization, i prefer reading variables from texmf.cnf.
  Attached patch works with those lines in texmf.cnf:
TEXDOCSSUFFIX = :.dvi:.ps:.html:.txt
TEXDOCSCOMPRESS = :.gz:.bz2:.zip:.Z
TEXDOCEXT = {$TEXDOCSSUFFIX}{$TEXDOCSCOMPRESS}

not a good idea, on TeX Live at least. you do
 texdoc longtable
and it finds longtable.html from the Williams Catalogue *before*
longtable.dvi.bz2. You need to try .dvi.bz2 immediately after .dvi

  There is one funny drawback: temporary file is removed before viewer is
  launched, but this should be easy to fix.
sounds a bit fundamental...

Sebastian



Re: [PATCH] texdoc and xdvi (Re: [Q] gzipped documentations)

2000-02-09 Thread Sebastian Rahtz

Denis Barbier writes:
  Every (te)TeX distribution has its preferred documentation format.

well, its often dictated by the package author, but no matter

  Order in which formats are parsed is actually hardcoded in texdoc, which
  i do not like. To fit your needs you only have to edit texmf.cnf without
  patching texdoc, e.g.
 TEXDOCSSUFFIX = :.html:.dvi:.doc

But if my preference is .dvi followed by .html, and my .dvi files are
compressed, I will get the .html before the .dvi.gz. That is surely
counter-intuitive?


 There is one funny drawback: temporary file is removed before viewer is
 launched, but this should be easy to fix.
   sounds a bit fundamental...
  
  Yes, but it will imply some changes in current texdoc's behaviour, so
  Thomas will decide what is _the_ answer.

I think Thomas has publicly said that he is *NOT* developing teTeX at
present; it would be nice to get a working solution on our own...

Sebastian



Re: [PATCH] texdoc and xdvi (Re: [Q] gzipped documentations)

2000-02-08 Thread Thomas Esser

 Content-Disposition: attachment; filename=texdoc.patch

Interesting, but IMHO texdoc should do the decompression and not assume
that the viewer does this. ghostview doesn't. acroread dosn't (compressing
pdf does not make sense, but one can never be sure what people do).

 Content-Disposition: attachment; filename=xdvi.patch

Interesting, but one should not assume that the "tempfile" program is
always available. One can prevent symlink attacks by creating a 700-mode
directory and putting temp files there. This is portable, tempfile is not
portable.

If cleanup is done using event handlers (trap), then the event handler
should already be set before the temp files are created...

Thomas