How do you limit CoffeeScript (or JavaScript) execution to a particular controller and action in Rails 3.1?

Question

The new Rails 3.1 asset pipeline is really nice, but since all CoffeeScript (or JavaScript) files get melded down into a single file that is included in every page, it raise

Answer 1

Why not to put the javascript for the particular controller as a view on this controller (as they correspond there if are so specific)?

If they are general enaugh you can mark your view with classes, ids or data (html5) and make your javascript look for that (so you can reuse your code).