GNU bug report logs - #71370
30.0.50; Please un-obsolete buffer-substring as a generalized variable

Previous Next

Full log

View this message in rfc822 format

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Sean Whitton <spwhitton <at> spwhitton.name>
Cc: 71370 <at> debbugs.gnu.org, Ihor Radchenko <yantar92 <at> posteo.net>, Stefan Kangas <stefankangas <at> gmail.com>, Adam Porter <adam <at> alphapapa.net>, Andrea Corallo <acorallo <at> gnu.org>, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: bug#71370: 30.0.50; Please un-obsolete buffer-substring as a generalized variable
Date: Thu, 20 Feb 2025 03:12:25 +0100

Sean Whitton <spwhitton <at> spwhitton.name> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.