zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Are completions in some way heavy?
Date: Mon, 6 Jun 2016 09:01:04 -0700	[thread overview]
Message-ID: <160606090104.ZM11947@torch.brasslantern.com> (raw)
In-Reply-To: <CAKc7PVBnpkEnkWZb4yh9BgutbBgfKS0Hh1x6e_Q-jnOyVDHQOg@mail.gmail.com>

On Jun 6,  2:43pm, Sebastian Gniazdowski wrote:
}
} This should provide speed up, to start with 15 enabled completions,
} instead of 800 [...]
} 
} That's a failure but I thought that maybe shell will be much lighter
} with <100 completions pre-loaded? Maybe situation with compsys isn't
} that bright because of the number of _* files? How can I reveal
} effects of much lighter $functions, etc., is it possible?

Functions that are marked for autoloading but haven't yet loaded are
already very lightweight.  That was one reason for using a suite of
files, so the autoload mechanism could take care of ignoring those
that are never needed in a particular session.  Then compdump avoids
the overhead of scanning directories to find those files.

Making it the user's responsibility to explicitly choose what to enable
is exactly what we wanted to *avoid*.  If that's a requirement in order
for the system to be "light enough" then we have failed.
 
} Also, overall, it would be nice that I would collect all mainstream _*
} patches, and provide the completions for all Zsh versions.

Having a location from which to grab .../share/$ZSH_VERSION/functions/
trees for past zsh releases would be useful, particularly if fixes from
more recent versions were backported when possible.

I would not suggest attempting to create forward-portable versions of
the functions.


  reply	other threads:[~2016-06-06 16:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 12:43 Sebastian Gniazdowski
2016-06-06 16:01 ` Bart Schaefer [this message]
2016-06-06 19:28   ` Sebastian Gniazdowski
2016-06-07 20:44     ` Bart Schaefer
2016-06-08  4:34       ` Sebastian Gniazdowski
2016-06-08  9:03         ` Oliver Kiddle
2016-06-08 18:40           ` Bart Schaefer
2016-06-10 12:22             ` Sebastian Gniazdowski
2016-06-10 17:42               ` Bart Schaefer
2016-06-11  7:15                 ` Sebastian Gniazdowski
2016-06-11 17:18                   ` Bart Schaefer
2016-06-11 17:44                     ` Sebastian Gniazdowski
     [not found]           ` <160608114009.ZM807__13786.2274809324$1465411295$gmane$org@torch.brasslantern.com>
2016-06-10 17:35             ` Daniel Shahaf
2016-06-10 19:49               ` Bart Schaefer
     [not found] ` <160606090104.ZM11947__15732.477248139$1465228961$gmane$org@torch.brasslantern.com>
2016-06-07 22:53   ` Daniel Shahaf

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=160606090104.ZM11947@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@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).