zsh-workers
 help / color / mirror / code / Atom feed
From: cheer_xiao <xiaqqaix@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: Slow completion when using aptitude
Date: Wed, 26 Jan 2011 13:11:40 +0800	[thread overview]
Message-ID: <AANLkTikAKmnTt+9o5ibUGevk+m=rZJg9WrxV1WP+hX6w@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimYBY7nA_FCXTA8n-ukYwBxnobmoUNowJ6kxaGz@mail.gmail.com>

On Wed, Jan 19, 2011 at 8:33 PM, Richard Hartmann
<richih.mailinglist@gmail.com> wrote:
> Hi,
>
> those questions might be better suited to the -users list.
>
>> And another small related issue: the command tab-completion of zsh
>> doesn't seem to know aptitude build-dep, which has been around for a
>> few years but (unfortunately) undocumented.
>
> I did not have time to check the first issue, but on zsh 4.3.10, you
> can complete to aptitude build-dep. As a general rule of thumb, please
> try to use the newest version of zsh (and starting with zsh -f where
> applicable/possible) before reporting issues. They might have been
> fixed, already.

Thanks for your attention. I posted this to zsh-workers because I
found it weird enough to be very likely a bug in source code. Could
you tell me if you are having performance problem with aptitude
tab-complete? Also, let me describe my problems in more detail.

If I type "sudo apt-get install a" and hit Tab, I only get a short
(yet noticeable) delay of about one second. But when I type "sudo
aptitude install a" and hit Tab, zsh freezes, one of the CPU cores get
100% loaded. It will recover after some 10 seconds. However after
this, the tab-completion of aptitude is as quick as apt-get's, until I
log out of zsh.

I am using the version from git repo:

xiaq@~> zsh --version
zsh 4.3.11-dev-1 (i686-pc-linux-gnu)

and my system:

xiaq@~> uname -a
Linux xxx 2.6.32-28-generic #55-Ubuntu SMP Mon Jan 10 21:21:01 UTC
2011 i686 GNU/Linux

After typing "sudo aptitude" and hitting Tab, the output is (build-dep
is absent):

xiaq@~> sudo aptitude
autoclean                 -- erase old downloaded package files
changelog                 -- view a package's changelog
clean                     -- erase downloaded package files
download                  -- download the .deb file for a package
forbid-version            -- forbid aptitude from upgrading to a
specific package ve
forget-new                -- forget what packages are "new"
full-upgrade              -- perform an upgrade, possibly installing
and removing pa
hold                      -- place packages on hold
install                   -- install/upgrade packages
markauto                  -- mark packages as having been
automatically installed
purge                     -- remove packages and their configuration files
reinstall                 -- download and (possibly) reinstall a
currently installed
remove                    -- remove packages
safe-upgrade              -- perform a safe upgrade
search                    -- search for a package by name and/or expression
show                      -- display detailed information about a package
unhold                    -- cancel a hold command for a package
unmarkauto                -- mark packages as having been manually installed
update                    -- download lists of new/upgradable packages
why                       -- show the manually installed packages that
require a pac
why-not                   -- show the manually installed packages that
lead to a con


  reply	other threads:[~2011-01-26  5:12 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 [this message]
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
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='AANLkTikAKmnTt+9o5ibUGevk+m=rZJg9WrxV1WP+hX6w@mail.gmail.com' \
    --to=xiaqqaix@gmail.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).