feat: pretty print top level errors (#553)
feat: pretty print top level errors (instead of using Debug derive)
ran rustfmt
ran cargo fmt instead (2024 edition is different)
Co-authored-by: altsem alltidsemester@pm.me
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
It’s Gitu! - A Git porcelain outside of Emacs
A terminal user interface for Git. Inspired by Magit.
Features
Gitu aims to implement many of the core features of Magit over time. It should be familiar to any previous Magit users.
Here’s a list of so-far supported features:
Keybinds
Keybinds try mimic Magit, while staying Vim-like. A help-menu can be shown by pressing the
hkey, or by configuringgeneral.always_show_help.enabled = trueConfiguration
The environment variables
VISUAL,EDITORorGIT_EDITOR(checked in this order) dictate which editor Gitu will open. This means that e. g. commit messages will be opened in theGIT_EDITORby Git, but if the user wishes to do edits to the actual files in a different editor,VISUALorEDITORcan be set accordingly.Configuration is also loaded from:
~/.config/gitu/config.toml~/.config/gitu/config.toml%USERPROFILE%\AppData\Roaming\gitu\config.toml, refer to the default configuration.
Installing Gitu
Follow the install instructions: Installing Gitu
Or install from your package manager:
Shell completions can be generated with
gitu completion <shell>, see Shell completions.Contributing
While a part of me do with issues/PRs could be closed a lot sooner to respect the work of contributors, I’ve also coded/tested/reviewed this myself on my spare time. And therefore it needs to stay interesting for myself and not become a chore. There are a few rough edges and missing features in Gitu, it’ll never become a full magit-clone. While I’m not against opening up pull-requests, I just wanted to be clear on the expectations. You are always free to fork/extend this project to your heart’s desire.