Re: PATCH: Don't store ZLE_LINE_ABORTED in vared context

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Mar 4,  7:40pm, Mikael Magnusson wrote:
} Subject: PATCH: Don't store ZLE_LINE_ABORTED in vared context
}
} send-break (^G ESC-^G) (unbound) (unbound)
}        Abort  the current editor function, e.g. execute-named-command, or the
}        editor itself, e.g. if you are in vared. Otherwise abort  the  parsing
}        of the current line; in this case the aborted line is available in the
}        shell variable ZLE_LINE_ABORTED.
} 
} However, pressing ctrl-c inside vared stores whatever was being edited
} in ZLE_LINE_ABORTED, which the above seems to imply should not happen.

Another documentation error rather than code error, IMO.

} The following adjusts the code accordingly. It was actually a bit
} annoying if you set up a widget to do the up-line-or-aborted, because
} it will grab the vared text as a command then.

Hrm, perhaps, but I believe the intent was to be able to hang on to
whatever buffer was most recently being edited when the interrupt came
through.