Subject: bug#71370: 30.0.50; Please un-obsolete buffer-substring as a generalized variable

From: Michael Heerdegen <[email-masked]>
Date: Thu, 20 Feb 2025 03:12:25 +0100

Sean Whitton <[email-masked]> writes:

> I would propose that we should keep anything where there isn't a simple
> set-* function to take its place.
> So at least buffer-string and buffer-substring, and possibly more.

Please let's keep those two separate questions separate: (1) is a
certain functionality useful, and (2) if it is, should it be provided,
maybe even only, as a gv setter function.

And of course the current `setf'ability of `buffer-substring' is not
falling from the sky.  It is implemented in a quite primitive internal
function named `cl--set-buffer-substring', four lines long.

That those implementations are internal functions doesn't mean we can't
keep those setter obsoleted.  We can provide replacements.

Sorry for speaking out something trivially obvious, but I had the
impression that this aspect has been overlooked by some.

Michael.