[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Should 'signal' sometimes return?

From: Davis Herring
Subject: Re: Should 'signal' sometimes return?
Date: Tue, 26 Jul 2016 10:43:34 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0

As I understand it, the debug-on-quit support is intended to catch the
user typing C-g, as opposed to altering code that calls 'signal' so that
it returns. If so, how about keeping the current approach for C-g, and
merely changing 'signal' itself so that it does not return? I wrote a
new patch to do that, and will send it to Bug#24047.

Just a thought: it could be useful to retain the (signal 'quit nil) behavior as an analog to (edebug), although I would understand keeping just the latter.


This product is sold by volume, not by mass. If it appears too dense or too sparse, it is because mass-energy conversion has occurred during shipping.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]