Re: more m4p bugs

On Mon, May 19, 2025 at 02:36:50PM -0500, Eric Blake wrote:
> > > > > Now testing with b686ed, you have a problem with redefining a macro as
> > > > > empty if it has been undefined in the meantime:
> 
> Another cute stack trace worth fixing:

Messing around, this one has odd behavior interactively (here, using
=> on the lines I typed):

$ m4p
=>hi
hi
=>changecom(//,-)
=>what happened
=>^D

what happened

It looks like the act of setting changecom() to use a start character
longer than one byte ends up in getting the output off (the newline is
not getting echoed soon enough).

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization:  qemu.org | libguestfs.org