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

Unknown error message is too long #92

Open
MintPaw opened this issue Apr 2, 2016 · 3 comments
Open

Unknown error message is too long #92

MintPaw opened this issue Apr 2, 2016 · 3 comments

Comments

@MintPaw
Copy link

MintPaw commented Apr 2, 2016

I'm trying to set up Vaxe on a new machine, but I'm getting an error that's too long to read as a single line in Vim while pressing C-X C-O. Is there any way for me to properly read this error?

https://i.imgur.com/EnTAuBl.png

@jdonaldson
Copy link
Owner

You could just try and build your project. You'll get the error message in your quickfix window. Then, you can wrap that with :setwrap

@MintPaw
Copy link
Author

MintPaw commented Apr 3, 2016

Building the file with :make works fine, but completion still yields errors.
Is there no way to wrap that omni-complete box?

It also seems like the auto-generated project.xml.hxml is empty save for the comment. That's probably causing the problem, but without seeing the errors it's very hard to debug.

EDIT: If I manually populate the .hxml file by copying it from another project it seems to work. Although it's pretty picky about what exactly it what exactly it needs in there. The problem seems to have been having an invalid haxelib package installed. Although I have had other error in the omni-complete and it's almost always too long for me to read properly.

On Sun, Apr 3, 2016 at 11:14 AM, Justin Donaldson notifications@github.com
wrote:

You could just try and build your project. You'll get the error message in
your quickfix window. Then, you can wrap that with :setwrap


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#92 (comment)

@jdonaldson
Copy link
Owner

The empty project.xml.hxml is a bad sign. Try deleting that and starting vim again.

You also can try to turn on additional logging with :VaxeToggleLogging, and then checking the resulting messages with :mess. A new message will be generated (with the hxml actually used) whenever you trigger a completion. There me be an error, or you may something wrong with the generated hxml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants