lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV /tmp patch, round 2


From: Nelson Henry Eric
Subject: Re: LYNX-DEV /tmp patch, round 2
Date: Tue, 15 Jul 1997 10:23:33 +0900 (JST)

> I do believe that this (lynx_temp_space) isn't related to this problem.

I believe it may be, but how is beyond my capabilities.

> Does it happen if you _don't_ set lynx_temp_space?

It happens, but with a name for the file that I would expect.  To be
exact, if I comment out the "setenv LYNX_TEMP_SPACE /home/guest/.lynx"
line from the .cshrc file for that account, the file which is created
in /home/guest and that most renders is /home/guest/L191120TMP.hog.

Before all this discussion started, that is the way I had it configured.
Because I use the same binary for various types of accounts (general under-
grads, students in my lab, ..., captive account), in userdefs.h I define
the tmp directory as `` #define TEMP_SPACE "~" ''.  I should have mentioned
this yesterday.  What I described yesterday was a binary compiled with
TEMP_SPACE as `~', but the environment variable LYNX_TEMP_SPACE set
`~/.lynx'.  The reason, again, for doing this, is that ~ needs permission
755, but I'd like the tmp space to be 600 (+t is not paranoia really, just
showing off :).

>  ] This account has a unique .mailcap entry:
>  ]    text/x-archive; /usr/bin/most +s -k %s,
>  ] and a unique .mime.types entry:
>  ]    text/x-archive                 hog. 

I leave this for reference.  It has bearing on the total situation.

>  ] a file with the extension .hog.gz, e.g. myarchive.hog.gz (a
>  ] compressed text file) a file by the name ".hog" (literally; not
>  ] "myarchive.hog") is created in /home/guest, not under
>  ] /home/guest/.lynx (ls -al):
>  ]    -rw-------   1 user       369447 Jul 14 19:39 .hog

Ditto. (Bad reference to most deleated.)

> [some speculations.  I know nothing about most, sorry.]

Most more or less has nothing to do with it.  You could put vi in there.

> Is lynx decompressing this (do you see gzip -d on the status line?)?

Yes, the information is in .mime.types for that (also hardcoded in Lynx?).
The status line is "/usr/bin/gzip -d /home/guest/.hog.gz" immediately
before it is passed to most.  (Most has the capability to decide whether
or not a file needs to be decompressed, but it's not given the chance in
this case.)

> Where is myarchive.hog.gz located, on the other end of a server, 
> file://localhost/path/to/myarchive.hog.gz, what?

On a server on another machine.  The URL is in the form:
        http://www.someservr.ac.jp/lynx/myarchive.hog.gz.
A head request to that server returns:
        Content-type: text/x-archive
        Content-length: 113267
        Content-encoding: gzip


> should work to send the decompressed stuff to stdout, so you could do
>      gzip -dc filename.hog.gz | most

Actually, you could do `most filename.hog.gz', but Lynx is programed
to decompress a file with the extension gz.

> .hog file, I'd have to suspect that neither lynx nor gzip is doing this.

One or the other is doing it, but how, I don't know.  This sounds like
a cop-out, but I'm really swamped at work, i.e., don't stretch your neck
waiting for a -trace output.

__Henry
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]