Hi Karen,
I'm unaware of any encoding default that might cause your problem.
However, if your server admin tried to upgrade lynx, they might have tried to
upgrade
gzip too. Make sure gzip is working.
I've heard of cases where upgrading from gzip 1.4.4 to 1.5 caused
the error you describe.
Also, it can't hurt to check available disk space:
df /tmp
or
df ~
Rudy
On Sun, Dec 26, 2021 at 10:24:27PM -0500, Karen Lewellen wrote:
make that error uncompressing temporary file.
come to think of it, that error sometimes shows up with google searches now
as well, with my changing the encoding default fixing the problem.
What we had before this situation was 2.8.9dev.16
Kare
On Sun, 26 Dec 2021, Karen Lewellen wrote:
Hi folks,
Sigh..this is frustrating.
One fall out of the last shellworld related Lynx incident, turns out our
admin was trying to upgrade the browser and failed, is that they rolled
things back to a much earlier edition.
I have told them as much, their removing even the edition of lynx
dreamhost provides on their shells, and dreamhost does not care about
proper lynx configuring. Can you say google presenting a captcha when
one seeks to do a search anyone?
Long story short, now when following many links in emails, I run into
the "error deflating temporary file message, that has a fix when in
lynx proper, but cannot be addressed if following an email link.
What I seek is a command line option that impacts the encoding, I am
likely not explaining this clearly, which lets me add the command when
editing the url presented in the email.
Is there such a thing?
Imagine I will follow this post with the actual error I mean.
Thanks,
Karen
--
Rudy Vener
Website: http://www.rudyvener.com
Twitter: https://twitter.com/RudySalt