You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running the latest BAT tool on my macOS M2 chip. whenever I tried to open the horizontal pane, I got the below msg. login banner. I want to remove it. I have a ".hushlogin " file created even though Kitty print msg saying "Last login: Mon Oct 9 00:35:57 on ttys001" Please how me know how to remove this login banner
@kovidgoyal thanks for quick help. so you means shell with --login option if yes then I am not using this option even then I have this last login issue
@uncenter, thanks for confirming. Here is mine with kitty --config=NONE, strange:
Unfortunately, I'm not sure how to troubleshoot this, but I'm happy to provide any info or be pointed in the right direction to look into this further. I wonder if this could just be something on my end, although it was working fine before the changes about a month ago.
I think this was just about the login message being displayed when a new kitty window was created not in the home directory since login wouldn't recognize .hushlogin. Personally it wouldn't make sense for kitty to disable the login message by default since that's a user preference, so yeah you still need that file. Glad it's working though!
I have also started seeing the Last login: Sat Dec 23 15:59:20 on ttys006 message on latest kitty (on macOS). After looking through the changelogs and commits, my understanding is that kitty 0.30.1 started using login which started printing this message:
macOS: When running the default shell, run it via the login program so that calls to getlogin() work (:iss:6511)
And then kitty 0.31.0 fixed ~/.hushlogin being respected:
macOS: When running the default shell with the login program fix :file:~/.hushlogin not being respected when opening windows not in the home directory (:iss:6689)
So as I understand it the new expectation is that you should touch ~/.hushlogin if you don't want to see this message. This would be great to include in the kitty docs somewhere , or maybe in the changelog. My initial understanding from this thread was that the ~/.hushlogin file was no longer needed.
This si nothing to do with kitty. macOS expects terminals to start login
shells and login shells show that message without hushlogin, you will
see the same behavior in any terminal on macOS.
In general sure, but specifically the feature of "we show a message without hushlogin" wasn't a thing on kitty until recently, so when I bisect "what changed recently" to work out which tool to look at, kitty is what comes up.
Reacted by Valerio Viperino and Sam A. Horvath-Hunt
Activity
uncenter commentedon Oct 8, 2023
Coincidentally I made a related Reddit thread earlier (https://www.reddit.com/r/KittyTerminal/comments/172d6m1/new_kitty_window_cwd_issues/). When kitty creates a new pane/kitty window in a directory that isn't the home directory, login(1) doesn't find the
.hushloginfile.uncenter commentedon Oct 9, 2023
Thanks!
ciscohack commentedon Oct 9, 2023
@kovidgoyal thanks for quick help. so you means shell with --login option if yes then I am not using this option even then I have this last login issue
ciscohack commentedon Oct 9, 2023
i think i found the answer what you means you means I should run the kitty with like this shell --login -q
kovidgoyal commentedon Oct 9, 2023
No you should need to update to next kitty build or use the nightly from tomorrow.
ciscohack commentedon Oct 9, 2023
oh my bad thanks but do i need any config modification or upgrade to nightly will be enough to get rid of this login banner msg
uncenter commentedon Nov 8, 2023
Works like a charm on
v0.31.0! Thanks again!avnigo commentedon Nov 19, 2023
Is this actually fixed after 32b7be2? It doesn't seem to be working for me on
v0.31.0, but I didn't get a chance to try 619d4e3 either.uncenter commentedon Nov 19, 2023
I'm just on the latest version AFAIK and it works fine:
Screenshot.2023-11-19.at.12.28.59.kitty.mp4
avnigo commentedon Nov 19, 2023
@uncenter, thanks for confirming. Here is mine with
kitty --config=NONE, strange:Unfortunately, I'm not sure how to troubleshoot this, but I'm happy to provide any info or be pointed in the right direction to look into this further. I wonder if this could just be something on my end, although it was working fine before the changes about a month ago.
uncenter commentedon Nov 19, 2023
Just to verify - you have a
~/.hushlogin? That looks like you don't since it doesn't even work in the root directory.avnigo commentedon Nov 19, 2023
I didn't as I understood that the update was going to fix having to add that file, but I added it now and it worked, thanks a lot!
uncenter commentedon Nov 19, 2023
I think this was just about the login message being displayed when a new kitty window was created not in the home directory since
loginwouldn't recognize.hushlogin. Personally it wouldn't make sense for kitty to disable the login message by default since that's a user preference, so yeah you still need that file. Glad it's working though!gibfahn commentedon Dec 23, 2023
I have also started seeing the
Last login: Sat Dec 23 15:59:20 on ttys006message on latest kitty (on macOS). After looking through the changelogs and commits, my understanding is that kitty 0.30.1 started usingloginwhich started printing this message:And then kitty 0.31.0 fixed
~/.hushloginbeing respected:So as I understand it the new expectation is that you should
touch ~/.hushloginif you don't want to see this message. This would be great to include in the kitty docs somewhere , or maybe in the changelog. My initial understanding from this thread was that the~/.hushloginfile was no longer needed.kovidgoyal commentedon Dec 23, 2023
This si nothing to do with kitty. macOS expects terminals to start login
shells and login shells show that message without hushlogin, you will
see the same behavior in any terminal on macOS.
gibfahn commentedon Dec 24, 2023
In general sure, but specifically the feature of "we show a message without hushlogin" wasn't a thing on kitty until recently, so when I bisect "what changed recently" to work out which tool to look at, kitty is what comes up.
paschun commentedon Dec 24, 2023
Excuse me if everyone knows this already, but there is a flag
login -qthat "acts as if a .hushlogin is present"Run login on macOS with -q
Run login on macOS with -q