From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: "27896@debbugs.gnu.org" <27896@debbugs.gnu.org>,
Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#27896: [External] : Re: bug#27896: 25.2; `C-M-%' with `rectangle-mark-mode'
Date: Tue, 9 Feb 2021 21:01:52 +0000 [thread overview]
Message-ID: <SA2PR10MB4474C3B54252438A2CDFF3DCF38E9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87sg65122m.fsf@mail.linkov.net>
> > My approach is to do, for each zone,
> > what I currently do for the active region
> > as a whole, which is what vanilla Emacs
> > does for the buffer as a whole.
> >
> > IOW, instead of always using `point-min'
> > and `point-max' for _matching_, use the
> > limits of each zone. IOW, just limit
> > matching to the search space.
>
> Is this similar to how multiple major modes work?
> i.e.
> https://urldefense.com/v3/__https://www.emacswiki.org/emacs/MultipleMod
> es__;!!GqivPVa7Brio!L1gKnae4wuMn0F1d58axUCx08NTPDOSKxu5AJGwkvZB2eQ04tfi
> 0Xcu6DJtQGsq_$
Maybe, I don't know. I've never looked into
`mmm-mode' or MuMaMo or any other such. I
have a vague recollection/impression that
they may rely on text or overlay properties
in some way. There's also Alan Mackenzie's
proposal a couple of years back for "islands"
as a way of handling multiple major modes.
As to "how", I said nothing really about the
actual how, beyond saying that the general
idea is to handle zone limits analogously to
how we currently handle buffer limits.
I didn't say "analogously", but perhaps I
should have. My own approach (started but
not finished, and I'd pretty much need to
start over if I resumed) did, yes, amount to
more than an analogy.
In isearch+.el I do what I described, in
order to treat the active region the same
way vanilla Isearch treats the whole buffer:
bind variables at search start to the region
limits, and then replace `point-(min|max)'
with those variable values when non-nil.
My thoughts and initial attempts to handle
zones (~noncontiguous region) were to do
the same thing: limit search to the limits
of each zone.
(I currently use a filter to limit search
that way, but filtering is after the fact.
What's needed is to limit search _matching_.)
next prev parent reply other threads:[~2021-02-09 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 4:17 bug#27896: 25.2; `C-M-%' with `rectangle-mark-mode' Drew Adams
2017-08-02 22:22 ` Drew Adams
2021-02-05 11:58 ` Lars Ingebrigtsen
2021-02-05 16:19 ` bug#27896: [External] : " Drew Adams
2021-02-07 18:58 ` Juri Linkov
2021-02-07 20:52 ` Lars Ingebrigtsen
2021-02-08 18:12 ` Juri Linkov
2021-02-09 8:09 ` Lars Ingebrigtsen
2021-02-09 9:24 ` Juri Linkov
2021-02-09 17:34 ` Drew Adams
2021-02-09 17:54 ` Juri Linkov
2021-02-09 18:38 ` Drew Adams
2021-02-09 19:19 ` Juri Linkov
2021-02-09 21:01 ` Drew Adams [this message]
2021-02-09 21:07 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SA2PR10MB4474C3B54252438A2CDFF3DCF38E9@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=27896@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).