Notepad++ Exe Location

[Gerald Weiß]

Bythe way, if you want to know how I found this out, I fired up Sysinternals ProcMon, set a filter on the ProcessName field to "notepad++.exe", closed Notepad++ and then ProcMon showed me which files had been accessed when I closed it.

I noticed it myself, and found the files inside the backup folder. You can check where it is using Menu:Settings -> Preferences -> Backup. Note : My NPP installation is portable, and on Windows, so YMMV.

I lost somehow my temporary notepad++ files, they weren't showing in tabs. So I did some search in appdata folder, and I found all my temporary files there. It seems that they are stored there for a long time.

Notepad++ offers a comprehensive user interface to review or change most of its settings. However, there are some special cases where it is worthwhile to edit the configuration files directly, including:

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. 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. 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. Do not be surprised by this.

There is a command-line option -settingsDir which will set a new directory for the per-user configuration file location. (Unlike the cloud directory, session.xml does work in the -settingsDir directory, so if you want to have all your per-user configuration, including your session information, in your cloud folder, it might be wise to not use the Cloud settings option, and instead point -settingsDir to the cloud folder.)

Search order: If the -settingsDir option is set, that configuration file directory will take priority over any other configuration file directory. If the Cloud directory setting is defined and enabled, that will take priority over the portable or standard configuration file directory. If doLocalConf.xml is present, the portable configuration file location will take priority over the %AppData%\Notepad++\ directory. If none of the other configuration file directories are active, then the standard configuration file directory is %AppData%\Notepad++\. 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.

ALWAYS BACKUP THE FILE TO BE EDITED. If you make a mistake, Notepad++ may erase the whole contents and replace it with useless defaults. This is probably the worst that can happen, but it does happen.

If changes are made in the Notepad++ UI to settings which are stored in configuration files, those will be written to disk when you exit Notepad++ after any file saves you do. Thus, if you are going to edit a Notepad++ configuration file with Notepad++ (and why would you want to edit it with anything else?), you will need to be careful. The safest sequence when editing a configuration file:

The context menu does not have a GUI-based editor; you just need to edit the file. As a result, the Settings > Edit Popup Context Menu entry exists to make it easy for you to access this config file.

Note that the menu names and menu item names (whether built-in or plugin names) that you use in the should be in English, not in a translated language. The Shortcut Mapper can help you find the English name of plugin commands; simply switch to English localization for the raw name of built-in commands; or you can look at the english.xml that shipped with your distribution.

Each will use the same text as the main menu entry uses, as defined by your current localization. This can be overridden by adding an ItemNameAs="new_name_for_the_item" attribute, so that the new name will be displayed instead of the standard one. This is useful when the name is lengthy, as it makes the Context Menu unwieldy otherwise. Non-Latin characters are supported.

All the types of commands in shortcuts.xml have a key attribute, which uses the Windows virtual key number as the value. This is not necessarily the same as the ASCII code or Unicode codepoint. In standard English locales, the virtual key usually lines up with the ASCII code for the character, but that is not universally true. The complete list of base virtual key code is to be found on keys.h. Because of this reliance on OS-defined virtual keys, many letters in your native alphabet cannot be used, though for characters that are entered directly with a key on your keyboard, it may be possible (with some effort) to determine the virtual key number for the key. (Some hints are given in the Notepad++ Community Forum at this post and this other post.)

When not empty, this node is made of nodes, each of which represents an individual macro. Each holds a non-empty list of tags which represent individual macro steps. These steps are either Scintilla commands or Notepad++ commands, not raw keystrokes. For more details on macro recording, see Macros.

The full list of Scintilla messages for type=0 and type=1 Scintilla messages, as well as a concise documentation, can be found in Scintilla.iface. More details on those messages can be found in the Scintilla Docs. You can use any Scintilla message that does not return a value, that passes an integer in wParam, and uses either an integer or string in lParam. There are some messages that require strings in the wParam, or various data structures in one or both parameters: those will not work in a macro. (For more on the messaging system, see Plugin Communication.)

If your automation task requires conditional execution, counters, variables, using the results of one action to influence the next, or other complex behavior, the macro system will not be sufficient for your needs: you will need a Plugin: there are scripting plugins available in Plugins Admin that allow automating Notepad++ with the full power of a variety of programming languages behind them, or you might find a pre-existing plugin that already accomplishes your automation task, or you could write your own plugin).

If you want access to a Windows environment variable (like TMP), use the standard %-notation for Windows variables (like %TMP%). If the variable references a path with one or more spaces in the name, then putting quotes around environment variables is required: for example, if %TMP% is defined as C:\Users\First Last\Temp\, then you will need to use C:\AppDir\blah.exe "%TMP%" as your command.

The order of the ext list here determines the order of extensions in the file-type pulldowns of the Windows-common-dialogs like Open, Save, and Save As dialogs. The automatically-added extension will be the first extension from this ext list.

This file sets the color scheme for the default theme. The other themes are stored in themes\*.xml, which follow the same format at stylers.xml. In general, use Settings > Style Configurator for easier maintenance of styles.

If you have added user-defined keywords in the Settings > Style Configurator, they will be stored as the contents of the , as a space-separated list (for example, fancyKeyword1 fancyKeyword2).

The colorStyle attribute decides whether to use the defined colors from fgColor and bgColor attributes, or to use the default color setting (from Settings > Style Configurator > Global Styles > Default Style). The attribute should be set to one of the following:

If 2 above lines are in overrideMap.xml, function list will load your parsers anotherPhpParser.xml and myPerlRule.xml instead of loaoding php.xml and perl.xml while showing PHP and Perl function list respectively.

If you previously had a v7.9-or-earlier style function list entry in functionList.xml, and you want to use it in a modern v8.x version of Notepad++, you can extract the pieces to the right locations in the new multi-file format:

This configuration file allows you to override the current toolbar icons. (New to v8.4.2) This allows you do define your own set of icons to use on the toolbar, and is useful (for example) if none of the five different icon sets available through Settings > Preferences > General > Toolbar are sufficient for your needs.

Note 2: This is the same folder descibed in Configuration Files Locations where config.xml goes, and will generally be the %APPDATA%\Notepad++\ directory, unless you are using local configuration or cloud configuration or overriding the configuration directory with -settingsDir.

For each of the 45 toolbar icons that can be customized, use the specific file name listed below. (Some toolbar buttons have two icons, one for when the button is enabled and one when the button is disabled.)

cloud\choice file: If this folder and file are present, the file contains the path to the Cloud folder. This config file is created when you define the Cloud preferences. If you are in a normal installation, this config file will be %AppData%\Notepad++\cloud\choice; if it is deleted from there, Notepad++ will not look for \cloud\choice. If you are in a portable / local configuration (doLocalConf.xml exists), it will be in \cloud\choice.

enableSelectFgColor.xml: This is a zero-byte file that is just used as an indicator to the Settings > Style Configurator > Global Styles > Selected text color to honor the foreground color, not just the background color. This config file must go in the Notepad++ installation folder; it will not be recognized in the %AppData%\Notepad++ hierarchy or in the cloud settings folder. (Available on v8.0.0 and newer.)

nppLogNulContentCorruptionIssue.xml: This is a zero-byte file that allows Notepad++ to write a logfile to %AppData%\Notepad++\nppLogNulContentCorruptionIssue.log in the case of certain crashes, which can help the developers debug issues resulting from the crash. If you want to prohibit that logfile from being created, delete this config file; but that will mean that you will not be able to provide the useful information to the developers if a crash causes issues for you; delete at your own risk. This config file must go in the Notepad++ installation folder; it will not be recognized in the %AppData%\Notepad++ hierarchy or in the cloud settings folder. (New to v8.1.9.3.)

3a8082e126