Subject: bug#56682: feature/improved-locked-narrowing 9dee6df39c: Reworked locked narrowing.

From: Drew Adams <[email-masked]>
Date: Thu, 9 Feb 2023 22:46:02 +0000

> (without-narrowing
   ^^^^^^^^^^^^^^^^^
>   ...)

Without entering into this thread's real content...

If we're now adding function/macro names that use
"narrowing" instead of (buffer) "restriction"
(which is OK by me), will you also please create
aliases for all of the existing thingies that use
the old "restriction" names?

It's not good to introduce multiple ways to refer
to the same thing (a narrowing, aka a buffer
restriction), and especially to do that only for
some such names.  Evolution isn't bad, but let's
not lose consistency for no good reason (dunno
whether there's a good reason here).

Currently we have, and for a long time we've had,
(at least) these that I'm aware of:

Functions/macros:

 byte-compile-save-restriction
 org-agenda-set-restriction-lock     (command)
 org-element-restriction 
 org-speedbar-set-agenda-restriction (command)
 save-restriction

Variables:

 byte-save-restriction
 org-element-object-restrictions  
 org-speedbar-restriction-lock-overlay

And I've added this function for my own library:

 isearchp-toggle-region-restriction  (command)

Maybe other 3rd-party code has also added some
such names.