This sounds like a question about what the principle of least surprise says in this case: can one expect a macro to behave as if someone were pressing a sequence of keys, or more like a (bracketed) paste action? In the latter case, one could have blinking parens throughout, *exept* when expanding a macro (which is what Artyom asks for, if I understand it correctly)
I'm afraid that especially rlwrap users are wont to stretch the boundaries of what readline is able to do, and that is why rlwrap has filters, which make the whole interaction scriptable. In that way, rlwrap itself can remain relatively simple. Or, if bracketed paste mode is enabled, and your macro is just inserting > text (i.e. not invoking any Readline commands) you can have all the text be > inserted in bracketed paste mode like "\e[200~YOUR TEXT HERE\e[201~". I just tried that, but without success.... On Mon, 20 Oct 2025 at 18:18, Chet Ramey <[email protected]> wrote: > On 10/20/25 10:44 AM, Artyom Bologov wrote: > > Hi Chet, > > > >> It's not a bug, at least it hasn't been considered one to this point. > >> You could temporarily disable paren matching around the call to the > >> macro. > > > > Given that I’m mainly using Readline through rlwrap, disabling paren > > matching at will is not possible. > > Maybe not `at will', but this is certainly possible: > > INPUTRC=inputrc.noblink rlwrap program > > -- > ``The lyf so short, the craft so long to lerne.'' - Chaucer > ``Ars longa, vita brevis'' - Hippocrates > Chet Ramey, UTech, CWRU [email protected] http://tiswww.cwru.edu/~chet/ > -- Hans Lub +31 (0)6 14818149 PGP key <https://hanslub.org/> Dolomieten 74, NL 3524 VH Utrecht [email protected]
