Hi,
the excerpt from Lynx.trace is:
[…]
Read 183362 of 231215 bytes of data, 53143 bytes/sec, ETA 0 sec.
Read 218233 of 231215 bytes of data, 57506 bytes/sec, ETA 0 sec.
HTCopy copied 231215 actual, 231215 limit
Data transfer complete
LYCloseTempFP
...LYCloseTempFP(/tmp/lynxXXXXxHf8r4/L312-2529TMP.jpeg)
display.im6 'jpeg:/tmp/lynxXXXXxHf8r4/L312-2529TMP.jpeg'
stop_curses: done.
LYSystem(display.im6 'jpeg:/tmp/lynxXXXXxHf8r4/L312-2529TMP.jpeg')
start_curses: done.
HTAccess: status=200
[…]
Why does Lynx use “display.im6” when /etc/lynx-cur/ does not
even *contain* this? (This is the Debian packaging.)
Additionally, I specifically set
XLOADIMAGE_COMMAND:xloadimage %s &
and this was ignored.
The picture in question is a normal <a href>, though…
This can’t be *that* hard. It “just works” on MirBSD.
A further grep through /etc/ points the bad program is named here:
/etc/mailcap:image/yuv; display.im6 'yuv:%s'; test=test -n "$DISPLAY"
(and some dozen more occurrences)
Is that the culprit? If so, Atsuhito KOHDA, how do I override it?
Thanks,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-314
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Boris Esser, Sebastian Mancke
_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
