From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: david rayner <david@rayninfo.co.uk>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: zstat
Date: Wed, 4 May 2022 11:49:53 +0200 [thread overview]
Message-ID: <CAN=4vMrJs+i=8RvkqFPALAmXTEqTKsr0pNYzMwKvjrE0kMU+2g@mail.gmail.com> (raw)
In-Reply-To: <a44d6ced-26ff-a26d-58d2-195f6645d36b@rayninfo.co.uk>
> # OK I have now 'deleted' my .zshrc (kept a copy of course)
>
> # I get the following 'odd' behaviour
>
> If I start a new gnome terminal I have zstat
>
> mint-HP-600B% zstat
>
> zstat: no files given
>
>
> # but if i reload zsh
>
> mint-HP-600B% zsh
> mint-HP-600B% zstat
>
> zsh: command not found: zstat
Which terminal are you using?
There are several terminals out there that inject extra initialization
code into the shell that they spawn. This initialization code usually
runs between global and user zshenv and is meant to enable tighter
integration between the terminal and the shell. In practice all such
code has side effects and can leak or break things. The terminals I'm
aware of that do this are Kitty, Integrated Visual Studio Terminal,
Integrated IntelliJ Terminal, Warp, and Fig. When you manually run
`zsh` in a terminal of this kind, the new shell won't run the extra
initialization code.
Roman.
next prev parent reply other threads:[~2022-05-04 9:50 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 ` zstat zzapper
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 ` Roman Perepelitsa [this message]
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='CAN=4vMrJs+i=8RvkqFPALAmXTEqTKsr0pNYzMwKvjrE0kMU+2g@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=david@rayninfo.co.uk \
--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).