New answers tagged color-management
If there's no way to do it within git itself, you could pipe the output into colordiff. colordiff can be used in place of diff to diff and colourise files and dirs, or you can pipe the output of diff into it and it will colourise it. e.g. git diff --name-status BRANCH_NAME | colordiff colordiff is available pre-packaged for most linux distros.
I dont know of any official way to do it, but I wrote this just now and it works for me. Put the bash script below into a file called: color_git_diff.sh (or whatever you want) #!/usr/bin/env bash for i in "$@" do if grep -q "^M" <<< "$i" then echo -e "\e[33m $i \e[0m" elif grep -q "^D" <<< "$i" then echo ...
Try next command: vimdiff [file1] [file2]
At the current stage of Linux development, there is no distribution/DE that is capable of delivering ClearType-like font rendering where the pixels are forced to stay in the grid. Think of it as a "mono-type-on-pixel-level" thing, where Microsoft's implementation (ClearType) allows better readability for smaller fonts. Apple's and Linux way of rendering ...
In my experience, using first a 1920x1200 and (after an upgrade) a 2560x1440 monitor connected via a KVM switch to both Linux and a Windows 7 desktop machine, the Windows fonts are ghastly - fuzzy, blurry, and difficult to read. The Linux fonts are crisp, clear, and beautiful to read. At any resolution. 1920x1200 on Windows was OK-ish but 2560x1440 is ...
Top 50 recent answers are included