Adrian Ho

Yeah, I'm actually thinking that the current behavior is a _bug_, and bugs need fixing. :grinning:

While I'm fixing this string coercion bug, it would be good to address the behavior of the other coercion options. Specifically, if `file` contains `12345`, it's clear now that `-s...

> @gromgit why would `-n a=@file` (with file containing `12345`) generate `{"a": 5}` and not `{"a": 12345}` seeing that `12345` is a valid number? I _was_ thinking that only having...

To summarize, current behavior is to include file as a string, regardless of coercion flags. And here's how I think it should work: 1. No coercion flags: Include file as...

Sorry, just realized I'm over-complicating things... > Currently, the only way to avoid this is to manually escape those characters with a `\`. But, if these values are coming from...

Homebrew banned and removed options in all core formulae **years** ago. Options _support_ in `brew`, however, remains intact, and third-party taps are free to include as many options in their...

> I can't judge if this is a good idea or not. My Ruby-fu is limited too, but I'm pretty sure that: * the whole point of migrations is that...

I'm not sure how #35874 managed to work. Perhaps macOS changed their MANPATH construction logic after that PR was committed, because the current `manpath` man page reads: > The `manpath`...

@Homebrew/maintainers, what was the rationale for using `libexec/gnu{bin,man}` instead of the conventional `libexec/{bin,man}` for, say, Homebrew-wrapped binaries?

> MacPorts instead used `libexec/gnubin/man/` (https://github.com/macports/macports-ports/blob/master/sysutils/coreutils/Portfile#L94). Yeah, that would trigger the current macOS man path logic, so that's a third option, that's probably the least disruptive of all: ~3. Move...