ruro

@bk2204 does the filter not know the path to the file that is being filtered? My idea was to skip processing `.gitattributes` inside the filter itself.

Understandable. In that case it might also be desirable to explain how to do "negative" filtering in `.gitattributes` in the documentation and in the error/warning message. Something along the lines...

Actually, now that I am thinking about it. Is there any reasons against just unconditionally adding something like ``` **/.git* filter= diff= merge= text ``` to the end of `.gitattributes`?

@tonistiigi I am not sure, that your assertion about how the `tty` mode currently works is true (at least it appears to work differently to me). For example, consider that...

Ah. After some experimenting with the current `--progress=tty` I now understand what you mean. The current tty output mode is indeed dependent on the tty size. For example, if there...

I am also interested in the "refresh with different colours" button. Another kind of related issue is that when hovering over a label, the corresponding line is highlighted. However, since...

@DavidBittner does your PKGBUILD work? I thought there were still some issues with coreutils, that broke the build. At least the `install.sh` script didn't work last time I checked. Also,...

This doesn't appear to be completely fixed. `pre-line` still collapses whitespace, so code blocks look broken: ```` Here is the code you asked for: ```python def foo(): # this line...

> You need to make sure you encrypt it such that both your user and system age identities can decrypt them. By "system identity" I assume you mean the ones...

@danwilliams the "New behaviour side-by-side" looks a bit weird (especially around line 15). I kind of understand why it is like that, but I wonder if it would be better...