Bug 128921 - Default /etc/lynx.cfg contains dubious advice
Summary: Default /etc/lynx.cfg contains dubious advice
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: lynx   
(Show other bugs)
Version: 2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-07-31 16:09 UTC by Alan Cox
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-07-31 21:22:05 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Alan Cox 2004-07-31 16:09:52 UTC
s always, I need someone's help posting a bug report on this as
Bugzilla has not yet been made eyes-free accessible ...
                                                                     
          
The default /etc/lynx.cfg contains the following caution:
                                                                     
          
# Please don't edit this file directly (it is updated with every Red Hat
# Linux update, overwriting your changes). Instead, edit
# /etc/lynx-site.cfg.
                                                                     
          
Unfortunately, editing /etc/lynx-site.cfg does no good, as directives
placed there are disallowed, by default, in /etc/lynx.cfg. If one tries,
lynx will not run at all.
                                                                     
          
                                                                     
          
--
                                                                     
          
                                Janina Sajka, Chair
                                Accessibility Workgroup
                                Free Standards Group (FSG)

Comment 1 Alan Cox 2004-07-31 21:22:05 UTC
Local error apparently.



Note You need to log in before you can comment on or make changes to this bug.