Ville Skyttä

That one does not look at `VIRTUAL_ENV_PROMPT` at all, but the part following it seems the same indeed, and more succinctly implemented over there. I'll drop that one from here.

...except that I won't :) The implementation here falls back to the venv dir even if loading the pyvenv.cfg fails for some reason. For example, does it exist in all...

`LEFTHOOK_VERBOSE=true` in the environment could reveal something for someone to work on this, please note that part of the issue report template, too: https://github.com/evilmartians/lefthook/blob/736ac31d15af4b9c020efdcdb48c2c128c892e86/.github/ISSUE_TEMPLATE/bug_report.md?plain=1#L31-L36

I do use (well plan to use) lefthook in CI. Use case is: run exactly same things on developer systems and in CI. Same versions of everything, same config of...

Regarding the config option, I guess I could make do with that and set up different config files for CI and local dev, but that's IMO really an antipattern I'd...

Regarding CI usage, here's pre-commit's related docs: https://pre-commit.com/#usage-in-continuous-integration In my experience, this use case for pre-commit (and other hook managers) is not at all uncommon, there are _lots_ of repositories...

It is currently documented as "disable colored output", so I thought it'd apply to all colors, no matter the implementation detail whether that's marked up or part of an icon....

Basic dprint config file in the current directorly, like ```json { "json": { }, "excludes": [ "**/*-lock.json" ], "plugins": [ "https://plugins.dprint.dev/json-0.19.1.wasm" ] } ``` File named `foo.json.in` in the current...

Ah, I'm not a zsh user nor have I even checked, just followed what they said in their docs. I'll leave it up to you to make the call here...

Looks like this is half obsolete as of 6.0.1, reworked remainders in https://github.com/santhosh-tekuri/jsonschema/pull/177, closing here.