You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…the code style XMl configuration file stored in the codestyles folder.
…the inspections XMl configuration file stored in the inspections folder.
…the keymaps XMl configuration files for Linux and macOS stored in the keymaps folder. See the keymap reference for a visual presentation of the default mappings.
…the preferences XMl configuration files stored in the options folder. This includes the following settings:
code.style.schemes.xml - settings of the currently used code style.
colors.scheme.xml - settings of the currently used color scheme.
customization.xml and project.default.xml - settings of the customized menus and toolbars.
editor.codeinsight.xml - settings of various automatic code transformations.
keymap.xml - the currently used keymap.
laf.xml and ui.lnf.yml - settings of the currently used UI theme.
all other customized preferences defined in the various categories: editor.xml, ide.general.xml and options.xml
…the list of disabled plugins stored in the disabled_plugins.txt file.
snowsaw core plugin configuration
NOTE: JetBrains uses a naming scheme for the folder all user configurations are stored in based on the product major/minor version! This requires this snowblock to be updated as soon as the product gets updated to adapt to the new version string.
clean
The target paths (based on the host OS) with the naming scheme <PRODUCT><VERSION> should be cleaned before the link core plugin execution.
NOTE: Due to the JetBrains naming scheme for the target path (more details described above) the previous targets should be kept to ensure they are cleaned up by this plugin after updating to a new product version.
link
The target paths (based on the host OS) with the naming scheme <PRODUCT><VERSION> should be created by snowsaw if they doesn't exist yet.
NOTE: Due to the JetBrains naming scheme for the target path (more details described above) must be updated after updating to a new product version.
The text was updated successfully, but these errors were encountered:
This new snowblock should include all important configurations for all used JetBrains IDEs and products which are currently IntelliJ (Ultimate Edition), PyCharm (Community Edition), Webstorm and GoLand. For details about the paths see the documentation about directories used by the IDE to store settings, caches, plugins and logs.
It should include…
codestyles
folder.inspections
folder.keymaps
folder. See the keymap reference for a visual presentation of the default mappings.options
folder. This includes the following settings:code.style.schemes.xml
- settings of the currently used code style.colors.scheme.xml
- settings of the currently used color scheme.customization.xml
andproject.default.xml
- settings of the customized menus and toolbars.editor.codeinsight.xml
- settings of various automatic code transformations.keymap.xml
- the currently used keymap.laf.xml
andui.lnf.yml
- settings of the currently used UI theme.editor.xml
,ide.general.xml
andoptions.xml
disabled_plugins.txt
file.snowsaw core plugin configuration
NOTE: JetBrains uses a naming scheme for the folder all user configurations are stored in based on the product major/minor version! This requires this snowblock to be updated as soon as the product gets updated to adapt to the new version string.
clean
The target paths (based on the host OS) with the naming scheme
<PRODUCT><VERSION>
should be cleaned before thelink
core plugin execution.NOTE: Due to the JetBrains naming scheme for the target path (more details described above) the previous targets should be kept to ensure they are cleaned up by this plugin after updating to a new product version.
link
The target paths (based on the host OS) with the naming scheme
<PRODUCT><VERSION>
should be created by snowsaw if they doesn't exist yet.NOTE: Due to the JetBrains naming scheme for the target path (more details described above) must be updated after updating to a new product version.
The text was updated successfully, but these errors were encountered: