Re: lynx-dev reading sjis docs [was Re: lynxcgi problem]

[Natasha Live]

I wasn't saying getting rid of the ability to run external
programs/scripts, my god it would not be a unix program without the
ability to spawn externl programs! I was only saying that external
programs shouldn't be first avenue of fixing a problem. Okay i can see the
use of external script to test new ways before full implementing them into
lynx (saves on the bug-fix circle test-trace bug-edit
source-compile-test), but to say to the end user "use this script to fix
the tables so that lynx can understand them" is basically bad form (sorry
best word i could think of! can't call it laziness casue you lot do a lot
of work on the system).

A few glaring things IMHO are the table support ( i know you're working on
it) and the ability to spawn a new browser when in a windows enviro.
Sorry this is a side-track but it is about external support.

A basic new browser option could be :
Highlight link, press N (or similar), get status line:
Start with D)ocument, L)ink, H)ome and C)ancel.
then spawn a new spawn lynx using a line from the lynx.cfg ie:
SPAWN_COMMAND:xterm -bg black -fg white -name Lynx -e /usr/local/bin/lynx
and the original lynx tags he http address on to the end of SPAWN_COMMAND.

On Tue, 28 Dec 1999, Henry Nelson wrote:
> 
> However, my way of thinking is the opposite.  Where Lynx runs circles around
> the other browsers out there is exactly those "outside" ways of doing things:
> lynxcgi, lynxprog, lynxexec, external, download, or printer.  Letting these
> fall into disuse is a waste of Lynx's talents.
> 
> __Henry