GNU bug report logs - #76313
New function `replace-region`

Previous Next

Package: emacs;

Reported by: Stefan Monnier <monnier <at> iro.umontreal.ca>

Date: Sat, 15 Feb 2025 22:19:02 UTC

Severity: normal

Tags: patch

Full log


Message #108 received at 76313 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefankangas <at> gmail.com>
Cc: 76313 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca, tsdh <at> gnu.org
Subject: Re: bug#76313: New function `replace-region`
Date: Sat, 08 Mar 2025 13:28:41 +0200
> From: Stefan Kangas <stefankangas <at> gmail.com>
> Date: Sat, 8 Mar 2025 01:46:20 -0800
> Cc: 76313 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca, tsdh <at> gnu.org
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > I'm saying that the documentation aspect of this is not the real
> > problem.  Once we agree on the code and API changes, updating the
> > documentation is a no-brainer, and I don't expect it to trigger an
> > argument.
> >
> > The problem here is how to provide the functionality without
> > complicating Emacs with yet another API, where we already have two.
> 
> OK, thanks.  That makes it more clear to me what you're saying.
> 
> I don't have any better solution to propose than:
> 
>     a) Obsoleting `replace-buffer-contents`.
> 
>     b) Renaming `replace-region-contents` to `replace-region-carefully`.
> 
> I think both of these would make sense independently of `replace-region`.
> How about we move ahead with those, and then revisit the situation once
> that is done?

I'm not sure I understand: are you suggesting to do the above, and
_then_ add a new replace-region function?  I thought I already
explained why doing so will not resolve the problems I had with the
addition of a new API?




This bug report was last modified 75 days ago.

Previous Next


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