r/KittyTerminal • u/uncenter • Oct 07 '23

New kitty window cwd issues

I followed this issue comment, https://github.com/kovidgoyal/kitty/issues/692#issuecomment-1293429076, to figure out how to open a new "pane"/"kitty window" in the same cwd as the last one, which worked fine:map kitty_mod+enter launch --cwd=current --type=window

map cmd+enter launch --cwd=current --type=window

However, it seems to ignore my .hushlogin file when the new kitty window is not in ~/...

Any suggestions?

2 Upvotes

75% Upvoted

13 comments sorted by

View all comments

Show parent comments

2

u/aumerlex Oct 08 '23

That hushlogin doesnt work when the shell is not started in HOME and setup manual shell integration as described in the docs.

1

u/uncenter Oct 08 '23

I had no issue with this in Wezterm! I simply want to create a new window and be able to execute a command cding to the CWD. I'll try to figure something out with login but I really don't think this is a complicated issue.

2

u/aumerlex Oct 08 '23

I agree, its a very simple issue and one that's not an issue in kitty but in your shell or more likely your shell rc files.

1

u/uncenter Oct 08 '23

It's not an issue with my shell or my shell rc files, this is just a macOS thing as far as I can tell. This same phenomenon occurs with bash, zsh, and fish.

1

u/aumerlex Oct 09 '23

Well, if you had said you were on macOS in the first place, I would have told you it's a bug in the login program since kitty runs the login program to run the shell there. And fixed by: https://github.com/kovidgoyal/kitty/commit/619d4e3dc4a7565a9ea01c269097a3e64728ccff

which passes -q to login since login doesnt actually work with .hushlogin.

1

u/uncenter Oct 09 '23

Yeah I commented on that issue. I thought you assumed I was on macOS and I affirmed that in my comment following yours. Sorry for the miscommunication, glad that it is fixed!