-
Notifications
You must be signed in to change notification settings - Fork 83
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
bean-format
fails to format a beancount file
#309
Comments
John-Goff
added a commit
to John-Goff/apheleia
that referenced
this issue
Jul 14, 2024
John-Goff
added a commit
to John-Goff/apheleia
that referenced
this issue
Jul 14, 2024
Seems more likely to me that this has either always been broken, or the older version of beancount that was current when this formatter was added used to allow reading from stdin. But I have not investigated. |
raxod502
added a commit
that referenced
this issue
Oct 5, 2024
Fixes #309 The `bean-format` tool reads a file from the filename passed on the command line, then outputs the formatted file to `STDOUT`. The filename passed on the command line is a requirement, the `bean-format` tool does not read from `STDIN` at all. Another option would be to use `("bean-format" input "-o" output)`, but this way apheleia can avoid an extra file read that's not strictly necessary. --------- Co-authored-by: Radon Rosborough <radon@intuitiveexplanations.com>
Yeah you're right, I learned since opening this PR that beancount released a new major version at some point before when I noticed this. Either way, thanks for merging that fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given the file
in.beancount
found here: https://github.com/radian-software/apheleia/blob/main/test/formatters/samplecode/bean-format/in.beancountapheleia-format-buffer
and other formatting commands fail, with the following contents in the*apheleia-bean-format-log*
bufferSeems as though this has been broken for over 2 years, as the most recent change to that formatter was this one: #110. I have been using apheleia through Doom Emacs, which must have updated the pinned version of apheleia recently which is why I didn't notice this sooner.
The text was updated successfully, but these errors were encountered: