370aff5fcc
* Default to tick-based updates This commit reintroduces code that was previously removed in favor of a notify-based update trigger. It turned out that notify-based updates can cause issues in larger repositories, so tick-based updates seemed like a safer default. https://github.com/extrawurst/gitui/issues/1444 https://github.com/extrawurst/gitui/pull/1310 * Add FAQ entry for --watcher * Remove --poll
1.6 KiB
Table of Contents
1. "Bad Credentials" Error Top ▲
Some users have trouble pushing/pulling from remotes and adding their ssh-key to their ssh-agent solved the issue. The error they get is:
See gihtub's excellent documentation for Adding your SSH Key to the ssh-agent
Note that in some cases adding the line ssh-add -K ~/.ssh/id_ed25519(or whatever your key is called) to your bash init script is necessary too to survive restarts.
2. Custom key bindings Top ▲
If you want to use vi-style keys or customize your key bindings in any other fassion see the specific docs on that: key config
3. Watching for changes Top ▲
By default, gitui polls for changes in the working directory every 5 seconds. If you supply --watcher as an argument, it uses a notify-based approach instead. This is usually faster and was for some time the default update strategy. It turned out, however, that notify-based updates can cause issues on some platforms, so tick-based updates seemed like a safer default.
See #1444 for details.