Johannes Altmanninger

> for example, es-MX should have only strings different from es and fallback to it That sounds nice. We've had a [discussion](https://github.com/fish-shell/fish-shell/pull/11967#issuecomment-3511474119) about computing a distance metric between specified language...

maybe `tig log -p -- path/to/file` ? That gives you diffs though. If you want blobs, maybe `for commit in $(git log --format=%h -- README.rst); do echo $commit:README.rst; done |...

> I don't have enough context from the diffs there's also the "-U99" diff flag for choosing the amount of context Sounds like an unusual use case, I usually get...

> That ticket - GUAC-734 - comes from the old Glyptodon Jira issue tracker I wonder if we can find it; just in case there was a particular reason this...

let me know if this patch works for you, I think it's an obvious fix. I guess we can add logging too but I'm not sure if that should block...

Ok, dropping `uname=` sounds fine to me, since I don't have a use case where I'd need to know whether the system is an arbitrary Unix. Both Python and NodeJS...

I haven't had time to look at this in detail but this might be a workaround that goes in the wrong direction. In general I'd either fix the stdlib rc...

yeah dash needs something like "trap ... EXIT HUP INT QUIT"

great work, can you share the file type magic number? Or the relevant line from `/proc/mounts`? Perhaps we can find a better approach. Does `df -l path/to/your/file` work? Their heuristic...

It seems we should do ```diff diff --git a/src/path.rs b/src/path.rs index 92ecefd1a..97a1b8ff8 100644 --- a/src/path.rs +++ b/src/path.rs @@ -660,7 +660,7 @@ fn path_remoteness(path: &wstr) -> DirRemoteness { => DirRemoteness::remote, _...