-
Notifications
You must be signed in to change notification settings - Fork 114
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
Error: Not available. codefmt doesn't have a default formatter for this buffer. #16
Comments
Can you post a link to your .vimrc? |
Did you remember to run :BundleUpdate? |
Also do you have clang-format installed? |
Ye, updated. |
No, http://clang.llvm.org/docs/ClangFormat.html Try typing |
If typing |
I am in process fixing the error message |
Though |
Installed successfully. But since I'm no good in VimL, couldn't figure out how to properly set up the Thanks, @fowles ! Guys, could you provide more detailed install/setup instructions in the README ? |
Glaive is the way to properly set up clang_format_executable. Did you get the impression from somewhere there was a better way? Just wondering if we need to do more to clarify that point. |
Hey, sorry for the late reply...
If you mean installation guide, then just make it clear in the readme, that:
And
( just humanize that, cz I'm kinda sleepy atm ) Also, everyone would be glad to see that clang-format is configurable globally and locally: Anyways, thanks for the replies and the plugin! |
K, #21 is adding friendly explanations for how each formatter works into vroom files. I probably want to sprinkle some quick pointers in the README and help files and point people to those vroom files for details. |
The announcement claims this plugin supports cpp & js natively.
so after installing with vundle ( as provided in the readme file )
when I try to
:FormatCode
on .cpp or .js files I get following error:Not available. codefmt doesn't have a default formatter for this buffer.
What I am missing? Should one use VAM or install any additional plugins? Thanks in advance.
The text was updated successfully, but these errors were encountered: