From: "Thomas A. Christensen II" <tchristensen@vet.k-state.edu>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Function definition file not found for default functions
Date: Thu, 19 Aug 2021 18:01:24 -0500 [thread overview]
Message-ID: <8006a280-4b97-9c5e-1a29-2a8c9bc69e91@vet.k-state.edu> (raw)
In-Reply-To: <CAH+w=7bvvrhQXm6EZvx2kjSJqVYgiHh5TC8mLp6X7cwQ4K5O8Q@mail.gmail.com>
> This means your $fpath value is not covering the directories where
> these functions are defined.
Ahh, thanks. Lmod was the only thing in fpath (might need to ask the
admins about that), but adding
fpath+=($HOME/.local/share/zsh/5.8/functions)
to my .zshenv solved the problem.
prev parent reply other threads:[~2021-08-19 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 20:15 Thomas A. Christensen II
2021-08-19 22:28 ` Bart Schaefer
2021-08-19 23:01 ` Thomas A. Christensen II [this message]
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=8006a280-4b97-9c5e-1a29-2a8c9bc69e91@vet.k-state.edu \
--to=tchristensen@vet.k-state.edu \
--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).