|
From: | Dmitry Gutov |
Subject: | Re: locked narrowing in ELisp |
Date: | Fri, 19 Aug 2022 00:42:05 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 |
On 18.08.2022 04:58, Stefan Monnier wrote:
Could someone give a few problem scenarios with this patch? Preferably ones that should be hard to fix. Adapting isearch took about 2 lines.I don't think there'll be much that's hard to fix, no. The problem is rather that there'll be a lot to fix, so it'll basically be half-broken for a long time.
That is a problem indeed. So at the very least the corresponding feature branch would need attention from somebody (or some people) who use narrowing a lot.
E.g. `C-x h M-x write-region RET` will end up writing something else than what I'd expect.
I see what you mean. Some region-related commands might need direct support indeed (region-beginning and region-end changes their return values once narrowing it applied).
soft-narrow-to-region might also alter the region, if we decide to support its programmatic application.
[Prev in Thread] | Current Thread | [Next in Thread] |