lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] Can't save options to disk


From: Stefan Caunter
Subject: Re: [Lynx-dev] Can't save options to disk
Date: Tue, 27 Sep 2011 08:48:14 -0400

On Tue, Sep 27, 2011 at 8:36 AM, Graham Lawrence <address@hidden> wrote:
> Using lynx -trace I get the same message: "Alert! Unable to save options!"
> Lynx.trace is attached as lt.zip
> I'm using the lynx included in slackware 13.1, i.e.
> 05:04:44 $ lynx -version
> Lynx Version 2.8.7rel.1 (05 Jul 2009)
> libwww-FM 2.14, SSL-MM 1.4.1, OpenSSL 0.9.8n, ncurses 5.7.20081102(wide)
> Built on linux-gnu Feb 12 2010 19:50:52
>
> I'm not trying to change any of the options marked (!).
> I want to change from Novice to Advanced, and set the editor to vim, they
> fail.
> I've made these changes in lynx.cfg, they are ignored.
> But other changes I have made in lynx.cfg have been accepted, e.g.
> SSL Prompting changed to Force Yes, which is a (!) item in Options


The trace shows you have a .lynxrc file; is it writable? Are you
selecting the [X] option to save to file? I don't see that happening
in the trace from a quick glance.

>
>
>
> On Mon, Sep 26, 2011 at 1:41 PM, Thomas Dickey <address@hidden> wrote:
>>
>> On Mon, 26 Sep 2011, Graham Lawrence wrote:
>>
>>> As user, I cannot save option changes to disk, so my changes remain in
>>> effect only until the session closes.
>>> As root there is no such problem.  But I rarely work as root.
>>>
>>> I've changed ~/lynx.cfg to have the options I want, but that has no
>>> effect
>>> on lynx's behavior
>>
>> Is there a message?  Does "lynx -trace" show any interesting messages?
>>
>> (offhand, the only related report I can recall was a while back from a
>> non-cooperative Fedora user...)
>>
>> --
>> Thomas E. Dickey
>> http://invisible-island.net
>> ftp://invisible-island.net
>
>
> _______________________________________________
> Lynx-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/lynx-dev
>
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]