Sh�rab dixit: >Now I tried to save this change to disk but i does not work. I checked >/etc/lynx-cur/* to see if perhaps it was not allowed for users to save >tis setting but couldn't find anything either. Cn somebody help on this,
Add the following line to lynx.cfg: ENABLE_LYNXRC:PREFERRED_ENCODING:ON Then you can save it. >Also: would it be possible to tell lynx to assume yes as an answer to >this question, so things would work even if nothing is fixed on the The 401 message body? That has nothing to do with the original problem. It’s another case of broken programming on the server side, but a different one… sending a 401 first… might work after you logged in once, if it stores that in cookies… who knows. >Checked, thanks. I'm wondering: how do other browsers do to still be >able to display the content ? Do they simply ignore the declared >encoding and use something like file to find out hat's the actual file(1) just reports it as “data”. No, they just don’t offer the “compress” method normally; lynx can do more, like gopher. bye, //mirabilos -- Support mksh as /bin/sh and RoQA dash NOW! ‣ src:bash (252 (272) bugs: 1 (2) RC, 175 (189) I&N, 76 (81) M&W, 0 F&P) ‣ src:dash (79 (91) bugs: 4 RC, 33 (37) I&N, 42 (50) M&W, 0 F&P) ‣ src:mksh (1 bug: 0 RC, 0 I&N, 1 M&W, 0 F&P) http://qa.debian.org/data/bts/graphs/d/dash.png is pretty red, innit? _______________________________________________ Lynx-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lynx-dev
