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 18:38:34 +0000 [thread overview]
Message-ID: <SA2PR10MB447405DF224DF0D19DD5C90DF38E9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87zh0d5dpu.fsf@mail.linkov.net>
> > I've long had in mind doing this myself,
> > and started to do so more than once, but I
> > haven't gotten around to accomplishing it.
> >
> > If someone does it (in a general way, with
> > no assumptions of rectangularity) then
> > great. If not, that will be for some
> > indefinite future.
>
> In the most general case, a noncontiguous region
> is just a set of subregions (or as you call this -
> 'zones') that for the commands that operate on it
> should look as just one contiguous string.
Well, no. It depends on the command, of
course. But _most_ commands will want to
treat a set of zones as just that.
They'll perform operations on one or more
of the zones - either separately or in
combination in some way.
Operations on zones need not even treat
_any_ (let alone all) of the zones as a
string.
> How to implement this, I have no idea.
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.
next prev parent reply other threads:[~2021-02-09 18:38 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 [this message]
2021-02-09 19:19 ` Juri Linkov
2021-02-09 21:01 ` Drew Adams
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=SA2PR10MB447405DF224DF0D19DD5C90DF38E9@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).