Closed volkipp closed 9 years ago
I did a little troubleshooting, and it appears that the "File has changed on disk" errors start happening after commit (the last one that allows me to edit my files and does not create a bunch of tmp files): 4dc17400a5f7a41baf00cce6501ab30f838475fe added @ syntax for cwd@hxml
The last commit that had the build system working properly was: fe393e134828b70405c8d92ceb77d27042bd44d9 -fix a bug where completion fails when one of the -cp doesn't exists
It should be fixed by latest commit; Thanks a lot for your fast report.
Please either confirm it is fixed, or let me know if you can see anything in the ST console (regarding tmp files, etc)
Thanks for the quick response! I'll let you know if anything comes up.
Any news ?
So I am having this issue still.
The current commit (58cad4780c3ce19a5219dfa38d25556f800ac726) dos not autocomplete nor build.
The commit linked by volkipp (fe393e134828b70405c8d92ceb77d27042bd44d9) does fix autocomplete for me but does not build.
I'm new to ST so I am not sure what other information would be useful for you.
Fixed 'Invalid build' message. It seems autocomplete and build are working fine. If there is some other issue with flambe feel free to open a new issue.
It looks like Flambe projects aren't working anymore with changes as of Aug. 19th. I'm on OSX, and when I try to select a build target with Control-Shift-Return, I get two items that say Invalid Build flambe.yaml Invalid Build flambe.yaml
If I hit escape or select one, it gives me the standard build targets for Flambe again. As another odd bug, I cannot edit my files in the project without a popup dialog saying that my file has changed on disk after about every keystroke. It looks like there are tmp files that are sticking around for every file that is edited.