There are a number of OpenSSL-related file extensions (e.g., .pem, .crt,
etc..) that contain data that are generally best not committed to
repositories. This file contains several common file extensions that
often correlate to these types of files.
* Update Autotools.gitignore
Add ignore-rule for Makefiles generated by configure
(directly by config.status)
* Add some descriptive comment.
Add more descriptive comment to explain why Makefile should be ignore.
If you have the [Ionide](http://ionide.io/) tools installed you will get an `.ionide` directory created in each directory that you open with VS Code, regardless of whether or not you are using F#.
The xy package generates *.xyd files whenever the commands
\MakeOutlines
\OnlyOutlines
\ShowOutlines
\NoOutlines
are present in the LaTeX source. These automatically-generated files
contain the dimensions of figures typeset with xy and are recreated as
needed. This is documented on pp. 15f. of the XY-pic Reference Manual
(1999/02/16).
As automatically-generated, temporary files, they should be ignored.
from vim's documentation on `:mksession` (:help :mksession):
...
10. If a file exists with the same name as the Session file, but ending
in "x.vim" (for eXtra), executes that as well. You can use *x.vim
files to specify additional settings and actions associated with a
given Session, such as creating menu items in the GUI version.
we already have Session.vim ignored. the Sessionx.vim file, like
Session.vim, is a user file. a user would generally want that file kept
private or for themselves, and the public or a team fetching from or
sharing the repository generally have no interest in a file relevant
only to a particular user. so it's a good idea to get git to help us
avoid mistakenly sharing the file.
When IntelliJ project is created as a file-based (i.e. without `.idea` folder, but with `.iws`, `.iml` and `.ipr` files), and this is a Gradle or Maven project with auto-import, should ignore them as well for the same reason we ignore `.idea` folder content in that case.
When a Unity project is opened in Jetbrains Rider, it installs a editor plugin into the Assets/Plugins/Editor/Jetbrains folder to manage Unity->Rider integration. This plugins life cycle is managed by your local Rider install and is automatically updated by Rider. It should not be committed to source control. This is documented by Jetbrains here https://www.jetbrains.com/help/rider/Unity.html
This change should ignore both the Jetbrains plugin folder and its .meta file correctly. For completeness, it would be nice to also ignore the /.idea*/ settings folder that Rider autogenerates, but i see a PR implementing that change has already been rejected.
