[dev] quirks with sam's structured regexps

From: Greg Reagle <greg.reagle_AT_umbc.edu>
Date: Sun, 28 Feb 2016 12:20:17 -0500

On Sun, Feb 28, 2016 at 11:34:37AM +0000, Raphaël Proust wrote:
> I managed to reconstruct an example that I am dissatisfied about.
> The following works:
> Edit ,x/test/{
> i/<
> a/>
> }
> But not the following:
> Edit ,x/test/{
> a/>
> i/<
> }
> The second one you the result "<tes>t" and a warning about changes
> being out of sequence.

I get these results: The first version works fine. The second version
shows error "?changes not in sequence" and does nothing.

But I don't see a big problem here, only a minor inconvenience. Do your
insert before your append when using a braced compound command, and it
works fine.
Received on Sun Feb 28 2016 - 18:20:17 CET