-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ormolu backend for haskell-mode is broken #312
Comments
Fair enough. If the maintainer of the original formatter recommends switching, then it seems logical for us to switch as well, to encourage best practices as determined by each language's community. Let me see if I can add a test case that will prevent a regression like this, too... I've done some work on more robust formatter tests that can leverage an entire project directory. |
raxod502
added a commit
that referenced
this issue
Sep 22, 2024
raxod502
added a commit
that referenced
this issue
Sep 22, 2024
Closes #312. The installation script was failing due to some Cabal bullshit that I don't even want to know the reason for, probably triggered by new package versions coming available, so I switched to upstream binaries. Applied the suggested fix from #312 for a new command-line option which has become required. Also set Ormolu as the default Haskell formatter instead of Brittany because that is what the Brittany dev recommends (see again #312).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
Because the default brittany for haskell-mode is unmaintained, and the repos recommand to use ormolu instead.
But the
ormolu
(version: ormolu 0.7.7.0) don't works with cabal project, will get below error message in *aphelia-ormolu-log* buffer:my configs:
with below config, will fix the issue.
Expected this can be fixed in apheleia.
Maybe it is time to change the default backend for haskell-mode to ormolu instead of brittany?
The text was updated successfully, but these errors were encountered: