Mohsin Kaleem

@sigmavirus24 why? EDIT: Looking at the implementation in pycodestyle, the XDG compliance is isolated to these lines: https://github.com/PyCQA/pycodestyle/blob/c47f5c1f977c20f16c19bc282834c70c9b40d800/pycodestyle.py#L85-L94 I'm slightly curious why it doesn't fallback to the users home directory...

@sigmavirus24 > By default, pycodestyle and flake8 merge those as the lowest priority configuration items when running the tool (as it merges other configuration values). That is the scenario in...

@sigmavirus24 > For normal tools, that works great. Flake8 and pycodestyle have seen this cause big headaches for folks who have one thing configured locally and then their coworkers see...

@sigmavirus24 > So you're saying that users shouldn't be shooting themselves in the foot? That's not exactly compassionate or user-focused design. Lol :rofl:. I meant projects should be configured to...

I don't have evil-collection but I still get the `evil-magit is obsolete. This package is now part of evil-collection. Having both installed will cause unintended behavior.` message. Could you disable...

Interesting. Sadly I can't reproduce a backtrace with the instructions you've shared. @philipsd6 Could you do `M-x find-library apheliea` and `M-x eval-buffer` and produce and share the stack trace again?...

> Looks like you've got some neat customization variables as well for your formatter definitions, I see no reason we can't include those as a new abstraction into Apheleia. Great....

Makes sense. How's about we keep core definitions including formatters in `apheleia.el` and move the formatter runner to a separate `apheleia-runner.el`?

I've wanted this as well, but my desire for it is starting to wane. I'd recommend reading [black#134](https://github.com/psf/black/issues/134). It provides a pretty compelling reason IMO for why this isn't supported....

I'm in the same boat. Kinda disappointing the README directs you to a build script (which is failing for me, so I built using just dotnet) and I have no...