[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 :). Anyhow: k.script ---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<--- key g key h key t key t key p key : key / key / exit ---8<---8<---8<---8<---8<---8<---8<---8<---8<---8<--- Doing lynx -cmd_script=/tmp/k.script http://www.hut.fi 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 -- [EMAIL PROTECTED] ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
