Re: [PATCH] Expose isearch and suffix regions to widgets.

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Apr 23,  9:36pm, Daniel Shahaf wrote:
}
} m0viefreak wrote on Sat, Apr 16, 2016 at 18:17:40 +0200:
} > I think ISEARCH_MATCH would be the ideal name, if the matched string was
} > exposed, but I haven't found a simple way to do that.
} 
} Something like the attached, perhaps?  Do you think something like this
} should be added?  (Myself, I'm not sure, since the value would be
} derivable from the three ISEARCHMATCH_* parameters' values.)

My point in suggesting ISEARCH_MATCH was to limit the feature to three
variables with "ISEARCH_" as a prefix.  This was countered with the
expressed desire to follow the "_ACTIVE" suffix pattern instead.  I'm
not particularly invested in this either way, but having *both* the
"_MATCH" and "_ACTIVE" variants is certainly redundant, and having
two different prefixes ("ISEARCH_" and "ISEARCHMATCH_") is annoying.

Other comments:

I will posit that isearch is rather different from YANK/SUFFIX/REGION
in that one might be interested in what the current search pattern is,
as well as what string is matched.

There are two existing variables LASTABORTEDSEARCH and LASTSEARCH which
refer to that search pattern, neither of which uses the "I", so maybe
these new three (or four or five) shouldn't use it either.

Those two variables aren't cleared when you start a new search, they
only change based on the final state of the search.