I started by calling it a "blacklist", but changed it because it makes it sound like there's something wrong with the libraries listed in the file when it's actually a problem with Tern. What I have in mind, ultimately is:

1. exclusions that the user configures (because they don't want code hints for certain directories or files) – something like what is in .jscodehints today
2. this list of files that we know cause problems for code hints. The only reason it's a pref and the only reason someone would override the value is if they are using one of our excluded files but know for sure that it works okay in their environment (unlikely, but I wanted to leave it as a possibility)
3. files that we detected were causing problems for Tern (does not exist yet – might actually take the form of automatic additions to list 1 above)

So, I'm open to other names but just "exclusions" wouldn't cover the generally behind-the-scenes nature of this new pref.