Per @andyw8 in #588:
https://github.com/ggreer/the_silver_searcher/wiki/Advanced-Usage
`agignore` is now deprecated as the place to declare ignored files for
search. We'll put these files into `gitignore` rather than `ignore` so
that we have consistently ignored files between ag, git, etc.
Recommended by @croaky:
bcfa239b31Close#588
After using byebug on any Ruby file, the sessions history is written to
this file. It shouldn't be part of our repositories, so we ignore it.
See also: https://github.com/thoughtbot/suspenders/pull/710
The first time a `.py` file is run, or any time it's been modified, Python
creates a `.pyc` file containing a bytecode representation.
These bytecode files should always be ignored by Git, since keeping them
updated in a repo would be time consuming and would serve no purpose.
* Silver searcher or ag was filtering out any directory that had a
.DS_STORE file. Any directory that has a .DS_STORE file in it is being
ignored by ag and therefor does not show up in the ctrlp fuzzy finder
either.
* Removing the * from before .DS_STORE in the gitignore
file still prevents .DS_STORE files from being checked into source
control and stops ag from filtering out the directory. I am not sure
if this is a bug with silver_searcher or what
It is a common practice to store environment variables in a .env file in
development. This file is read by tools such as foreman and dotenv. This
file can contain sensitive information such as secret keys and should
always be excluded from version control
* sass gets compiled to `tmp/sass-cache` with Rails
* vendor/bundle_gems seems like an arbitrary vendor directory
* vim/.netrwhist is for a plugin we no longer use
