bug#5273: 23.1; format-alist encode vs write-region-post-annotation-function

[Kevin Ryde]

(Belated followup! ...)

Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> the issue of temp
> buffers accumulating if to-fn errors out is indeed a problem, but not
> a new one,

I presume kill-on-write was an attempt to address that though.

As I say, I suspect the `format-count' passed from build_annotations()
naming the buffer "Format Temp 0" etc the same on each call will keep a
lid on how many leftovers.

I suspect that also means it's not reentrant -- if the TO-FN writes from
another buffer with a buffer-file-format then "Format Temp 0" will get
re-used and clobbered too soon.  I might start a separate bug for that.

> with-temp-buffer is not an option, since the new "temp" buffer (usually)
> needs to be returned as the new current-buffer at the end of
> the function.

There must be some far-enough outer scope of write-region or whatever
where temporaries can be discarded ... but the amount of stuff done just
to save some bytes is scary! :-)