-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
Watcher compiling same file twice #189
Comments
@Nexus6 Definitely seems like a bug. I'll look into it and figure out what's going on. |
I forgot to mention, here's my invocation of coconut where the problem is manifest: |
@Nexus6 Fixed in |
Got it. Tested and the fix is working. Thanks! |
Reopening--it looks like this is now happening again. |
This should now been fixed again. |
After updating coconut-develop and friends I can't reproduce the problem. If 1.2.2-post_dev17 is the right version to be testing with then I guess the bug is fixed. |
@Nexus6 Yep, that's right--good to hear it's fixed! |
I'm using coconut -w while editing my .coco files in vim. Most of the time (but not always I think) the file is compiled twice. For instance, when I'm editing foo.coco and save it, I see
Coconut: Compiling foo.coco ...
Coconut: Compiled to foo.py .
Coconut: Compiling foo.coco ...
Coconut: Compiled to foo.py .
If I introduce a compile error, for example putting '/1' on a line, I see
Coconut: Compiling foo.coco ...
CoconutParseError: parsing failed (line 32)
/1
Coconut: Compiling foo.coco ...
CoconutParseError: parsing failed (line 32)
/1
Version/platform info:
$ coconut -v
Version 1.2.0 [Colonel] running on Python 3.5.2 (default, Sep 10 2016,
08:21:44) [GCC 5.4.0 20160609]
The text was updated successfully, but these errors were encountered: