From: "Richard Villa" <villar@earthlink.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: lynx temporary files
Date: Sat, 8 Jan 2005 18:00:57 -0600 [thread overview]
Message-ID: <013001c4f5de$4c1cb0b0$6401a8c0@NACHOCHIPS> (raw)
In-Reply-To: <20050108024657.GF790@rednote.net>
The only thing I can suggest, is to reinstall Lynx.
----- Original Message -----
From: "Janina Sajka" <janina@rednote.net>
To: <speakup@braille.uwo.ca>; <blinux-list-bounces@redhat.com>;
<ma-linux@rednote.net>
Sent: Friday, January 07, 2005 8:46 PM
Subject: lynx temporary files
>I have a problem with lynx. It's writing temporary files in my $HOME (as
> opposed to something more appropriate like /tmp), but I can't find why.
> I'd like to fix this--but can't find what to tweak. Does anyone know?
>
> Here's what I get in my $HOME:
>
> L20052-1103TMP.html
> L9387-1161TMP.html.gz
> L9387-1181TMP.html
> L9387-1197TMP.html
> L9387-298TMP.html.gz
> L9387-368TMP.html
> L9387-420TMP.html
> L9387-954TMP.html.gz
>
>
>
> --
>
> Janina Sajka Phone: +1.202.494.7040
> Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
>
> Chair, Accessibility Workgroup Free Standards Group (FSG)
> janina@freestandards.org http://a11y.org
>
> If Linux can't solve your computing problem, you need a different problem.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Janina Sajka
` Adam Myrow
` Janina Sajka
` Laura Eaves
` Janina Sajka
` Richard Villa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='013001c4f5de$4c1cb0b0$6401a8c0@NACHOCHIPS' \
--to=villar@earthlink.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).