From: zzapper <zsh@rayninfo.co.uk>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: zstat
Date: Tue, 3 May 2022 16:11:47 +0100 [thread overview]
Message-ID: <9027a735-bc24-ca29-c2f3-6d47ea0b83bc@rayninfo.co.uk> (raw)
In-Reply-To: <CAH+w=7aNqirVQ58X1JKS33hLHkqiN+gc7UMxdwSQLj2Qi9aRuQ@mail.gmail.com>
On 03/05/2022 15:54, Bart Schaefer wrote:
> On Tue, May 3, 2022 at 7:25 AM zzapper <zsh@rayninfo.co.uk> wrote:
>
> Place this in your .zshenv:
>
> function zmodload() { builtin zmodload "$@" }
> functions -T zmodload
>
> This should print a trace each time zmodload is run. (If it doesn't,
> check that you haven't changed $ZDOTDIR)
>
> Then run
>
> zsh -o sourcetrace
>
> which traces one line for every file read with the "source" or "."
> commands. Between the two you should be able to see exactly where
> zsh/stat is coming from.
Bart
function zmodload() { builtin zmodload "$@" }
functions -T zmodload
I guess the following generically loads anything in zsh/files ?
+zmodload:0> zmodload -F zsh/files b:zf_chown b:zf_mv b:zf_rm
zzapper
next prev parent reply other threads:[~2022-05-03 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 14:25 zstat zzapper
2022-05-03 14:54 ` zstat Bart Schaefer
2022-05-03 15:11 ` zzapper [this message]
2022-05-03 15:57 ` zstat Peter Stephenson
2022-05-03 16:34 ` zstat zzapper
2022-05-04 0:36 ` zstat Bart Schaefer
2022-05-04 6:43 ` zstat zzapper
2022-05-04 7:18 ` zstat Bart Schaefer
2022-05-04 9:31 ` zstat david rayner
2022-05-04 9:49 ` zstat Roman Perepelitsa
2022-05-04 12:09 ` zstat david rayner
2022-05-04 12:26 ` zstat zzapper
2022-05-04 13:21 ` zstat Peter Stephenson
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=9027a735-bc24-ca29-c2f3-6d47ea0b83bc@rayninfo.co.uk \
--to=zsh@rayninfo.co.uk \
--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).