MacOS kitty zsh
being non-login shell but kitty $(which zsh)
is login shell
#7359
Replies: 2 comments 2 replies
-
kitty instances are not subprocesses of a login shell. When kitty is
running the users *default systemwide login shell* it will run it using the login
process, in login mode. This is harmless beyond creating noise in the
process tree. If you dont want this behavior for some reason, then set
your default shell to something else and set shell in kitty to the
actual shell you want to run and it wont run in login mode.
|
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
SPiCaRiA
-
The typical solution for this is to configure your path as you want it,
either in kitty.conf or in your shell rc files rather than depending on
path_helper.
For instance in my zshenv I have
```
# Add to PATH uniquely
typeset -U path
path=(~/.local/bin "$path[@]")
path=(~/bin "$path[@]")
```
Or define a functiona named kitty in your zshrc that clears PATH when
running kitty.
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I read somewhere else before (can't remember which issue :x) that Kitty by default opens as login shell under macOS to align with its wierd behavior. However, I feel that I don't want Kitty instances being subprocess of a login shell to mimick the same thing, which doesn't make much sense to me.
Not wanting to change the behavior of parent process being login shell, I am trying to alias kitty instead of setting the
shell
option inkitty.conf
. Here comes the confusion: ideally, I want to create an alias likekitty $SHELL
so it works regardless of the shell, but this (as well askitty $(which zsh)
) still starts as a login shell.kitty zsh
works as a non-login shell though.Thank you for any information regarding my question/purpose!
Beta Was this translation helpful? Give feedback.
All reactions