Closed Redoubts closed 1 year ago
Hi. FYI, the discussion around this new implementation was at #12.
Looks like you have a too broad fpath, do you need all of
/usr/share/zsh/functions/Completion/AIX/*
/usr/share/zsh/functions/Completion/BSD/*
/usr/share/zsh/functions/Completion/Base/*
/usr/share/zsh/functions/Completion/Cygwin/*
/usr/share/zsh/functions/Completion/Darwin/*
/usr/share/zsh/functions/Completion/Debian/*
/usr/share/zsh/functions/Completion/Linux/*
/usr/share/zsh/functions/Completion/Mandriva/*
/usr/share/zsh/functions/Completion/Redhat/*
/usr/share/zsh/functions/Completion/Solaris/*
/usr/share/zsh/functions/Completion/Unix/*
/usr/share/zsh/functions/Completion/X/*
/usr/share/zsh/functions/Completion/Zsh/*
/usr/share/zsh/functions/Completion/openSUSE/*
completion functions?
EDIT: I see you're also using some_nfs_directory. Network file systems will potentially bring a considerable performance downgrade in general.
Yeah, this is kinda user error that I can fix locally. But I noticed that .zim/init.zsh
seems to try to fully resolve the path of ZIM_HOME (or however all those source ../.zim/modules/..
lines are built out).
I have a complex corp setup, where /home
is mounted on NFS, and that path resolves to different places depending on host. Whenever .zim/init.zsh
updates (presumably very rarely), it fully resolves based on one host, but that resolved path can be much slower other hosts. I wonder if it's worth leaving symlinks as they are.
Yes, we resolve all symlinks when building ~/.zim/init.zsh
. I wonder what would be the downside of not doing that anymore, if there are any.
Released version 1.12.0 which does not resolve symlinks when building ~/.zim/init.zsh anymore.
I'm noticing very slow startup of my shell, and when I look at
zsh -x
output, it seems that this plugin is the cause. I can trace it to init.zsh doingwhich expands to.
(splayed out for clarity, directories redacted for privacy)
Is there any way I can disable this or mitigate some how?