From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: locked narrowing in ELisp
Date: Fri, 19 Aug 2022 00:42:05 +0300 [thread overview]
Message-ID: <fc2f9d65-69f0-2ab3-4b38-43d1fafb42f7@yandex.ru> (raw)
In-Reply-To: <jwvpmgy9uup.fsf-monnier+emacs@gnu.org>
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.
next prev parent reply other threads:[~2022-08-18 21:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 20:18 locked narrowing in ELisp Stefan Monnier
2022-08-17 0:05 ` Dmitry Gutov
2022-08-17 0:55 ` Stefan Monnier
2022-08-17 1:00 ` Dmitry Gutov
2022-08-17 13:03 ` Stefan Monnier
2022-08-17 13:40 ` Dmitry Gutov
2022-08-17 13:55 ` Eli Zaretskii
2022-08-17 14:03 ` Dmitry Gutov
2022-08-17 14:20 ` Eli Zaretskii
2022-08-17 23:13 ` Dmitry Gutov
2022-08-18 1:58 ` Stefan Monnier
2022-08-18 21:42 ` Dmitry Gutov [this message]
2022-08-18 6:25 ` Eli Zaretskii
2022-08-18 23:10 ` Dmitry Gutov
2022-08-19 6:31 ` Eli Zaretskii
2022-08-22 0:59 ` Dmitry Gutov
2022-08-17 11:44 ` Eli Zaretskii
2022-08-17 11:54 ` Dmitry Gutov
2022-08-17 5:59 ` Po Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc2f9d65-69f0-2ab3-4b38-43d1fafb42f7@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.