Open Atom's Settings View with Cmd+, Ctrl+, the Atom > Preferences File > Preferences Edit > Preferences menu option, or the "Settings View: Open" command from the Command Palette.Ĭheck Atom's settings in the Settings View, there's a description of most configuration options in the Basic Customization section. In some cases, unexpected behavior might be caused by settings in Atom or in one of the packages. If you see this indicator, click it and follow the instructions. Atom detects this and through the incompatible-packages package displays an indicator in the status bar when this happens.
#Atom rpg save editor upgrade
If you have packages installed that use native Node modules, when you upgrade to a new version of Atom, they might need to be rebuilt. Tip: You can also use apm unlink -all to easily unlink all packages and themes. In these cases, you may want to clear the state that Atom has saved. In some cases the state that gets saved can be something undesirable that prevents Atom from working properly. Clearing Saved StateĪtom saves a number of things about your environment when you exit in order to restore Atom to the same configuration when you next launch the program.
#Atom rpg save editor how to
The Atom FAQ has information on how to contact the maintainers of any Atom community package or theme. We strongly recommend creating an issue on the package's GitHub repository. When you find the problematic package, you can disable or uninstall the package. Restart Atom or reload Atom with Alt+Cmd+Ctrl+L Ctrl+Shift+F5 after you disable each package to make sure it's completely gone. Since the Settings View allows you to disable each installed package, you can disable packages one by one until you can no longer reproduce the issue. Start Atom normally again and open the Settings View with Cmd+, Ctrl+. If removing or commenting out all content from the init script and starting Atom normally still produces the error, then try figuring out which package is causing trouble. If you can no longer reproduce the problem in safe mode, it's likely it was caused by one of the packages or the init script. This starts Atom, but does not load packages from ~/.atom/packages or ~/.atom/dev/packages and disables loading of your init script.
To determine if that is happening, start Atom from the terminal in safe mode: atom -safe In some cases, these packages and the code in the init script might be causing unexpected behavior, problems, or performance issues. Atom will also execute the code in your init script on startup. Using Safe ModeĪ large part of Atom's functionality comes from packages you can install. If you're building Atom from source, pull down the latest version of master and re-build.
#Atom rpg save editor update
To update to the latest version, you can download it from the atom.io website or the latest release on GitHub and follow the Installation instructions for Atom on Linux.
0 kommentar(er)
