When Notepad++ is looking for shortcuts, stylers and themes, function list definitions, and user defined language definitions, it will try to read from the per-user directory if the right file isn’t found there, then it will check machine-wide configuration files. (For a refresher course on %AppData%, see the Community Forum FAQ’s %AppData% entry.) The machine-wide configuration files go in the executable directory (so usually c:\program files\notepad++\). In a standard installation, the per-user configuration files go in %AppData%\Notepad++\. So if you open up the configuration file after you have changed the preference but before you have exited Notepad++, you will not see that change reflected in the file yet. But this also means that, when you make a change using Notepad++ menus and dialogs (like changing a preference, or saving a macro), your change will not be written to the configuration file until Notepad++ exits. Please note that Notepad++ writes the configuration files when it exits, which is why the Editing Configuration Files section below says that Notepad++ may overwrite your changes. Adding keywords to a language, because the new language version isn’t matched yet.Editing previously-recorded macros, or crafting new macros manually.However, there are some special cases where it is worthwhile to edit the configuration files directly, including: Notepad++ offers a comprehensive user interface to review or change most of its settings. Configuration Files Details Configuration Files
0 kommentar(er)
