[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: Lloyd Rasmussen
Subject: Re: lynx-dev [PATCH] Forced exit capability for command scripts
Date: Sat, 29 Jun 2002 11:07:57 -0400

I haven't used the scripting facilities at all.  

'Q' is the unconditional Quit action, not prompted, whereas 'q'
normally displays a yes/no prompt.

After a goto URL has been entered and the Enter key completes it, Q
should quit the browser, although it might take a minute or two for
repeated connect attempts to time out.

On Sat, 29 Jun 2002 15:30:37 +0300, Ville Herva wrote:

>[Please CC - I'm not subscribed to lynx-dev.]
>Thomas Dickey wrote:
>> > Thinking of the busy loop patch I sent earlier: on the other hand it makes
>> > sense to continue when the script stream runs dry - that way you can make
>> > a script that logs you in to somewhere and then continue interactively.
>> > OTOH, when you use -cmd_script from scripts (as I do) you really want lynx
>> > to exits once everything is done.
>> >
>> > The attached patch implements an "exit" statement to cmd_scripts. Once exit
>> > is encountered, lynx is forced to exit. 
>> actually it already has a "quit" command.
>Hmm. I feel stupid now :).
>key g
>key h
>key t
>key t
>key p
>key :
>key /
>key /
>  lynx -cmd_script=/tmp/k.script
>with the exit-patch, lynx immediately exits. 
>If I replace "exit" with "quit", it doesn't. (This is with 2.8.5dev8).
>Also, grep -i quit **/*.[ch] doesn't immediately reveal where the "quit"
>command is implemented...
>-- v --
>; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

Braille is the solution to the digital divide.
Lloyd Rasmussen, Kensington, Maryland
home:  <address@hidden> <>
Work:  <address@hidden>         <>

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

reply via email to

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