Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #16138

Follow-up on PROMPT_COMMAND bug report (submitted today)

From "Franklin, Jason" <jason.franklin@quoininc.com>
Newsgroups gnu.bash.bug
Subject Follow-up on PROMPT_COMMAND bug report (submitted today)
Date 2020-04-15 11:45 -0400
Organization Quoin, Inc.
Message-ID <mailman.339.1586970202.3066.bug-bash@gnu.org> (permalink)
References <d4eee50f-6d0f-9ffe-cea9-be713a1cbfac@quoininc.com>

Show all headers | View raw


Greetings:

I realized that I didn't include my email when I used bashbug to report
my issue, so I'm sending a follow-up email so that the maintainers can
be in touch.

I browsed the code and tried to fix the issue myself by modifying the
"prompt_again()" function to execute PROMPT_COMMAND directly.  This
didn't work, and I'm still not sure why.

Maybe the Chet, et al., can make sense of this.  Thanks so much for your
help and for maintaining my favorite shell!

-- 
Jason Franklin

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Follow-up on PROMPT_COMMAND bug report (submitted today) "Franklin, Jason" <jason.franklin@quoininc.com> - 2020-04-15 11:45 -0400

csiph-web