paulaltin
paulaltin
It seems that macOS 13 changed from GNU diff to "Apple diff": macOS 12: ``` $ diff --version diff (GNU diffutils) 2.8.1 Copyright (C) 2002 Free Software Foundation, Inc. ```...
Similar issue: https://github.com/NixOS/nix/issues/7286
I've pushed a commit (56d503a098f619476d03d29bf67514e6023433ab) to work around this issue, so the "unrecognized option" error message won't be displayed on macOS any more. Colored diffs still don't work out of...
> I've pushed a commit ([56d503a](https://github.com/paulaltin/git-subline-merge/commit/56d503a098f619476d03d29bf67514e6023433ab)) to work around this issue, so the "unrecognized option" error message won't be displayed on macOS any more. The workaround was relying on process...
Thanks for posting this! I'm not familiar with magit myself; is the issue the weird characters appearing in the output, or the fact that magit-process buffer isn't interactive? The characters...
> Try it; you’ll never go back. Easier said than done, apparently! I'm not having any luck installing it on my machine, either through Homebrew or via the instructions on...
The issue of ANSI escape sequences in the output should be fixed by #10.
The issue of interactivity is a little trickier. The simplest thing to do would be to check whether `stdin` is connected to a terminal, and if it isn't then display...
@dabrahams: I've pushed a commit to the same branch as the fixes to #9 and #10, which attempts to detect whether the script can be run interactively. I've tested it...
Changes which attempt to auto-detect whether the script can run interactively have been merged to master, since they are strictly an improvement and did work in an emacs shell, but...