From: Thomas Koutcher <thomas.koutcher@online.fr>
To: git@vger.kernel.org
Subject: [ANNOUNCE] tig-2.5.8
Date: Sun, 5 Feb 2023 19:38:24 +0100 [thread overview]
Message-ID: <119fc2c6-510c-84e0-3dad-52a37b2966d6@online.fr> (raw)
Hi,
I am pleased to announce Tig version 2.5.8 which brings some improvements
and bugfixes. See the release notes below for a detailed list of changes.
What is Tig?
------------
Tig is an ncurses-based text-mode interface for git. It functions mainly
as a Git repository browser, but can also assist in staging changes for
commit at chunk level and act as a pager for output from various Git
commands.
- Homepage:https://jonas.github.io/tig/
- Manual:https://jonas.github.io/tig/doc/manual.html
- Tarballs:https://github.com/jonas/tig/releases
- Gitter:https://gitter.im/jonas/tig
- Q&A:https://stackoverflow.com/questions/tagged/tig
Release notes
-------------
Improvements:
- Update utf8proc to v2.8.0, supporting Unicode 15.
- Support editing from the pager and the log (-p) views. (#1243)
- Adjust build for native Apple Silicon.
- Autoscroll the pager view while loading. (#1223)
- Automatically show next diff in the status view. (#413, #469)
- Replace `Unknown` author with `Not Committed Yet`.
- Allow use of regular expressions for coloring. (#1249)
- Add support for option word-diff-regex. (#1252)
- Include original blob name in temporary filename. (#1254)
Bug fixes:
- Use %(file_old) for old filename in the blame view. (#1226)
- Correctly report which version of libncurses was linked. (#1240, #1241)
- Fix stage view closing when holding the ] key. (#1245)
- Make tests work from a path with symlinks.
- Fix encoding of very long lines. (#1227)
- Fix diffstat color for tig log -p.
- Clean IO before closing a view or quitting.
Thanks to everyone who contributed (in alphabetical order): Alex Daily,
alice, Mahmoud Al-Qudsi, Sebastian Gniazdowski, Thomas Koutcher.
--
Thomas Koutcher
reply other threads:[~2023-02-05 18:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=119fc2c6-510c-84e0-3dad-52a37b2966d6@online.fr \
--to=thomas.koutcher@online.fr \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).