Configuring Project and IDE Settings
Project settings refer to a set of preferences related to resources, file colors, version control options, code styles, etc. Project settings are stored with each specific project as a set of
xml files under the
You can configure project settings on the two possible levels:
The level of a template project. The settings defined for a template project, apply to any project you create.
The project level. Settings defined on this level apply to the current project only.
Project-level settings and structure
The project level settings and structure are applied to the current project only. These settings are stored together with other project files in the .idea directory.
If your project is under a version control, it is recommended that you store XML files with project-specific settings (the .idea folder inside the project folder) under version control, the exception being workspace.xml and tasks.xml, which store user-specific settings.
You can refer to this JetBrains.gitignore on GitHub to see what should be ignored.
Access the project-level settings
Selectfor Windows and Linux, or for macOS.
Alternatively, press Ctrl+Alt+S, or use the icon on the toolbar.
IDE-level (global) settings and structure
The IDE level (global) settings and structure are applied to the current project and to all new projects that you create afterwards. The list of IDE-level settings contains less options, but it enables you to change the editor settings, create custom scopes, configure inspections, set VCS-specific settings, and so on.
Access the IDE-level settings
From the main menu, selectfor Windows and Linux, or for macOS.
Restore the default settings
To restore the GoLand default settings, you can remove the configuration directory (idea.config.path) when the IDE is not running. The directory is located in:
Note that the Library folder may be hidden in the Finder.
For more information, refer to Directories used by the IDE to store settings, caches, plugins and logs.
Monitor the IDE performance
In case of performance issues, you can use Activity Monitor to track the percentage of CPU consumed by various subsystems and plugins.
From the main menu, select. It lists all subsystems and plugins that are consuming CPU at the moment, and arranges them by how much %CPU they are using.