So it is possible to change this behavior? I mean, is it possible to configure git so that it always pipes output to less (no matter the output is long or short), and leave nothing in the tty after less is quit? Thanks. For instance, if we run git log -oneline, if the log is short less won't even be called if the log is longer than one screen, then we would be temporarily directed to the output screen of less as usual: 0000000 set the pager of git to lessĪnd after pressing q, the whole thing gets written to the tty, so we end up with something like $git log -oneline # OMG!!! The output of less is always written to the tty after quitting. However, this is not the case if less is called by git (the pager of git is set to less -r in my case). Starting from 1.0.73 Fork includes an Internet Access Policy document that allows Little Snitch users to. For instance, if we run less README, we would be temporarily directed to a screen with things like SO rocks.Īnd after pressing q, the output of less would disappear, and we end up with something like $less README Images tracked using Git Large File Storage. >which meld /usr/local/bin/meld I have diff.tool and merge.tool set in gits config. In OS X terminal, when less is called on its own or by other programs like man, its output won't be written to the tty after we quit less. I have meld installed with brew on macOS (Catalina). Per mzabaluev's comment: The OS X terminal has some magic integration with less which breaks when less is run as a subprocess by git: when run as git diff less, scrolling forward is possible with the touchpad gesture, but with the output of git diff it only scrolls the terminal output and cannot tell less to scroll forward.
0 kommentar(er)
