Re: PATCH: unwanted error aborting continued command substitution

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Apr 17, 12:02pm, Peter Stephenson wrote:
} Subject: Re: PATCH: unwanted error aborting continued command substitution
}
} On Fri, 17 Apr 2015 12:52:56 +0200
} Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
} > On Fri, Apr 17, 2015 at 11:16 AM, Peter Stephenson
} > <p.stephenson@xxxxxxxxxxx> wrote:
} > > On Fri, 17 Apr 2015 06:39:29 +0200
} > > Mikael Magnusson <mikachu@xxxxxxxxx> wrote:
} > >> % $(
} > >> cmdsubst> [press ctrl-c here]
} > >> zsh: parse error near `$('
} >
} > I didn't think to try this yesterday, but invoking push-input gives
} > the same error (sorry).

So does send-break (using e.g. ESC-x send-break RET):

torch% $(
cmdsubst> 
execute: send-break_
zsh: parse error near `$('
torch% 

} That's a completely different kettle of fish --- push-input is basically
} a hack to try to convince the line editor we've left it so we can start
} again.

Yes it's a hack, but it's the same kettle -- push-input uses send-break,
and send-break is supposed to be a simulated interrupt for cases where
the TTY intr character is not set.

So either send-break should actually set ERRFLAG_INT, or we need a third
error flag for simulated interrupts.