Re: Coding bug in insert-file-contents-internal
[sorry for response delay. back now.]
On Mon, 07 Feb 2005, David Kastrup whispered secretively:
>> I don't know if there's a better way to do it:
>
> Yes.
>
> record_unwind_protect() and specbind() (of a Q... Symbol that names the
> variable) are both fine. Easiest/best is internal_bind_lisp_object().
I'll spin a new patch that does that.
Whatever. I think it is rather likely that the fix is not in the
yet
released 21.4.17,
It's not.
I take it that this bug has not been encountered except by people
using special software, and this even though XEmacs comes with tool
bars and things. Am I right to conclude that the xbm and xpm image
loading modes of XEmacs (which are the default formats used for icons
unless I am mistaken) basically are not affected by this bug since
they are principally ASCII formats and seemingly coded in a manner
that don't mind if the end of line conversion is set to some weird
value via the dired.el operation?
That's true. This only breaks loading of PNGs and things like that from
files.
If this could be asserted, it would make loading preview-latex
somewhat faster under XEmacs and would remove the necessity for at
least some workaround code. We would still need workaround code for
the actual in-text images generated by TeX (which are usually PNG),
but for nothing else.
The `workaround code' is simply to read it ourselves and then use :data
instead of :file, I think.
This is possibly more efficient because we can cache it ourselves, as
well (although this may be overdesign) :)
--
Synapsids unite! You have nothing to lose but your eggshells!