Hi Elijah, On Mon, 10 Jan 2022, Elijah Newren wrote: > On Mon, Jan 10, 2022 at 11:22 AM Jonathan Tan <jonathantanmy@xxxxxxxxxx> wrote: > > > > Elijah Newren <newren@xxxxxxxxx> writes: > > > > > Scalar also has a mechanism for providing potentially large blocks > > > of pre-vetted configuration for users. It does so as part of a new > > > top-level command. And it does so with a very opinionated set of > > > values that are not configurable. Thus, while I'd like to use it, > > > they use a configuration option that would break things badly at my > > > $DAYJOB. (Too many gradle plugins using jgit, which doesn't > > > understand index.version=4 and will blow up with a very suboptimal > > > error message when they see it.) And, it's very specific to scalar; > > > we probably don't want to add a new toplevel command everytime > > > someone wants common configuration to be easily grabbed by some > > > user. > > > > Do you have more information on this? The closest thing I've seen is > > "Scalar Config" under "Modifying Configuration Values" in [1], which > > seems to be more about bundling additional tools (which may change > > config, of course). > > > > Unless you're referring to the config bundled in the Scalar tool itself, > > in which case this patch set seems orthogonal and potentially > > complementary - I was envisioning config being provided by a package > > manager package, but Scalar could provide some too for users to use at > > their own discretion. > > > > [1] https://github.com/microsoft/git/blob/7a514b4c2d5df7fdd2f66f048010d8ddcb412d0b/contrib/scalar/docs/troubleshooting.md > > Yes, I was referring to the config hardcoded in the Scalar tool itself > (see set_recommended_config() in > https://lore.kernel.org/git/4439ab4de0bc3f48a6bdcf4b5165b16fad792ebd.1638538470.git.gitgitgadget@xxxxxxxxx/). I was kind of thinking that such problems might be solved via introducing e.g. `scalar.ensureJGitCompatibility = true` (which should be a relatively trivial patch to write). What do you think? Ciao, Dscho
