Skip to content
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

Jump to bottom

Make compile file output make sense #157

Open
m0smith opened this issue Mar 11, 2015 · 2 comments
Open

Make compile file output make sense #157

m0smith opened this issue Mar 11, 2015 · 2 comments

Comments

@m0smith
Copy link
Owner

m0smith commented Mar 11, 2015

C-c C-v C-c - compile file, I think this is working but I'm not sure. The groovy menu seems to output a very long list of compiled deps when it succeeds, and an error when there is an obvious syntax error, although I am missing the easy to read Malabar compilation buffer to get results. Also flycheck seems to compile the file continuously, not sure why
@m0smith
Copy link
Owner Author

m0smith commented Mar 11, 2015

Flycheck and be enabled and disabled as needed. The point of flycheck is highlight errors on the fly. If you do not want that, go ahead and disable it.

@m0smith
Copy link
Owner Author

m0smith commented Mar 11, 2015

m0smith/malabar-mode-jar#31 was created to clean up the grooovy buffer output

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@m0smith