-
Notifications
You must be signed in to change notification settings - Fork 453
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
Atom-beautify cannot detect installed Uncrustify #2526
Comments
I am having a similar issue with Ubuntu 18.04 and uncrustify installed from source. Uncrustify is on my |
I'm facing the same issue on Manjaro, installing with |
Same, Manjaro for me as well. I managed to install it with docker, and that version does run, but that gives another error:
|
Same for me ("Could not find 'Uncrustify'". setting the executable does not help). |
the error is on /atom-beautify/blob/master/src/beautifiers/uncrustify/index.coffee line 21 that can't read uncrustify version, so i can fix it on my pc by rewrite that line with |
If you still need this and are looking for something to fill the spot that Atom left, I am using Pulsar the successor to Atom... This package is working except for one deprecated error listed in #2605 If you don't need this anymore, can you please close this out so it's not just sitting there? Thanksv |
Okay I'll close this as I no longer require the beautifier. Personal advice, for those still using Atom-beautify and facing this issue better use external beautifier and copy paste the result into Atom to avoid headache. |
Description
Atom-beautify return error when I run Beautify on Java file. Running
which uncrustify
return absolute path/usr/bin/uncrustify
. Runninguncrustify
on terminal also return the command usage. Atom is v1.40, on Fedora 32.Input Before Beautification
NA
Expected Output
NA
Actual Output
NA
Steps to Reproduce
dnf install uncrustify
Beautify
Debug
Checklist
I have:
so I know this is not a duplicate issue
Atom Beautify: Help Debug Editor
command in Atom and added link fordebug.md
Gist to this issueThe text was updated successfully, but these errors were encountered: