zsh-users
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: zzapper <david@rayninfo.co.uk>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: How many Active Zsh Frameworks?
Date: Sun, 6 Mar 2016 18:17:31 +0100	[thread overview]
Message-ID: <CAKc7PVB=yOD314kH3-DZtusep3aOB=AEd-niKf+kk2J=p5DVMA@mail.gmail.com> (raw)
In-Reply-To: <XnsA5C2DA3EC461Cdavidrayninfocouk@80.91.229.13>

Antigen is written in Advanced Bash Scripting guide style. It does
forks for its operations, which are slow. In my one test loading 40
plugins takes 4.906 seconds on Antigen. I would recommend you my
Zplugin:

https://github.com/psprint/zplugin

Written with cooperation with people from this mailing list, fast (0.6
seconds for the same 40 plugins, 0.3 seconds when using "light" mode)
and advanced (e.g. completions management, automatic plugin
compilation), supporting OMZ themes via snippet feature, keeping
$FPATH clean (for 40 plugins FPATH has 40 entries with all other
frameworks).

Best regards,
Sebastian Gniazdowski


On 5 March 2016 at 22:27, zzapper <david@rayninfo.co.uk> wrote:
> Andrew Janke <floss@apjanke.net> wrote in news:56DB1BB5.4010403
> @apjanke.net:
>
>> https://github.com/unixorn/awesome-zsh-plugins
>
> looks like omz, pretzo and antigen in that order according to the star
> count.
> Early results of my  poll seem to suggest most zsh users do use a framework
>
> --
> zzapper
> https://twitter.com/dailyzshtip
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>


  reply	other threads:[~2016-03-06 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05 12:50 zzapper
2016-03-05 17:47 ` Andrew Janke
2016-03-05 21:27   ` zzapper
2016-03-06 17:17     ` Sebastian Gniazdowski [this message]
2016-03-07 15:57 ` Marc Chantreux

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='CAKc7PVB=yOD314kH3-DZtusep3aOB=AEd-niKf+kk2J=p5DVMA@mail.gmail.com' \
    --to=sgniazdowski@gmail.com \
    --cc=david@rayninfo.co.uk \
    --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).