remove many v7.x mentions

- done with most files

- left brief references to v7.x in config-files and ghost-typing (and in History, of course)

Author: pryrt

content/docs/auto-completion.md

@@ -75,7 +75,7 @@ The keyboard shortcuts for manual completion can be adjusted in [**Settings > Sh
 
 ## Create auto-completion definition files
 
-Notepad++ uses XML configuration files to define the per-language function and parameter auto-completion.  Those AutoComplete files are located in the `autoCompletion` subdirectory of the Notepad++ install folder.  (In older versions, Notepad++ v7.6.1 and earlier, they were found in the `plugins\APIs` subdirectory of the intstall folder.)
+Notepad++ uses XML configuration files to define the per-language function and parameter auto-completion.  Those AutoComplete files are located in the `autoCompletion` subdirectory of the Notepad++ install folder.
 
 The syntax of AutoComplete files is simple, but does have a few rules, most importantly correct syntax and proper sorting. If the syntax is incorrect, the XML file will fail to load and AutoComplete will be not be available for that file type.
 

content/docs/command-prompt.md

@@ -157,8 +157,8 @@ code | file
 * `-qf="D:\path to\file"`: Launch [ghost typing](../ghost-typing/) to display a file content via the file path *D:\path to\file*
 * `-qSpeed(1|2|3)`: [Ghost typing](../ghost-typing/) speed. Value from 1 to 3 for slow, fast, and fastest
 * `-quickPrint`: Print the file given as argument `filepath` then quit Notepad++
-* `-settingsDir="d:\your settings dir\"`: Override the default settings dir (new to v7.9.2)
-* `-openFoldersAsWorkspace`: Any folders listed as arguments will be opened as a workspace, rather than opening all the contained files individually (new to v7.8)
+* `-settingsDir="d:\your settings dir\"`: Override the default settings dir
+* `-openFoldersAsWorkspace`: Any folders listed as arguments will be opened as a workspace, rather than opening all the contained files individually
 * `-titleAdd="additional title bar text"`: Add a dash and a space and the supplied text to the right side of the application title bar (new to v8.0.0)
 * `-pluginMessage="text for plugin(s)"`: if plugin developers need extra command line arguments, then users can add this option, and the plugin will be [notified](../plugin-communication/#NPPN_CMDLINEPLUGINMSG "NPPN_CMDLINEPLUGINMSG") that it can parse that string for extra information (new to v8.4.2)
 * `filepath`: file or folder name to open (absolute or relative path name)

content/docs/config-files.md

@@ -22,7 +22,7 @@ In a portable installation, the configuration files all go in the same directory
 
 If you enable the [Cloud settings](../preferences/#cloud), 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).
 
-There is a [command-line option](../command-prompt/) `-settingsDir` which will set a new directory for the per-user configuration file location (added in v7.9.2).
+There is a [command-line option](../command-prompt/) `-settingsDir` which will set a new directory for the per-user configuration file location.
 
 **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.
 
@@ -261,7 +261,7 @@ Position | Name | Value format | Meaning
 
 Inside each of the languages, you _could_ add keywords. However, it's better to use [**Settings > Style Configurator**](../preferences/#style-configurator) and make use of the user-defined keywords box for a given category (when available). These user-defined keywords are stored in [`stylers.xml`](#highlighting-schemes-stylers-xml) (described below).
 
-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. When using the [old-style dialogs](../preferences/#default-directory), the automatically-added extension will be the first extension from this `ext` list. As of v7.8.7, the new-style dialogs will also automatically add the first extension.
+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.
 
 The `commentLine`, `commentStart`, and `commentEnd` attributes are used by the [Edit Menu](../editing/#edit-menu)'s **Comment/Uncomment** actions for adding or removing the comment syntax to the selected lines of text. These are independent of the selected [programming **Language**](../programing-languages/)'s syntax lexer, so changing these attributes will _not_ affect what code sections will get highlighted as comments by the active syntax highlighter. (Because of the way the Scintilla library that Notepad++ uses for the lexers, in order to change what gets highlighted as a comment, one would need to edit and re-compile the lexer for the chosen and then rebuild the Notepad++ project; in other words, it would have to be changed by the developers for a new release, not changed by the user in the `langs.xml` configuration file.)  These attributes can only define one type of line and block comments; if your language has multiple types of either, you will have to choose the _one_ type that you'd like Comment/Uncomment to work with.
 
@@ -286,9 +286,8 @@ The `<WordsStyle>` `colorStyle` attribute decides whether to use the defined col
 ## `Function List`
 
 Defines what counts as a "function" for **View > Function List**. There are some comments in the file(s), and lots of examples of the builtin languages, which you can customize.
-From v7.9.1 the file structure of function list parsers have been changed, so please follow one of sections below according your Notepad++ version.
 
-### v7.9.1 and later versions
+### Function List Definitions
 
 The `functionList` folder contains a separate XML file (function list parse rule) for each language's function list capability.
 Each function list parse rule links to a language with the language default name. For example the file name of php language parse rule is `php.xml`, the file name of Java language parse rule is `java.xml`, Check [overrideMap.xml](https://github.com/notepad-plus-plus/notepad-plus-plus/blob/master/PowerEditor/installer/functionList/overrideMap.xml) for the naming list of all supported programming languages.
@@ -315,51 +314,17 @@ For plain text files (ones with **Language > None (Normal Text)** selected), you
 <association id= "someOtherNormalText.xml"			 langID= "0" />
 ```
 
-### v7.9 and previous versions
-
-The `functionList.xml` config file contains XML entries for each language's function list definition, as well as a map that tells Notepad++ which section of the XML is applied to each file type.
-
-If you want to add **Function List** capability for your User Defined Language (UDL), you can. You need to add two groups of information:
-
-1. In the `<associationMap>` section, you need to add lines like the following
-
-        <association id="fn_udl_example"          userDefinedLangName="ExampleUDL"     />
-        <association id="fn_udl_example"          ext=".ex"                            />
-        <association id="fn_udl_example"          ext=".exudl"                         />
-
-    where `fn_udl_example` is a name unique to this UDL. It is best to define it both
-    based on `userDefinedLangName=...` (which must match the name you saved for your UDL) and on extension `ext=...` (which must match the extension(s) of your UDL type, with one extension per entry).
-
-2. In the `<parsers>` section, add a parser, with a similar format to all the builtin parsers shown. An example would be
-
-        <parser
-            id="fn_udl_example"
-            displayName="Example UDL Name (UDL)"
-            commentExpr="((--.*?$))"
-        >
-            <function
-                mainExpr="^[\s]*(private[\s]+)?(procedure|function)[\s]*[\w_]+"
-                displayMode="$functionName"
-            >
-                <functionName>
-                    <nameExpr expr="^[\s]*(private[\s]+)?(procedure|function)[\s]*[\w_]+" />
-                </functionName>
-            </function>
-        </parser>
-
-    where the `fn_udl_example` must match the `<association id>`. The `displayName` sets what shows in the **Function List** window header. The `...Expr` values are all defined in [regular expression syntax](../searching/#regular-expressions).
-
 ### Upgrading old Function List entries
 
-If you previously had a v7.9-or-earlier style function list entry in `functionList.xml`, and you want to use it in a v7.9.1-or-later Notepad++, you can extract the pieces to the right locations in the new multi-file format:
+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:
 
 1. Open the old `functionList.xml`
 2. Open the `functionList\overrideMap.xml`
-3. Copy the `<association...>` tag from the old `functionList.xml` to the `functionList\overrideMap.xml`, and place near the end of the `<associationMap>` section. Make sure it follows the rules for v7.9.1-or-later `<association>` tag syntax
+3. Copy the `<association...>` tag from the old `functionList.xml` to the `functionList\overrideMap.xml`, and place near the end of the `<associationMap>` section. Make sure it follows the rules for modern `<association>` tag syntax
 4. Open the `functionList\blah.xml` for your particular language
-   - If you don't have `blah.xml` yet, copy one of the v7.9.1-or-newer language's XML files to `blah.xml`, and remove the whole `<parser...> ... </parser>` section
+   - If you don't have `blah.xml` yet, copy another language's XML file from the most-recent Notepad++ version to `blah.xml`, and remove the whole `<parser...> ... </parser>` section
 5. Copy the `<parer...>...</parser>` section from the old `functionList.xml` to the `functionList\blah.xml`
-   - Please note that the `blah.xml` should _not_ contain a `<parsers>` section, _just_ the `<parser>` section. It will cause problems with the Function List if you wrap it in the `<parsers>...</parsers>` block. Make sure it ends up with the v7.9.1-or-newer structure described above.
+   - Please note that the `blah.xml` should _not_ contain a `<parsers>` section, _just_ the `<parser>` section. It will cause problems with the Function List if you wrap it in the `<parsers>...</parsers>` block. Make sure it ends up with the structure described above.
 
 ## Toolbar Icon Customization: `toolbarIcons.xml`
 

content/docs/editing.md

@@ -152,7 +152,7 @@ Below the `Begin/End Select` entries, there are a number of sub-menus to the **E
         * `Remove Consecutive Duplicate Lines`: will only remove duplicates that are on the lines immediately following the first instance (still keeping the first instance); acts upon the line set spanned by the current selection, or the entire file if no active selection
         * NOTE: Duplicates removal is performed with the assumption that all line-endings in the file are uniform and match the current selection for the file being edited -- the quickest way to check that selection is to glance at the status bar, where the current line-ending type is shown either as `Windows (CR LF)`, `Unix (LF)` or `Macintosh (CR)`.  It might be desirable to check the line-ending types in your file before executing a sorting operation, and use the `Edit > EOL Conversion >` choices or right-click on the Status Bar's EOL indicator to fix the line endings if necessary.
     * There are methods for splitting lines and joining lines together:
-        * `Split Lines`: will insert a line-ending into a long line(s): if there is one or more [Vertical Edge](../preferences/#margins-border-edge) value specified (requires v7.9.3 or later), it will split at the right-most Vertical Edge; otherwise, it will split at the current size of the editor window.  It operates on the lines spanned by the current stream selection or the single line of the caret if no stream selection is currently active.
+        * `Split Lines`: will insert a line-ending into a long line(s): if there is one or more [Vertical Edge](../preferences/#margins-border-edge) value specified, it will split at the right-most Vertical Edge; otherwise, it will split at the current size of the editor window.  It operates on the lines spanned by the current stream selection or the single line of the caret if no stream selection is currently active.
         * `Join Lines`: will combine the lines touched by the active stream selection by replacing line-endings with a single space character. It requires an active stream selection that spans two or more lines.
     * There are commands for removing lines
         * `Remove empty lines`: will remove all lines containing no characters from the entire document
@@ -161,7 +161,7 @@ Below the `Begin/End Select` entries, there are a number of sub-menus to the **E
         * `Move Up Current Line`: will swap the current line with the line above it, effectively moving the line of the caret up one row in the document; if a selection spanning lines is active upon invocation, it will move those lines touched by the selection up as a group
         * `Move Down Current Line`: will swap the current line with the line below it, effectively moving the line of the caret down one row in the document; if a selection spanning lines is active upon invocation, it will move those lines touched by the selection down as a group
         * `Reverse Line Order`: will take the selected lines (or all of the lines of the current document if no active selection) and will order them reversely (i.e. flipped) from their existing order (added in v8.0.0)
-        * `Randomize Line Order`: will take the selected lines (or all of the lines of the current document if no active selection) and place them in an unpredictable order (added in v7.9 as "Sort Lines Randomly"; renamed in v8.0.0)
+        * `Randomize Line Order`: will take the selected lines (or all of the lines of the current document if no active selection) and place them in an unpredictable order
     * There are a variety of sorting algorithms:
         * `Ascending` means smallest to largest (A-Z)
         * `Descending` means largest to smallest (Z-A)

content/docs/ghost-typing.md

@@ -60,15 +60,4 @@ These options apply to any of the ghost typing modes, unless otherwise mentioned
 
 ## Historical Syntax
 
-The syntax listed above is valid for Notepad++ v7.9.2 and newer.
-
-In Notepad++ v7.9.1 and earlier, there were differnces in the syntax:
-
-* the command-line options for the ghost typing modes did not use the `=`,
-  so it would be interpreted as literal text (part of the value)
-* quotes were interpreted as literal text (part of the value)
-* the sequence `%20` was used to represent a space, since you could not
-  use quotes to make spaces significant.
-
-Keep these differences in mind if using older versions of Notepad++.
-
+The syntax listed above is valid for Notepad++ v8 and newer.  If you have a v7.x version of Notepad++, please download the [last offline User Manual that contains Notepad++ v7.x details](https://github.com/notepad-plus-plus/npp-usermanual/releases/download/3.6/nppUserManual.zip)

content/docs/plugin-communication.md

@@ -1382,7 +1382,7 @@ Bit 30 indicates which view has the buffer (clear for main view, set for sub vie
 
 ---
 #### [2122] **NPPM_GETSETTINGSONCLOUDPATH**
-*Get settings on cloud path. It's useful if plugins want to store its settings on Cloud, if this path is set. (added v7.9.2).*
+*Get settings on cloud path. It's useful if plugins want to store its settings on Cloud, if this path is set.*
 
 *First call should be made with buffer set to NULL to retrieve the actual size needed.
 Second call is sent with correctly allocated buffer, +1 for trailing null, to retrieve the full path file name.*