TCLUG Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [TCLUG:20364] slick way to read .dvi.gz
- To: tclug-list@mn-linux.org
- Subject: Re: [TCLUG:20364] slick way to read .dvi.gz
- From: Mike Hicks <hick0088@tc.umn.edu>
- Date: Sat, 12 Aug 2000 12:21:17 -0500
- Posted-Date: Sat, 12 Aug 2000 12:21:21 -0500 (CDT)
- References: <Pine.SOL.4.20.0008111648540.8083-100000@garnet.tc.umn.edu>
- Sender: mike@3po.dhs.org
Philip C Mendelsohn wrote:
>
> I'm wondering if anyone has a slick answer to this:
>
> I have lots of systems around here running Debian (usually slink /
> slink+). I decided to set up teTeX to do some work at home -- No
> trouble. The question is that I want to actually read some of the docs I
> usually take for granted.
>
> The teTeX docs are usually a lot of .dvi.gz files, and they are tied
> together with a couple of web pages.
>
> I'm having a hard time setting up lynx or netscape to gunzip them *and*
> send them to xdvi.
>
> Can anyone suggest a method other than gunzipping everything once
> installed? Any suggestions on a better .dvi previewer? Am I forgetting
> something stupid about named pipes, or why I can't use them in the MIME
> types editor in Netscape?
I wouldn't really recommend using named pipes, as many programs these
days will only read from `regular' files. However, you can just create
a regular file to dump a dvi file into, then run xdvi on it. A simple
example of this would be something like (the `$$' is a variable
representing the process ID of the script):
#!/bin/sh
gunzip -c $1 > /tmp/tmp.$$
xdvi /tmp/tmp.$$
rm -f /tmp/tmp.$$
HTH
--
_ _ _ _ _ ___ _ _ _ ___ _ _ __ If it jams, force it. If
/ \/ \(_)| ' // ._\ / - \(_)/ ./| ' /(__ it breaks, it needed
\_||_/|_||_|_\\___/ \_-_/|_|\__\|_|_\ __) replacing anyway.
[ Mike Hicks | http://umn.edu/~hick0088/ | mailto:hick0088@tc.umn.edu ]