Vagrant grunt-contrib-watch watchers issue

gistfile1.txt

20:13 <kzar> (Why I need it at all is that nfs doesn't trigger
             things like grunt-contrib-watch very quickly so my
             code doesn't build on save quickly.)
20:13 <phinze> ah hey that's a problem i'm working on solving too
20:14 <phinze> i think the pending nfs_guest PR may help with this
               - reverses the share direction
20:14 <phinze> are you running emacs on the host or the guest
20:14 <kzar> phinze: OH cool, yea I'm super-happy with vagrant in
             every other way but the watch issue is killing me
20:14 <kzar> phinze: oh cool
20:14 <kzar> phinze: Well I'm running emacs on the host so I get
             the nice graphical one
20:15 <kzar> phinze: and I wanted to avoid using tramp really but
             it's worse not having grunt watch notice changes
20:15 <phinze> yeah one of my top prios is supporting a
               host-editing-env guest-execution-env model of
               development
20:15 <phinze> grunt watch can do polling i assume, but that's
               still like a multi-second delay
20:15 <phinze> at least that's what i've found from guard/listen
               which are the ruby equivalents
20:15 <kzar> phinze: Well I can't see any good options to help me
             with grunt-contrib-watch. It DOES notice my changes
             but really slowly
20:16 <phinze> yeah probably polls
20:16 <kzar> phinze: any idea how long that fix will take to come
             in?
20:16 <phinze> i'm hoping we can make it in for 1.4, but not really
               sure on timeline. i can tell you at least you've got
               one vagrant dev who is very invested in getting it
               solved :)
20:17 <kzar> cool
20:17 <kzar> But tell me if the files are on the host, how does
             reverse nfs mounting work?
20:17 <phinze> as a stopgap i've had folks switch to console emacs
               on the guest when doing really heavy work needing
               feedback loops
20:17 <kzar> phinze: this what you talking about
             https://github.com/mitchellh/vagrant/pull/2587 ?
20:17 <kzar> phinze: fuck that though, I'd be editing in a terminal
             window and mac hotkeys kill me
20:18 <kzar> as an emacs user
20:18 <kzar> I'd close the window instead of copying and stuff
20:18 <phinze> lol
20:20 <phinze> i'm a longtime console vim user, so i can empathize
               only in theory ;)
20:20 <kzar> phinze: oh man I want that nfs_guest feature so
             bad. So to be clear, it _would_ work if I'm sharing a
             directory on the host with the VM? 
20:20 <phinze> kzar: well i wouldn't get your hopes too high just
               yet - i've yet to vet it for this particular use
               case... i'm thinking it "might" help the inotify
               problem
20:21 <kzar> OK
20:21 <phinze> and we'd probably need some mechanism for the
               initial mirror of files into the share
20:21 <phinze> since as you say, we'd want to start with the files
               on the host
20:21 <phinze> but i guess my main point is that it's definitely a
               use case that i'm concerned about, so expect at
               least some movement on it
20:23 <kzar> phinze: thanks OK, well if I can help with it somehow
             my email is kzar@kzar.co.uk . I don't have masses of
             spare time and I'm not familiar with Vagrant codebase
             _but_ I have done some ruby before and I am a
             programmer by trade