From: Cheryl Homiak <chomiak@charter.net>
To: speakup <speakup@braille.uwo.ca>
Subject: more on links from howto to redhat manual
Date: Wed, 26 May 2004 23:49:37 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0405262341260.17686@localhost.localdomain> (raw)
Well, I still can't explain it but I solved it for the fedora installation
the same way as I did for the debian one: I got rid of the current
installation (the one from fedora) by doing "yum remove lynx" and
downloaded and compiled 2.8.5-rel1 from the lynx website. Interestingly,
when I removed fedora's version, I was told it was removing 2.8.5-1 but I
was pretty sure it had said 2.8.5.dev16 when I checked i before. There
were other little ideosyncracies, like the fedora lynx installation using
fedora as the startfile even though that wasn't what the lynx.cfg had for
a startfile; made me wonder what else they might have over-ridden. At any
rate, with my new install fresh from lynx, the Pine site and the opensound
site downloaded for me with no problem, AND ..... the Redhat 9 manual is
there in all its glory. So I can't explain why it doesn't happen to
everybody, but it seems to have had something to do with the .dev16
release. Other than that I can't say, but maybe somebody will be
comforted and encouraged if they have a weird problem with lynx and see my
saga in the archives.
--
Cheryl
"Do not fear, for I am with you;
do not be dismayed, for I am your God.
I will strengthen you and help you;
I will uphold you with my righteous right hand."
next reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Cheryl Homiak [this message]
` Janina Sajka
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=Pine.LNX.4.60.0405262341260.17686@localhost.localdomain \
--to=chomiak@charter.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).