git-split-diffs VS kitty

if i had to recommend 1 app/script that i use daily: https://github.com/banga/git-split-diffs

`karabiner elements` (https://karabiner-elements.pqrs.org/) to disable things like "Apple + Q" -> nothing worse than going to close a single tab and then your whole app quits. also able to re-map caps-lock into escape, ect

`iterm2` for terminal (colored tabs are great; albeit i disable the hell out of many of the options like "clickable urls" ect)

for cli, i try to gnu all-the-things (and i just explode my PATH to the paths `brew` installed dynamically - will try another package manager at a future date)

`sublime text`

`firefox`/`librewolf` + plugins (containers, netmon, request interceptor, dark reader, adnauseam)

This with the UI from https://github.com/banga/git-split-diffs would make the perfect CLI diff tool!

I wrote https://github.com/banga/git-split-diffs mainly to scratch an itch about not having side by side git diffs in the terminal, then ended up adding more fancy features like syntax highlighting and it got somewhat popular.

I actually tried to automate the screenshots for this project's readme using GitHub actions, but struggled to get it to produce the same quality screenshots as my local machine. This is the script I use for now, which has to be invoked manually: https://github.com/banga/git-split-diffs/blob/main/scripts/g...

Terminal: I use Kitty. I have tabs, splits, clipboard bindings, quick access terminal, and a few custom keybindings. It is fast, it works well on Wayland, and it does not get in my way.

I've been using Omarchy as my main setup since June 26, 2025, the day DHH released the first version. Before that I had my own custom Opinionated Linux, mclovin-ARCHived: an Arch + i3wm installer set up exactly the way I liked. It was total control over the OS: me deciding what goes in, keeping every piece (i3wm, polybar, picom, kitty, dotfiles) up to date and making sure they all talked to each other for the whole OS to keep working. It did the job, but it was costly to keep up to date: always digging into some new TUI to solve a small issue, and changing CPU or laptop meant checking compatibility for everything and tweaking for each machine.

I was wondering also. If it can help, there is an overview on Kitty's website : https://sw.kovidgoyal.net/kitty/

You're right my comment was off the cuff but I stand by it's logic. I didn't say Kovid was a terrible person, just not great. Having not done research into him specifically I just noted with the parent that certain qualities such as supposed abrasiveness often overlap with qualities I dislike, like using the Lenna image.

My point is that using the Lenna image is a signal, just as you rightly point out so is my comment. I know exactly what the image is and is used for. But I also think it's sad that it's politically charged to say using a Playboy image in a literally objectifying fashion as a test-subject by a women who's requested we don't use it is bad.

It's not a sudden ban, it's been an issue since ~2015. Fun fact I learnt in this, Goyal is totally open to changing it (https://github.com/kovidgoyal/kitty/issues/661), it's simply no-one changed it. I'll see if I can, thanks for the correct call-out.

It works on any terminal that supports the Kitty graphics protocol — Ghostty and Kitty are the two main ones.

Kitty has poor security

https://github.com/kovidgoyal/kitty/issues/2084

Claude Code comes with a notification hook. Some terminals support it natively (iTerm2, Kitty, Ghostty) but most don’t, and even when they do, it’s a system notification which is easy to miss if you step away.

Similarly kitty is at 0.44.0 [0], zutty at 0.16.0 [1]

0.https://github.com/kovidgoyal/kitty/releases/tag/v0.44.0

1. https://git.hq.sig7.se/zutty.git