Oliver Ford

(With none in config) ``` $git show 5c4da1c | ./diff-so-fancy | third_party/ansi-reveal/ansi-reveal.pl [...] [RESET][COLOR011]──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[RESET] [COLOR011]modified: lib/DiffHighlight.pm [COLOR011]──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────[RESET] [BOLD][COLOR013]@ lib/DiffHighlight.pm:15 @[BOLD][BOLD][COLOR146] my $NULL = File::Spec->devnull();[RESET] # Highlight by reversing foreground and...

Wouldn't the handling be the same [as for rename](https://github.com/so-fancy/diff-so-fancy/blob/0e792f9356ad7743dbba8a45529b7a77031eb7f2/diff-so-fancy#L287-L318), it looks the same just s/rename/copy/g? ``` $ git mv diff-so-fancy dsf $ git --no-pager diff --staged diff --git diff-so-fancy dsf...

Intra-line highlighting is handled by [`diff-highlight`](https://github.com/git/git/tree/master/contrib/diff-highlight), which is distributed with `git`, so the appropriate place to discuss it would be the mailing list - but I'd suggest you probably won't...

You can configure `diff-highlight` (be sure it's on your `$PATH` - it's usually distributed with `git` - and there are examples for configuring the colours in the readme) so that...

Duplicate of #1986

Depends on use case I suppose, if you're using it as a client(s) - server VPN for privacy or whatever wg-quick is probably great. For networking many servers though you...

This also false-positives on: ``` ``` With bootstrap-vue `b-table`s, where it's not easy to workaround other than ignoring the lint, because `foo.bar` and `foo.baz` might _both_ be keys in the...

Ah, this is because `versions` defaults to `1.1 2`, which causes the HTTP2 transport to be configured (cf. 97d918df3e89a3cc4dd5e5c06967bb85870c5ce3). Probably the request should be inspected for HTTP/2-incompatible features such as...

My solution is to create a matcher: ```caddy @http2notallowable { header_regexp Upgrade .+ header_regexp !Content-Transfer-Encoding (?:chunked|) header_regexp !Connection (?i:close|keep-alive|) } ``` (EDIT: Or not! Seems negated header matchers can't be...

@francislavoie The only acceptable value is the empty string. But this is no good for proxying HTTP/1.x requests that _do_ want to upgrade! Only solution for those is not to...