On 1/8/20 2:38 PM, Daniel Colascione wrote:
On Tue, Sep 24, 2019 at 10:20 PM Daniel Colascione <dan...@google.com> wrote:

On Mon, Sep 23, 2019 at 6:36 AM Chet Ramey <chet.ra...@case.edu> wrote:

On 9/23/19 7:32 AM, Daniel Colascione wrote:
On Wed, Jan 9, 2019 at 12:37 PM Chet Ramey <chet.ra...@case.edu> wrote:

On 1/9/19 2:39 PM, Daniel Colascione wrote:
Any chance we can revive this patch now that Bash 5 is out? (The patch
itself, of course, would need to be rebased.)

Yes, I plan to.

Have you had a chance to look at the patch?

Sorry, I have not. I need a bigger chunk of time than I've had available
to figure out the intent of the patches, and whether they're a good idea
to include in readline, before looking closely at the code.

I've had a people tell me that this patch is very useful for helping
them understand editing operations and pasting. I sent this patch over
a year and a half ago. Should I expect another year and a half of
pinging this thread? :-)

Is there anything I can do to get this patch looked at?

I haven't taken the time to sit down and look at it.  That's my bad.

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    c...@case.edu    http://tiswww.cwru.edu/~chet/

  • Re: [PATCH... Daniel Colascione
    • Re: [... Chet Ramey
      • R... Daniel Colascione
        • ... Chet Ramey
          • ... Daniel Colascione
            • ... Chet Ramey
              • ... Daniel Colascione
                • ... Daniel Colascione
                • ... Chet Ramey
                • ... Daniel Colascione
                • ... Chet Ramey
                • ... Daniel Colascione
                • ... Chet Ramey
    • Re: [... gentoo_eshoes--- via Bug reports for the GNU Bourne Again SHell
      • R... Chet Ramey
        • ... gentoo_eshoes--- via Bug reports for the GNU Bourne Again SHell
          • ... Chet Ramey
            • ... gentoo_eshoes--- via Bug reports for the GNU Bourne Again SHell
              • ... Chet Ramey

Reply via email to