Skip to content

Last login msg on latest kitty terminal  #6689

Closed

Description

@ciscohack

Hi Expert,

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

I am running the latest BAT version

image

Activity

  1. uncenter commented on Oct 8, 2023

    @uncenter

    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 .hushlogin file.

  2. uncenter commented on Oct 9, 2023

    @uncenter

    Thanks!

  3. ciscohack commented on Oct 9, 2023

    @ciscohack
    Author

    @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

  4. ciscohack commented on Oct 9, 2023

    @ciscohack
    Author

    i think i found the answer what you means you means I should run the kitty with like this shell --login -q

  5. kovidgoyal commented on Oct 9, 2023

    @kovidgoyal
    Owner

    No you should need to update to next kitty build or use the nightly from tomorrow.

  6. ciscohack commented on Oct 9, 2023

    @ciscohack
    Author

    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

  7. uncenter commented on Nov 8, 2023

    @uncenter

    Works like a charm on v0.31.0! Thanks again!

  8. avnigo commented on Nov 19, 2023

    @avnigo

    Works like a charm on v0.31.0! Thanks again!

    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.

  9. uncenter commented on Nov 19, 2023

    @uncenter

    I'm just on the latest version AFAIK and it works fine:

    Screenshot.2023-11-19.at.12.28.59.kitty.mp4
  10. avnigo commented on Nov 19, 2023

    @avnigo

    @uncenter, thanks for confirming. Here is mine with kitty --config=NONE, strange:

    image

    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.

  11. uncenter commented on Nov 19, 2023

    @uncenter

    Just to verify - you have a ~/.hushlogin? That looks like you don't since it doesn't even work in the root directory.

  12. avnigo commented on Nov 19, 2023

    @avnigo

    Just to verify - you have a ~/.hushlogin?

    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!

  13. uncenter commented on Nov 19, 2023

    @uncenter

    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!

  14. gibfahn commented on Dec 23, 2023

    @gibfahn
    Contributor

    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.

  15. kovidgoyal commented on Dec 23, 2023

    @kovidgoyal
    Owner

    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.

  16. gibfahn commented on Dec 24, 2023

    @gibfahn
    Contributor

    This si nothing to do with kitty.

    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.

  17. paschun commented on Dec 24, 2023

    @paschun

    Excuse me if everyone knows this already, but there is a flag login -q that "acts as if a .hushlogin is present"

  18. added a commit that references this issue on Jan 28, 2024
    619d4e3
  19. added a commit that references this issue on Jul 8, 2026
    ea220d9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions