Watchr: Docpad watching doesn't really work #477

Closed
adiospace opened this Issue Apr 7, 2013 · 16 comments

Comments

Projects
None yet
3 participants
Contributor

adiospace commented Apr 7, 2013

node 0.10.3
npm 1.2.17
docpad 6.30.2
osx 10.8.3

Let's say I have a layout and an index file that uses the layout. When I run "docpad run" all the files are generated. When I modify the index file, the changes are picked up, but if I modify the file again, nothing is generated anymore.

For some reason, only the first modification to a file is picked up.

Owner

balupton commented Apr 7, 2013

Hrmmm, a few people have been reporting this, or similar issues. I've made a label for all watching related issues.

Can you try the suggestion here and let me know if it works - bevry#427 (comment)

Contributor

adiospace commented Apr 7, 2013

Yes, it works. Thanks.

Contributor

adiospace commented Apr 7, 2013

As a side note, the livereload plugin was also affected by the same issue...

Owner

balupton commented Apr 7, 2013

Thanks for that. Yeah it is a pain of an issue. Is there a time when I can remote into your machine and debug? As the proper fix is autodetection of the correct method to use.

Contributor

adiospace commented Apr 8, 2013

I guess we can this week, say, around 16:00 Sydney time.

Owner

balupton commented Apr 9, 2013

Lets do Wednesday or Thursday 16:00 Sydney Time, let me know which day :) My skype username is balupton

Contributor

adiospace commented Apr 9, 2013

Wednesday. 16. Mine's agolaru

FWIW, I've been having the same issue for a few weeks and the preferredMethods seems to have fixed it. The only issue now is that watching doesn't pick up changes for 2-3 seconds, which makes using the live-reload plugin somewhat pointless. I have an identical dev setup to @adrianolaru.

balupton referenced this issue in bevry/watchr Apr 10, 2013

Closed

Make it handle how vim saves files #38

Owner

balupton commented Apr 10, 2013

Please reinstall docpad and give this a go :)

Contributor

adiospace commented Apr 10, 2013

I've done that... still testing...but...

when I edit with vim and use docpad run

  • if set noswapfile: fix doesn't work
  • if noswapfile is not set (default): I get 2 generator logs:
    Generated 0 files...
    Generated 3 files...
    everytime i make a change...
Contributor

adiospace commented Apr 10, 2013

I'm running docpad without any watchOptions in docpad.coffee... sublime text 3 is working just fine now...

Owner

balupton commented Apr 10, 2013

K. Is it possible for me to remote in again?

Owner

balupton commented Apr 10, 2013

Ok, reinstall docpad again, and test it out - the watchr version installed with docpad should be v2.4.3 now

Owner

balupton commented Apr 10, 2013

This also seems to be the config option causing the problem in Sublime Text 3:

    // Save via writing to an alternate file, and then renaming it over the
    // original file.
    "atomic_save": true,
Contributor

adiospace commented Apr 10, 2013

we can do it again tomorrow...if there's still the need...

Owner

balupton commented Apr 11, 2013

Yep, lets do it again. Keen to get this sorted. Also lets continue this discussion on the associated watchr issue instead: bevry/watchr#33

balupton closed this Apr 11, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment