Re: XEmacs and 1x1 gif images

Robert Pluim writes: OK. I'm happy to hear that. :-) Hm. I just got around to trying it, and I only get 43 lines. Maybe we should blame larsi for the other 250 lines you get? ;-) I don't think returning is the right thing to do: Errors should never pass silently. Unless explicitly silenced. The obvious application of the Zen is for the calling code to do the explicit silencing. In the case of VM, (condition-case nil (set-extent-begin-glyph (make-extent (point) (point)) (make-glyph (vector 'gif :data data))) (image-conversion-error (insert "[invalid GIF: " file "]\n"))) or similar. Unfortunately, there are times when we do want to see such errors. It would be horrible for somebody to spend a few days trying to track down why some image doesn't appear, only to find out that the image is broken (according to giflib) and got swallowed in make-image-instance. I agree that we do *not* (normally) want to see a backtrace for a problem that XEmacs thinks is external. `make-image-instance' seems to agree, it has a fourth argument NOERROR with this documentation: NOERROR controls what happens with the image cannot be generated. If nil, an error message is generated. If t, no messages are generated and this function returns nil. If anything else, a warning message is generated and this function returns nil. But callers of make-image-instance don't generally seem to have a way to control that. :-( It doesn't say what's in the error message. Maybe we can suppress the backtrace part in make-image-instance. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta