zsh-users
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Zach Riggle <zachriggle@gmail.com>
Cc: Mikael Magnusson <mikachu@gmail.com>, Zsh Users <zsh-users@zsh.org>
Subject: Re: Shell startup, aliases vs. functions vs. autoloadable functions, and zcompile benefits
Date: Tue, 30 Nov 2021 13:30:18 +0100	[thread overview]
Message-ID: <CAN=4vMrsCFbtyJLPa0yj-7GyG8GycOkQ=8q4_YbqyRzVyXeXDg@mail.gmail.com> (raw)
In-Reply-To: <CAMP9c5kuUtuPO=JjefwEWU_gTxLs4vN7cvqxyZNMC3e6J+ESLA@mail.gmail.com>

On Tue, Nov 30, 2021 at 12:49 PM Zach Riggle <zachriggle@gmail.com> wrote:
>
> > FWIW, I zcompile my own rc files
>
> What is the optimal way to compile a huge set of them?

Most of the zsh files you are using are *installed* rather than
modified by yourself. You can zcompile them when you install/update
them. E.g., you have some code that installs/updates prezto. Invoke
zcompile in there.

There are also zsh startup files that you modify manually every now
and then (.zshrc, etc.). Compiling these files is harder and is more
likely to cause issues. On the other hand, the benefits of compiling
them are tiny, simply because those files are tiny. Once again, you
can manually zcompile different things and check whether you notice
any difference. If you don't, there is no need to invest in
zcompiling.

If first_prompt_lag of your shell is 600ms, zcompiling won't have
noticeable effects. You'll need to optimize other things first for
zcompiling to matter.

Roman.


  reply	other threads:[~2021-11-30 12:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27  8:10 Zach Riggle
2021-11-27  8:33 ` Roman Perepelitsa
2021-11-27 20:22   ` Bart Schaefer
2021-11-30  2:30     ` Zach Riggle
2021-11-30  4:11       ` Bart Schaefer
2021-11-30  8:18         ` Zach Riggle
2021-11-30  7:51       ` Roman Perepelitsa
2021-11-30  8:10         ` Mikael Magnusson
2021-11-30  8:27           ` Mikael Magnusson
2021-11-30  8:30             ` Zach Riggle
2021-11-30  9:11             ` Roman Perepelitsa
2021-11-30 11:49               ` Zach Riggle
2021-11-30 12:30                 ` Roman Perepelitsa [this message]
2021-11-30 15:10                   ` Zach Riggle
2021-11-30 16:37                     ` Bart Schaefer
2021-11-30 16:41                       ` Roman Perepelitsa
2021-11-30  8:29           ` Roman Perepelitsa
2021-11-30  8:25         ` Zach Riggle

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='CAN=4vMrsCFbtyJLPa0yj-7GyG8GycOkQ=8q4_YbqyRzVyXeXDg@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=mikachu@gmail.com \
    --cc=zachriggle@gmail.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).