fsevent_watch --latency 0.1 /Users/me/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activesupport-5.0.2/lib/active_support/localefsevent_watch --latency 0.1 /Users/me/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activemodel-5.0.2/lib/active_model/localefsevent_watch --latency 0.1 /Users/me/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/activerecord-5.0.2/lib/active_record/localefsevent_watch --latency 0.1 /Users/me/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actionview-5.0.2/lib/action_view/localefsevent_watch --latency 0.1 /Users/me/Temp/wat/config/localesfsevent_watch --latency 0.1 /Users/me/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/web-console-3.4.0/lib/web_console/localesfsevent_watch --latency 0.1 /Users/me/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/actioncable-5.0.2fsevent_watch --latency 0.1 /Users/me/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/coffee-rails-4.2.1fsevent_watch --latency 0.1 /Users/me/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/jquery-rails-4.2.2fsevent_watch --latency 0.1 /Users/me/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/turbolinks-5.0.1fsevent_watch --latency 0.1 /Users/me/Temp/wat/dbfsevent_watch --latency 0.1 /Users/me/Temp/wat/app/channelsfsevent_watch --latency 0.1 /Users/me/Temp/wat/app/controllersfsevent_watch --latency 0.1 /Users/me/Temp/wat/app/helpersfsevent_watch --latency 0.1 /Users/me/Temp/wat/app/jobsfsevent_watch --latency 0.1 /Users/me/Temp/wat/app/mailersfsevent_watch --latency 0.1 /Users/me/Temp/wat/app/modelsfsevent_watch --latency 0.1 /Users/me/Temp/wat/test/mailersfsevent_watch --latency 0.1 /Users/me/Temp/wat/app/assets
I suspect something is automatically adding anything from the I18n load path to the list of watchable directories without checking whether they are part of a gem or not.
> * Why can't we just watch the top level directory instead of watching the subdirectories too?
If you did that you would receive more notifications, for example the log folder, the tmp folder and so on (although I don't know what the tradeoff is between this vs monitoring a larger number of paths). You might also want to reload code outside of the application top level folder (such as a gem containing an engine that you are developing concurrently with the application)
Fred
If you did that you would receive more notifications, for example the log folder, the tmp folder and so on (although I don't know what the tradeoff is between this vs monitoring a larger number of paths). You might also want to reload code outside of the application top level folder (such as a gem containing an engine that you are developing concurrently with the application)