Re: Q: Is there a way to tell why DEBUG trap was triggered?

On 3/16/20 1:00 PM, Greg Wooledge wrote: > On Mon, Mar 16, 2020 at 09:47:44AM -0400, Chet Ramey wrote: >> On 3/15/20 7:41 AM, Šimon Let wrote: >>> Hi All, >>> >>> I'm using PROMPT_COMMAND and DEBUG trap to emulate "PRE" and "POST" hooks >>> in bash. I have run into the issue where the DEBUG trap ge

Re: Q: Is there a way to tell why DEBUG trap was triggered?

On Mon, Mar 16, 2020 at 09:47:44AM -0400, Chet Ramey wrote: > On 3/15/20 7:41 AM, Šimon Let wrote: > > Hi All, > > > > I'm using PROMPT_COMMAND and DEBUG trap to emulate "PRE" and "POST" hooks > > in bash. I have run into the issue where the DEBUG trap gets triggered when > > any custom readline w

Re: Q: Is there a way to tell why DEBUG trap was triggered?

On 3/15/20 7:41 AM, Šimon Let wrote: > Hi All, > > I'm using PROMPT_COMMAND and DEBUG trap to emulate "PRE" and "POST" hooks > in bash. I have run into the issue where the DEBUG trap gets triggered when > any custom readline widget/function is executed. I would like to > programmatically determine