Closed zippy1981 closed 5 months ago
That looks odd. Does this happen every time you log in?
Yes.
On Thu, Nov 16, 2023, 06:59 Roman Perepelitsa @.***> wrote:
That looks odd. Does this happen every time you log in?
— Reply to this email directly, view it on GitHub https://github.com/romkatv/gitstatus/issues/412#issuecomment-1814305984, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABD34UJW5I6L4RI4SDNQM3YEX5ZDAVCNFSM6AAAAAA7M2F5XGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJUGMYDKOJYGQ . You are receiving this because you authored the thread.Message ID: @.***>
Does it fail fast or after approximately 10 seconds?
About a second
On Thu, Nov 16, 2023, 07:30 Roman Perepelitsa @.***> wrote:
Does it fail fast or after approximately 10 seconds?
— Reply to this email directly, view it on GitHub https://github.com/romkatv/gitstatus/issues/412#issuecomment-1814350083, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABD34VBUWKI5MOZ7IF2LC3YEYBOTAVCNFSM6AAAAAA7M2F5XGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJUGM2TAMBYGM . You are receiving this because you authored the thread.Message ID: @.***>
This is very strange. It looks as if zsh forks and then the child dies immediately.
If you don't need git status in your prompt on that machine, you can comment out "vcs" in ~/.p10k.zsh
. This will avoid the use of gitstatusd although given the forking prompt you might still have a broken shell afterwards.
I tried sshing to my sdf.org account from Windows and Fedora