rune/gitignore
1
0
Fork 0
Code Pull Requests Activity
485a600a77
gitignore/Global/SlickEdit.gitignore

13 lines
324 B
Plaintext
Raw Normal View History

Add Global/SlickEdit.gitignore file This commit adds a global ignore file for SlickEdit, a commercial editor. SlickEdit will create the following files when the user sets up a workspace: *.vpw Workspace file. Contains a list of project files associated with the workspace. *.vpj Project file. Contains the project’s settings, including the list of source files. *.vpwhist Workspace history file for Windows. Contains user session information (list of open files, debugger breakpoints, etc.) *.vpwhistu Workspace history file for UNIX/Linux/MacOSX. (Same as above.) *.vtg Workspace tag file. Contains a database of source code symbols. It is assumed that GitHub users will generally not want to store their workspace and project files in a repository, so those files are ignored globally. However, those files do not contain user-specific data so they could be stored in a repository and shared among developers if desired for a particular project. This can be done by adding rules like ’!*.vpw’ and ‘!*.vpj’ to the project’s .gitignore file. The workspace history and tag files contain user-specific data, so they should not be stored in a repository. For more information, download the PDF user guide from: http://www.slickedit.com/products/slickedit/product-documentation Note: The user guide is 1400 pages long and over 13MB in size. Searching for ‘vpwhist’ will lead to the section that discusses storing these files in a repository.
2014-03-19 00:21:03 +01:00
# SlickEdit workspace and project files are ignored by default because
# typically they are considered to be developer-specific and not part of a
Edit comment in Global/SlickEdit.gitignore Remove unnecessary wording about negative ignore rules.
2014-03-19 07:37:25 +01:00
# project.
Add Global/SlickEdit.gitignore file This commit adds a global ignore file for SlickEdit, a commercial editor. SlickEdit will create the following files when the user sets up a workspace: *.vpw Workspace file. Contains a list of project files associated with the workspace. *.vpj Project file. Contains the project’s settings, including the list of source files. *.vpwhist Workspace history file for Windows. Contains user session information (list of open files, debugger breakpoints, etc.) *.vpwhistu Workspace history file for UNIX/Linux/MacOSX. (Same as above.) *.vtg Workspace tag file. Contains a database of source code symbols. It is assumed that GitHub users will generally not want to store their workspace and project files in a repository, so those files are ignored globally. However, those files do not contain user-specific data so they could be stored in a repository and shared among developers if desired for a particular project. This can be done by adding rules like ’!*.vpw’ and ‘!*.vpj’ to the project’s .gitignore file. The workspace history and tag files contain user-specific data, so they should not be stored in a repository. For more information, download the PDF user guide from: http://www.slickedit.com/products/slickedit/product-documentation Note: The user guide is 1400 pages long and over 13MB in size. Searching for ‘vpwhist’ will lead to the section that discusses storing these files in a repository.
2014-03-19 00:21:03 +01:00
*.vpw
*.vpj
# SlickEdit workspace history and tag files always contain user-specific
# data so they should not be stored in a repository.
*.vpwhistu
*.vpwhist
*.vtg
Copy Permalink