Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: zstat

X-seq: zsh-users 27720
From: zzapper <zsh@xxxxxxxxxxxxxx>
To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
Cc: Zsh-Users List <zsh-users@xxxxxxx>
Subject: Re: zstat
Date: Tue, 3 May 2022 16:11:47 +0100
Archived-at: <https://zsh.org/users/27720>
In-reply-to: <CAH+w=7aNqirVQ58X1JKS33hLHkqiN+gc7UMxdwSQLj2Qi9aRuQ@mail.gmail.com>
List-id: <zsh-users.zsh.org>
References: <e01cd4e5-97d9-d256-4ae5-f1ce80ac5194@rayninfo.co.uk> <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@xxxxxxxxxxxxxx> 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

Follow-Ups:
- Re: zstat
  - From: Peter Stephenson

References:
- zstat
  - From: zzapper
- Re: zstat
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author