Is it not interesting how a shared label translates into totally different
experiences?
Speaking only for myself, I have no idea why your screen reader would
impact
an option field...mine presents them perfectly for me.
Personally while I made the change in the options menu, indeed it does
work, the problem is that the fix is not permanent.
Its one of those options with an ! meaning the change cannot be saved.
Perhaps something to consider changing in future?
Karen
On Sat, 10 Jun 2017, -dan d. wrote:
Thanks, that fixed it.
I made the change in lynx.cfg instead. As a blind user I find the options
input combersome with a screen reader. I prefer to make entries into .lynxrc
and/or lynx.cfg instead.
In it it says nothing about the string:
[36][(1)
Per the lynx.cfg info I used only "none". What is the purpose of the number
string?
Thanks for your help.
This is, again, almost certainly
a problem with wrongly labelled
compressed data. Set this in (O)ptions, then retry:
Preferred encoding : [36][(1)__None____]
bye,
//mirabilos
--
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh
XB
_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
