zsh-users
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: New zplugin feature (was: Re: How completions work, do they require fpath?)
Date: Wed, 10 Feb 2016 10:19:50 +0100	[thread overview]
Message-ID: <CAKc7PVAkV2BAEQ6dX-O3Qfc4xfrzrvJ9bim83o+0m1EifEggkQ@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVBWKfwV7iCBSw4R+gfes=dw1YHB-dAUAh4PRM2dtcUG=Q@mail.gmail.com>

Well, actually, antigen snippet I showed implements this too :D In
Advanced Bash Scripting Guide style (thus not fast), but still, they
do it.

Best regards,
Sebastian Gniazdowski


On 10 February 2016 at 10:08, Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
> On 31 January 2016 at 20:26, Bart Schaefer <schaefer@brasslantern.com> wrote:
>> You could try this:  Define your own "compdef" whose only action is
>> to cache its arguments somewhere.  Load all the plugins, then after
>> compinit is run, play back the cached compdef arguments with the real
>> compdef.
>
> I realized how great that idea is. Implemented it in zplugin, thus an
> idiom is possible:
>
> source '/Users/sgniazdowski/.zplugin/bin/zplugin.zsh'
> zplugin load "some1/plugin1"
> zplugin load "some2/plugin2"
> ...
> zplugin load "some3/plugin3"
> autoload -Uz compinit
> compinit
> zplugin cdreplay -q # -q is quiet
>
> The difference between running compinit once and twice is huge,
> following time differences are possible:
> zsh -i -c exit  0,73s user 0,25s system 99% cpu 0,980 total
> zsh -i -c exit  0,11s user 0,04s system 97% cpu 0,156 total
> (for 3 plugins)
> zsh -i -c exit  1,24s user 0,41s system 99% cpu 1,667 total
> zsh -i -c exit  0,48s user 0,18s system 98% cpu 0,668 total
> (for 40 plugins)
>
> This is a very innovative, great thing. All current plugin managers
> drifted towards double compinit calling, by force of lack of
> shadowing:
> https://github.com/tarjoilija/zgen/blob/master/zgen.zsh#L471-L475
> https://github.com/zsh-users/antigen/blob/master/antigen.zsh#L441-L462
>
> OMZ slowness is I guess also result of this.
>
> Fun example:
> % unfunction compdef
> % zplg dtrace
> % compdef _ls cp
> % zplg dstop
> % zplg cdlist
> Recorded compdefs:
> compdef _ls cp
> % zplg cdreplay
> Compinit isn't loaded, cannot do compdef replay
> % autoload -Uz compinit
> % compinit
> % zplg cdreplay
> Running compdef _ls cp
> % echo $_comps[cp]
> _ls
>
> Best regards,
> Sebastian Gniazdowski


  reply	other threads:[~2016-02-10  9:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10  9:08 Sebastian Gniazdowski
2016-02-10  9:19 ` Sebastian Gniazdowski [this message]
2016-02-10 13:15   ` Sebastian Gniazdowski

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=CAKc7PVAkV2BAEQ6dX-O3Qfc4xfrzrvJ9bim83o+0m1EifEggkQ@mail.gmail.com \
    --to=sgniazdowski@gmail.com \
    --cc=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).