From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: RFH: bash completion performance
Date: Fri, 2 Feb 2024 23:25:00 +0000 [thread overview]
Message-ID: <20240202232500.M134686@dcvr> (raw)
I noticed bash completion for lei gets really slow with gigantic
candidate lists. It's not lei's fault, rather bash being
inefficient when fed a gigantic list:
https://marc.info/?i=20240110052801.M32409@dcvr
Chet (bash maintainer) gave a detailed reply here which
I haven't had time to act on:
https://marc.info/?i=9ef19570-ac1b-47d4-8e8b-aca69f958327@case.edu
I've already got a lot on my plate in public-inbox itself, so
hopefully another C hacker here can optimize it for us.
(I figure there's more people proficient with C reading this
inbox than there are with Perl, maybe I'm wrong...)
reply other threads:[~2024-02-02 23:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240202232500.M134686@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).