From: "Laura Eaves" <leaves1@carolina.rr.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: lynx temporary files
Date: Sat, 8 Jan 2005 16:07:25 -0500 [thread overview]
Message-ID: <054201c4f5c6$0e02f0e0$6601a8c0@geekspeak> (raw)
In-Reply-To: <20050108151124.GG790@rednote.net>
Hi -- I haven't used lynx for a long time, but used to do some development
on it back a few years ago, and I seem to remember that some commented
internal debugging messages go to temp files in the current directory, not
in /tmp
Again, as someone else suggested, is this a standard release of lynx? did
you use an option that is seldom used that someone may have forgotten to
turn off debugging for? Have you looked at the contents of the files?
Good luck.
--le
----- Original Message -----
From: "Janina Sajka" <janina@rednote.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, January 08, 2005 10:11 AM
Subject: Re: lynx temporary files
Hi, Adam:
Well, /tmp is 1776, which is the Fedora default, at least. Also, the
lynx I'm using is the default provided by Fedora, 2.8.5dev.16, which I
believe is unchanged from Fedora 2. I don't rightly remember when I
started seeing this, but I was surprised, because I, too, am accustomed
only to see these files in /tmp.
Needless to say, though, that I have mangled the configuration in order
to make lynx more blind friendly. I have a .lynxrc and I have also made
system-wide changes using the new /etc/lynx-site.cfg mechanism. Looking
through both of these, I find nothing about where to write these files.
The closest I see is to put cache files into RAM, which I have turned
on. And, of course, these are cache, so what does that mean?
Adam Myrow writes:
> Is this a version of Lynx compiled from source or pre-installed? Is it a
> stable, or developer version? Are the permissions on /tmp 1777? Lastly,
> is Lynx deleting these files on exit? I've never had Lynx put anything in
> any place other than /tmp, and it always cleans up after itself, so I'm
> puzzled by this.
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
--
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
next 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 [this message]
` Janina Sajka
` Richard Villa
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='054201c4f5c6$0e02f0e0$6601a8c0@geekspeak' \
--to=leaves1@carolina.rr.com \
--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).