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

[Greg Wooledge]

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 widget/function is executed. I would like to
> > programmatically determine if the DEBUG trap was triggered for a "real"
> > interactive command or if it was triggered for a custom readline widget.
> Since the DEBUG trap happens before the command executes, it's not a real
> `post-command' hook.

I think they simply stated things backwards.  The DEBUG trap is a
pre-command hook, and PROMPT_COMMAND is post-command.  Sort of/close
enough.

That said, I'm not sure what a "custom readline widget" is.