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

Watcher compiling same file twice #189

Closed
Nexus6 opened this issue Oct 7, 2016 · 8 comments
Closed

Watcher compiling same file twice #189

Nexus6 opened this issue Oct 7, 2016 · 8 comments

Comments

@Nexus6
Copy link

Nexus6 commented Oct 7, 2016

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]

@evhub evhub added the bug label Oct 7, 2016
@evhub
Copy link
Owner

evhub commented Oct 7, 2016

@Nexus6 Definitely seems like a bug. I'll look into it and figure out what's going on.

@evhub evhub added this to the v1.2.1 milestone Oct 7, 2016
@Nexus6
Copy link
Author

Nexus6 commented Oct 8, 2016

I forgot to mention, here's my invocation of coconut where the problem is manifest:
coconut -w -t35 -f -s .

evhub added a commit that referenced this issue Oct 17, 2016
@evhub
Copy link
Owner

evhub commented Oct 17, 2016

@Nexus6 Fixed in coconut-develop! Run pip install coconut-develop to get the new behaviour.

@Nexus6
Copy link
Author

Nexus6 commented Oct 19, 2016

Got it. Tested and the fix is working. Thanks!

@evhub evhub mentioned this issue Feb 14, 2017
@evhub
Copy link
Owner

evhub commented Feb 22, 2017

Reopening--it looks like this is now happening again.

@evhub evhub reopened this Feb 22, 2017
@evhub evhub modified the milestones: v1.2.3, v1.2.1 Feb 22, 2017
evhub added a commit that referenced this issue May 3, 2017
@evhub
Copy link
Owner

evhub commented May 3, 2017

This should now been fixed again.

@Nexus6
Copy link
Author

Nexus6 commented May 3, 2017

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.

@evhub
Copy link
Owner

evhub commented May 4, 2017

@Nexus6 Yep, that's right--good to hear it's fixed!

@evhub evhub mentioned this issue May 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants