Path: csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From: =?UTF-8?Q?=C5=A0imon_Let?= <simon.a.let@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Q: Is there a way to tell why DEBUG trap was triggered?
Date: Sun, 15 Mar 2020 12:41:36 +0100
Lines: 21
Approved: bug-bash@gnu.org
Message-ID: <mailman.2744.1584272511.2412.bug-bash@gnu.org>
References: <CAOdNpm_9gFMXFJigxYgSVHgWwKdA0XE-TvbabXSs85d=R6WREQ@mail.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
Precedence: list
Xref: csiph.com gnu.bash.bug:16032

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.

I tried to use READLINE_LINE and READLINE_POINT variables but these are not
set during the DEBUG trap.

Is there another way that can be used to determine why the DEBUG trap was
triggered?

PS: I'm wondering what is your opinion on providing PRE and POST functions
natively in bash?


Thank you,

=C5=A0imon Let