If it cannot find a configuration file in any of the per-user locations, it will use the version from the same directory as the executable. If none of the other configuration file directories are active, then the standard configuration file directory is %AppData%\Notepad++\.
#Xml notepad portable
If doLocalConf.xml is present, the portable configuration file location will take priority over the %AppData%\Notepad++\ directory. If the Cloud directory setting is defined and enabled, that will take priority over the portable or standard configuration file directory. Search order: If the -settingsDir option is set, that configuration file directory will take priority over any other configuration file directory.
There is a command-line option -settingsDir which will set a new directory for the per-user configuration file location (added in v7.9.2). If you enable the Cloud settings, some per-user configuration files will go in the defined directory (including contextMenu.xml, shortcuts.xml, userDefineLang.xml, langs.xml, stylers.xml, and config.xml the userDefineLang\ subfolder can be placed there as well, though it won’t be created by default when the Cloud settings folder is first populated). The ? menu’s Debug Info will show Local mode: ON for a portable version.) (An installation is treated as “portable” if the zero-byte doLocalConf.xml file is present alongside the notepad++.exe executable. In a portable installation, the configuration files all go in the same directory as the notepad++.exe executable (or the appropriate subdirectory), and there is no per-user configuration location. 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)
