In addition to `.Spotlight-V100` and `.Trashes`, the following dotfiles
may appear at the root of all OSX volumes (not just external disks):

- `.DocumentRevisions-V100`: auto-save and versions storage
- `.fseventsd`: file system event storage
- `.Temporaryitems`: temp directory used by some applications instead of
                     /tmp and /var/tmp
- `.VolumeIcon.icns`: storage of custom icon for volume, if set

joomla 3.3.6

add .eggs/ directory to Python.gitignore

ignore /vendor/bundle on Ruby.gitignore

Correct URL for NPM URL reference

URL for commented reference has been updated

ignore new scratch directory for metadata

add *.vs/ to ignore VS files in VS15 CTP5

This directory is created by ExtUtils::MakeMaker starting with version
7.05_05, via this commit:
https://github.com/Perl-Toolchain-Gang/ExtUtils-MakeMaker/commit/b6a9eba5b0501dbe2fa0568a15dc588b1a289128

It was added to the default MANIFEST.SKIP in ExtUtils-Manifest 1.70, here:
https://github.com/Perl-Toolchain-Gang/ExtUtils-Manifest/commit/e0f44577f84521ded664a41b46021eae95a1a1af

As of Visual Studio 2015 CTP5 the Roslyn cache and suo files are stored in a .vs/ directory.

Revert "Ignore npm-debug.log"

Adding gitignore file for Synopsys VCS simulator.

Whether to use VCS or any other simulator is a choice of the individual designer rather than of the project as a whole.

Unity3D - Cache files, solution settings files and meta file update

User-specific files for MonoDevelop/Xamarin Studio.

Setup of the development environment.

Add Google App Engine generated folder

Base path to placeholder images

The .htaccess settings depend on the development environment, in some cases it is not used.

Base is media/catalog/product/placeholder/default/ and media/catalog/product/placeholder/my-theme/ new placeholder set on admin.

As Carl has pointed out, they are covered by other templates under Global/.

Typo in comment

I know this is petty, but imagine thousand upon thousand of corrective commits saved by fixing the typo right into the heart of the file.

Add Carthage build folder and explaination

Fixes #1217.

Once again ignore .classpath and .project in the Eclipse template. This has
been requested in multiple PRs such as #1338 and #1221 and is essentially a
reversion of #805. I copy the explanation for this change from the discussion
in #1217 by @segfly:

*In short*:

I can't point to any counter-documentation off the top of my head. I just know
from experience these files pollute a project's repo without adding value
- that is, unless everyone contributing is using Eclipse and no-one is using
dependency management. And even then, the guidance provided by the eclipse docs
is bad advice.

*In Long*:

The .classpath file is used by Eclipse to maintain the project's classpath
during automatic compile (every save of a file). In the olden days, one would
manually configure the project within the Eclipse UI and include all the
dependent jars necessary to compile your project. Eclipse then wrote that
configuration out to the .classpath file.

In theory, this file could be shared with others so they did not have to
manually configure their eclipse classpath. In practice, I never saw it work
out quite so well due to eventual bloating of the classpath with needless jars
or jars that only existed on one person's machine. Mind you, many people back
then also used to check their dependent jars into version control along with
their source.

Dependency management tools like Gradle and Maven have done away with all that
of course. But they also integrate nicely with Eclipse and manage the project
classpath dynamically. The .classpath file is basically rebuilt based on
changes to the build.gradle file or pom.xml file. Effectively, this renders the
whole point of checking in the .classpath moot as it is easily rebuilt by the
Maven or Gradle plugin.

The .project file is another animal completely. It basically describes what
plugins should be applied to the project as configured in the Eclipse UI. Again
the theory is it could be shared and creates a happy world. But due to
different eclipse versions people may have, different plugins installed, etc.
sharing the .project file actually causes more issues. And I've seen many
projects unable to open due to a bad .project file - requiring one to delete it
anyway (which then of course, when someone recreates it, they inevitably check
it in over the old one and end up breaking someone else's environment).

The bottom line is, regardless of what the eclipse documentation says, these
are very much internal configuration files for eclipse and best left out of
a repo.

Avoid ignoring Gradle wrapper jar file

Added missing gradle netbeans directory

Ignore the pip self check marker file in a Virtualenv.

Add .Trash-* to ignore Linux partition or ext disk trash folders

Update TeX.gitignore

*.synctex is generated when the synctex option is used under Windows.