On Tue, 17 Sep 2002, Philip Webb wrote: > we don't want it to be specific to 1 application (eg Xli), > so Lynx should simply trap any extraneous messages & refresh the screen, > perhaps with a choice in lynx.cfg to preserve them for debugging.
they're just going to the screen either way right now - I don't know offhand if xli is writing to stderr or stdout. (I am certain that it doesn't return a useful exit code, since I have tested that more than once - so there's no good way to check if it failed to display an image). But I'll take a look at the other site Ian mentioned - my copies of xli do not display png files; gimp is too bloated to want to use for this purpose, and xzgv doesn't satisfy me either). -- T.E.Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
