Re: Out-of-date completions for `read-buffer'

[Stuart D. Herring]

> I think it is worth fixing.  Copying the alist pairs as well as the
> alist itself would be simple and avoid any danger of crashing.  It
> would still "complete wrong" in the case of creating or killing
> buffers, but that seems like a minor issue.  So I think that solution
> would be fine.  However, the `complete-buffer' solution you proposed
> would be fine too.
>
> Would you like to fix it one way or the other?

It turned out that the `complete-buffer' method was easy, since
Vbuffer_alist is of course still around: see the attached (hopefully
trivial) patch.  The name of the new function and its doc string might
both need improvement.

Davis

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.

read-buffer.patch
Description: Binary data