[Top][All Lists]

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

Re: [Lynx-dev] "lynx -child" implies "-restrictions=disk_save"

From: Thomas Dickey
Subject: Re: [Lynx-dev] "lynx -child" implies "-restrictions=disk_save"
Date: Sat, 16 Jun 2007 20:36:48 -0400
User-agent: Mutt/1.3.27i

On Sun, Jun 17, 2007 at 12:19:02AM +0400, Andrew Belov wrote:
> I'm trying to wire Lynx with the Snownews RSS reader. Both fit together
> nicely except that "-child", while enabling seamless return from Lynx to
> the RSS article list, bars file-saving at the same time.
> I'm not aware why were the restrictions introduced in the first place,

The option was adding in 1995 (other than a change to account for the
local host) - see docs/CHANGES2.5 - which is before the mailing list
archives.  Reviewing changes for LYPrint.c, I see that no_disk_save
was combined with child_lynx in 1997/5/21 - but no remark in
docs/CHANGES2.8 on that seems relevant.  Perhaps it was an afterthought
for this change:

* Extended the disk_save restriction to the print menu as well as
  the download menu, and accordingly updated lynx.hlp,, and
  Lynx_users_guide.html. - HN, FM

The likely reason for the restriction is that it was for using lynx as
a blackbox that would only display a given webpage, but not allow the
user to manipulate its contents.

Since "-child" sets no_disk_save, the "child_lynx || no_disk_save"
does appear to be redundant.

> so I hacked a "-child_relaxed" option (see the attached patch) as a
> makeshift. The patch also takes out seemingly redundant checks that
> involve both child_lynx and no_disk_save.

The help-message should be reworded, perhaps:

       "exit on left-arrow in startfile (allows save to disk)"
> Note there's one additional location in LYPrint.c that may need
> attention WRT child restrictions:
> if (child_lynx == FALSE && no_mail == FALSE && local_host_only == FALSE)
> It seems logical as long as file-saving is disallowed, but if we choose
> to do away with implied restrictions for "-child", then the check for
> child_lynx==FALSE should be lifted.

or perhaps make "-child" also set no_mail

Thomas E. Dickey

reply via email to

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