Re: Follow-up on PROMPT_COMMAND bug report (submitted today)

From	"Franklin, Jason" <jason.franklin@quoininc.com>
Newsgroups	gnu.bash.bug
Subject	Re: Follow-up on PROMPT_COMMAND bug report (submitted today)
Date	2020-04-15 14:48 -0400
Organization	Quoin, Inc.
Message-ID	<mailman.354.1586976506.3066.bug-bash@gnu.org> (permalink)
References	<d4eee50f-6d0f-9ffe-cea9-be713a1cbfac@quoininc.com> <8e03e3c8-5323-1b78-840c-9e16d8d001c6@case.edu> <55bec9bc-6681-467e-4a12-dbc4f8ed5605@quoininc.com>

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On 4/15/20 2:44 PM, Chet Ramey wrote:
> On 4/15/20 11:45 AM, Franklin, Jason wrote:
>> 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 didn't see any bug report. Maybe resend it?
> 

Interesting.

The "bashbug" program must not be working for me, or (more likely) I'm
not using it correctly.  I will send an email here directly that
describes the problem.

Thanks for letting me know!

-- 
Jason Franklin

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

Thread

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

csiph-web