[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lynx-dev] lynx word bleeding?
From: |
Ian Collier |
Subject: |
Re: [Lynx-dev] lynx word bleeding? |
Date: |
Thu, 3 Feb 2022 10:36:23 +0000 |
On Wed, Feb 02, 2022 at 11:18:23PM -0500, Karen Lewellen wrote:
> Ian you indicate that this cannot be saved on the options menu, meaning it
> must be corrected where ever the compile or main lynx.cfg is stored?
That is correct; and also the lynx.cfg contains settings that dictate
whether options can be saved on the options page, so it is possible to
change that too.
I know we have been here before, but you can write a lynx.cfg file just for
your own account and run Lynx with the "-cfg FILENAME" option to use it.
imc
Re: [Lynx-dev] lynx word bleeding?, Karen Lewellen, 2022/02/01
Re: [Lynx-dev] lynx word bleeding?, Ian Collier, 2022/02/02
Re: [Lynx-dev] lynx word bleeding?,
Ian Collier <=
Re: [Lynx-dev] lynx word bleeding?, Karen Lewellen, 2022/02/03
[Lynx-dev] Handling sites that don't send content-type (was: lynx word bleeding?), Luke, Shellworld Support, 2022/02/09
- Re: [Lynx-dev] Handling sites that don't send content-type (was: lynx word bleeding?), Karen Lewellen, 2022/02/09
- Re: [Lynx-dev] Handling sites that don't send content-type (was: lynx word bleeding?), Chime Hart, 2022/02/09
- Re: [Lynx-dev] Handling sites that don't send content-type (was: lynx word bleeding?), Karen Lewellen, 2022/02/09
- Re: [Lynx-dev] Handling sites that don't send content-type (was: lynx word bleeding?), Chime Hart, 2022/02/09
- Re: [Lynx-dev] Handling sites that don't send content-type (was: lynx word bleeding?), Karen Lewellen, 2022/02/09
- Re: [Lynx-dev] Handling sites that don't send content-type (was: lynx word bleeding?), Chime Hart, 2022/02/09
- Re: [Lynx-dev] Handling sites that don't send content-type (was: lynx word bleeding?), Karen Lewellen, 2022/02/09
- Re: [Lynx-dev] Handling sites that don't send content-type (was: lynx word bleeding?), Chime Hart, 2022/02/09