[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: Thomas Dickey
Subject: Re: lynx-dev [PATCH] Forced exit capability for command scripts
Date: Sat, 29 Jun 2002 10:31:55 -0400
User-agent: Mutt/1.3.27i

On Sat, Jun 29, 2002 at 04:03:54PM +0300, Ville Herva wrote:

> If I understand this correctly, the difference is, that "exit" will exit
> immediately and unconditionally. In the example script above, we are
> entering an URL after a 'g' command. Pressing 'Q' then does not work.
> The example is dull, but the reasoning is that if the web page changes (or
> there is some other unanticipated condition, such as a network problem), we
> may be in any unexpected state when the command script ends. If command
> scripts are executed from shell scripts it is important that lynx will exit
> no matter what rather than waiting for a key press.
> You can propably achieve this with a suitable combination such as "key ^C" -
> "key Q", but I thought an explicit command was cleaner (although my
> implementation necessarly isn't.)

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)

Thomas E. Dickey <address@hidden>

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

reply via email to

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