Luka Markušić

Is this a problem only with `vim-fubitive`, or with `vim-fugitive`?

Alright, could you please give me the steps to try and reproduce it?

I guess the PR #34 could fix this behaviour. Could you please try it out to see if it helps?

I'd leave this open so we have it at hand in case the current approach _does_ break at some point, but I wouldn't merge it if nobody has complained so...

No problem! Here's the log in its entirety. ``` INFO:root:scli 0.7.0-2-g506ca72 DEBUG:root:urwid 2.1.2 DEBUG:root:python 3.10.2 (main, Jan 15 2022, 19:56:27) [GCC 11.1.0] DEBUG:root:script hash: 038868f8d7a1e8167bd8282ab07331df00b1d6f3 DEBUG:root:signal-cli account: linked device DEBUG:root:MainWindow.keypress:...

Are there any plans to make a periodic history save? E.g. once a day or something, just so one doesn't have to manually quit and start the chat again?

> I second this request. It's very irritating that I have to use my mouse at all. Can't you `` beteeen them?

How would you check it manually?

You can use the `lazydocker-bin` until the issue is fixed, both `lazydocker` and `lazydocker-git` seem to be affected with `-flto`, but I'm not sure where it's originating from.

Bisect points to [this](https://github.com/jesseduffield/lazydocker/commit/d2fa5e9e9c81abc3e100eec9bfc8c808e62853ed).