Replies: 1 comment
-
Compiling |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Disclaimer: new to zsh.
Should autoload functions and completion be zcompiled? I took a glance at zcompile implementations between some plugin managers and have a few questions:
It seems zgenom zcompiles the most appropriate set of files (tests for zsh-parsable, ignores symlinks). It doesn't include autoload functions (unless it has the suffix
.zsh
but glancing over at random dotilfes, the naming scheme seems to be just the name of the function without the suffix--I could be wrong). It also doesn't include completion files. Should these be zcompiled or handled?Would it make sense to compile multiple files into one .zwc file to reduce the number of files every shell init needs to read (or one per "module"? zcompile is usually instant on personal config so I'm not sure if there are introduced downsides. Checking if any one of the files in a .zwc digest was updated to update the digest might not be as straightforward though. This idea is not new, I came across it as a feature request from a project I can't remember.
Is there a general rule for when to use zcompile -M vs -R? I think I understand everything in the manpage except
-R
's:Some of these may not be appropriate for a plugin manager to do but I'm still curious if there are any thoughts.
Much appreciated.
P.S. The only files zgenom missed were .zsh-theme files (I'm not sure if that's a standard naming scheme but I've seem them in other plugin managers, e.g. for files like powerlevel10k.zsh-theme).
Beta Was this translation helpful? Give feedback.
All reactions