[Top][All Lists]

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

Re: lynx-dev [PATCH] Forced exit capability for command scripts

From: Ville Herva
Subject: Re: lynx-dev [PATCH] Forced exit capability for command scripts
Date: Sat, 29 Jun 2002 17:44:06 +0300
User-agent: Mutt/1.3.25i

On Sat, Jun 29, 2002 at 10:31:55AM -0400, you [Thomas Dickey] wrote:
> On Sat, Jun 29, 2002 at 04:03:54PM +0300, Ville Herva wrote:
> actually, the prompt doesn't depend upon the webpage but upon lynx.cfg:
> # If QUIT_DEFAULT_YES is TRUE then when the QUIT command is entered, any
> # response other than n or N will confirm.  It should be FALSE if you
> # prefer the more conservative action of requiring an explicit Y or y to
> # confirm.  The default defined here will override that in userdefs.h.
> #
> (whether a separate 'exit' command is desirable is a different question)

I don't think we're talking about the exactly same issue here. What I mean
that if you type for example 'g', then "http://"; and then 'Q', the quit
command is not executed (instead you see "http://Q"; on the goto URL field.). 

So the idea behind 'exit' command is that it'll exit unconditionally no
matter in which context it is encoutered.

And that can come in handy if you have a script to for example fill a form,
and the format of the form changed. The the script can get into unexpected
state -- and explicit 'exit' statement will at least quit lynx when desired.

-- v --


; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

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