On Tue, Mar 08, 2011 at 09:40:26PM -0500, Chet Ramey wrote:
> On 3/8/11 11:12 AM, Chet Ramey wrote:
>
> > I might be able to finesse this particular case based on the state that
> > readline exports to the calling application.
>
> I think I was able to do that. Try the attached patch; it works for me.
> It identifies a single specific common case and allows the history to be
> saved in that case. I think that case minimizes the chances of deadlock,
> but it requires much more testing before I will be convinced. Please help
> me out by testing it.
The patch does its work, thanks a lot.
> Yes, I know that it's not 100% safe and will run unsafe functions from a
> signal handler. I will devise a better fix for later, but that will
> require changes to readline (so it can catch SIGHUP) that will have to
> wait.
Werner
--
"Having a smoking section in a restaurant is like having
a peeing section in a swimming pool." -- Edward Burr
