From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Slow completion when using aptitude
Date: Sat, 05 Feb 2011 09:46:11 -0800 [thread overview]
Message-ID: <110205094611.ZM26274@torch.brasslantern.com> (raw)
In-Reply-To: <AANLkTindKuTD9-AEmxX0Q_CKAykVNO04HMmA26Pq7q0J@mail.gmail.com>
On Feb 5, 5:30pm, cheer_xiao wrote:
}
} Well, the fix is here, simpler than I thought. You missed a line here:
} cachevar=_deb_packages_cache_uninstalled
Yeah, as soon as you said the package list hadn't changed when the
_dep -> _deb typo got fixed, I realized I'd failed to copy that
assignment from the original function.
} On the other hand, I think the performance can be further improved. A
} delay of 1s is good enough for me but not good enough for some.
There are a whole slew of completion functions that take 1s or more, so
if there are people who are unhappy with this one, they're going to be
unhappy in general. My response would be, consider how long it would
take to get the same information if you didn't have the completion.
Also the second and subsequent times you use it in the same shell, it
should be as fast as it's theoretically possible for it to be without a
C-code level optimization deeper in compsys, because the arrays will
all have been populated already.
next prev parent reply other threads:[~2011-02-05 17:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 9:51 cheer_xiao
2011-01-19 12:33 ` Richard Hartmann
2011-01-26 5:11 ` cheer_xiao
2011-01-26 7:51 ` Julien Nicoulaud
2011-01-26 8:35 ` Frank Terbeck
2011-01-26 14:21 ` cheer_xiao
2011-01-26 14:55 ` Frank Terbeck
2011-01-26 17:05 ` Bart Schaefer
2011-01-26 17:29 ` Bart Schaefer
2011-01-30 2:49 ` cheer_xiao
2011-01-30 5:16 ` Bart Schaefer
2011-01-30 5:53 ` cheer_xiao
2011-01-30 7:15 ` Bart Schaefer
2011-01-30 10:40 ` Julien Nicoulaud
2011-01-30 10:51 ` Julien Nicoulaud
2011-01-30 11:18 ` cheer_xiao
2011-01-31 0:02 ` Bart Schaefer
2011-02-03 10:21 ` cheer_xiao
2011-02-03 14:56 ` Bart Schaefer
2011-02-04 3:24 ` cheer_xiao
[not found] ` <AANLkTinfzf6gM5Z83_+iQqkc+QVzGGKa3yqbPTa+Wm3A@mail.gmail.com>
[not found] ` <110203193315.ZM22047@torch.brasslantern.com>
2011-02-04 3:44 ` cheer_xiao
2011-02-04 3:48 ` cheer_xiao
2011-02-04 4:29 ` Bart Schaefer
2011-02-04 5:46 ` cheer_xiao
2011-02-04 15:04 ` Bart Schaefer
2011-02-05 9:13 ` cheer_xiao
[not found] ` <AANLkTinftiPPV-TtNU5DQ1+TV6Tb5P6AprBsRGdjoamB@mail.gmail.com>
2011-02-05 9:21 ` cheer_xiao
2011-02-05 9:30 ` cheer_xiao
2011-02-05 17:12 ` gi1242+zsh
2011-02-05 17:48 ` Bart Schaefer
2011-02-05 18:40 ` gi1242+zsh
2011-02-05 17:46 ` Bart Schaefer [this message]
2011-02-03 10:23 ` cheer_xiao
2011-02-03 14:51 ` Bart Schaefer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=110205094611.ZM26274@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).