Diff to HTML by rtfpessoa

Files changed (10) hide show
  1. runtime/doc/fold.txt +36 -8
  2. runtime/doc/indent.txt +1 -1
  3. runtime/doc/index.txt +2 -1
  4. runtime/doc/pi_tutor.txt +16 -9
  5. runtime/doc/quickfix.txt +73 -19
  6. runtime/doc/syntax.txt +3 -1
  7. runtime/doc/todo.txt +1 -4
  8. runtime/doc/usr_01.txt +3 -3
  9. runtime/doc/version9.txt +4 -2
  10. runtime/doc/windows.txt +10 -1
runtime/doc/fold.txt CHANGED
@@ -1,4 +1,4 @@
1
- *fold.txt* For Vim version 9.1. Last change: 2023 Mar 24
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
@@ -87,9 +87,11 @@ The most efficient is to call a compiled function without arguments: >
87
  The function must use v:lnum. See |expr-option-function|.
88
 
89
  These are the conditions with which the expression is evaluated:
 
90
  - The current buffer and window are set for the line.
91
  - The variable "v:lnum" is set to the line number.
92
- - The result is used for the fold level in this way:
 
93
  value meaning ~
94
  0 the line is not in a fold
95
  1, 2, .. the line is in a fold with this level
@@ -104,6 +106,8 @@ These are the conditions with which the expression is evaluated:
104
  "<1", "<2", .. a fold with this level ends at this line
105
  ">1", ">2", .. a fold with this level starts at this line
106
 
 
 
107
  It is not required to mark the start (end) of a fold with ">1" ("<1"), a fold
108
  will also start (end) when the fold level is higher (lower) than the fold
109
  level of the previous line.
@@ -117,12 +121,6 @@ recognized, there is no error message and the fold level will be zero.
117
  For debugging the 'debug' option can be set to "msg", the error messages will
118
  be visible then.
119
 
120
- Note: Since the expression has to be evaluated for every line, this fold
121
- method can be very slow!
122
-
123
- Try to avoid the "=", "a" and "s" return values, since Vim often has to search
124
- backwards for a line for which the fold level is defined. This can be slow.
125
-
126
  If the 'foldexpr' expression starts with s: or |<SID>|, then it is replaced
127
  with the script ID (|local-function|). Examples: >
128
  set foldexpr=s:MyFoldExpr()
@@ -148,6 +146,36 @@ end in that line.
148
  It may happen that folds are not updated properly. You can use |zx| or |zX|
149
  to force updating folds.
150
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
151
 
152
  SYNTAX *fold-syntax*
153
 
1
+ *fold.txt* For Vim version 9.1. Last change: 2024 Dec 16
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
87
  The function must use v:lnum. See |expr-option-function|.
88
 
89
  These are the conditions with which the expression is evaluated:
90
+
91
  - The current buffer and window are set for the line.
92
  - The variable "v:lnum" is set to the line number.
93
+
94
+ The result of foldexpr then determines the fold level as follows:
95
  value meaning ~
96
  0 the line is not in a fold
97
  1, 2, .. the line is in a fold with this level
106
  "<1", "<2", .. a fold with this level ends at this line
107
  ">1", ">2", .. a fold with this level starts at this line
108
 
109
+ The result values "=", "s" and "a" are more expensive, please see |fold-expr-slow|.
110
+
111
  It is not required to mark the start (end) of a fold with ">1" ("<1"), a fold
112
  will also start (end) when the fold level is higher (lower) than the fold
113
  level of the previous line.
121
  For debugging the 'debug' option can be set to "msg", the error messages will
122
  be visible then.
123
 
 
 
 
 
 
 
124
  If the 'foldexpr' expression starts with s: or |<SID>|, then it is replaced
125
  with the script ID (|local-function|). Examples: >
126
  set foldexpr=s:MyFoldExpr()
146
  It may happen that folds are not updated properly. You can use |zx| or |zX|
147
  to force updating folds.
148
 
149
+ Minimizing Computational Cost *fold-expr-slow*
150
+
151
+ Due to its computational cost, this fold method can make Vim unresponsive,
152
+ especially when the fold level of all lines have to be initially computed.
153
+ Afterwards, after each change, Vim restricts the computation of foldlevels
154
+ to those lines whose fold level was affected by it (and reuses the known
155
+ foldlevels of all the others).
156
+
157
+ The fold expression should therefore strive to minimize the number of dependent
158
+ lines needed for the computation of a given line: For example, try to avoid the
159
+ "=", "a" and "s" return values, because these will require the evaluation of the
160
+ fold levels on previous lines until an independent fold level is found.
161
+
162
+ If this proves difficult, the next best thing could be to cache all fold levels
163
+ in a buffer-local variable (b:foldlevels) that is only updated on |b:changedtick|:
164
+ >vim
165
+ vim9script
166
+ def MyFoldFunc(): number
167
+ if b:lasttick == b:changedtick
168
+ return b:foldlevels[v:lnum - 1]
169
+ endif
170
+ b:lasttick = b:changedtick
171
+ b:foldlevels = []
172
+ # compute foldlevels ...
173
+ return b:foldlevels[v:lnum - 1]
174
+ enddef
175
+ set foldexpr=s:MyFoldFunc()
176
+ <
177
+ In above example further speedup was gained by using a precompiled Vim9script
178
+ function without arguments (that must still use v:lnum). See |expr-option-function|.
179
 
180
  SYNTAX *fold-syntax*
181
 
runtime/doc/indent.txt CHANGED
@@ -1,4 +1,4 @@
1
- *indent.txt* For Vim version 9.1. Last change: 2024 Nov 12
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
1
+ *indent.txt* For Vim version 9.1. Last change: 2024 Dec 16
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
runtime/doc/index.txt CHANGED
@@ -1,4 +1,4 @@
1
- *index.txt* For Vim version 9.1. Last change: 2023 Jul 14
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
@@ -1529,6 +1529,7 @@ tag command action ~
1529
  |:ownsyntax| :ow[nsyntax] set new local syntax highlight for this window
1530
  |:packadd| :pa[ckadd] add a plugin from 'packpath'
1531
  |:packloadall| :packl[oadall] load all packages under 'packpath'
 
1532
  |:pclose| :pc[lose] close preview window
1533
  |:pedit| :ped[it] edit file in the preview window
1534
  |:perl| :pe[rl] execute Perl command
1
+ *index.txt* For Vim version 9.1. Last change: 2024 Dec 15
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
1529
  |:ownsyntax| :ow[nsyntax] set new local syntax highlight for this window
1530
  |:packadd| :pa[ckadd] add a plugin from 'packpath'
1531
  |:packloadall| :packl[oadall] load all packages under 'packpath'
1532
+ |:pbuffer| :pb[uffer] edit buffer in the preview window
1533
  |:pclose| :pc[lose] close preview window
1534
  |:pedit| :ped[it] edit file in the preview window
1535
  |:perl| :pe[rl] execute Perl command
runtime/doc/pi_tutor.txt CHANGED
@@ -1,4 +1,4 @@
1
- *pi_tutor.txt* For Vim version 9.1. Last change: 2024 Nov 09
2
 
3
  INTERACTIVE TUTORIALS FOR VIM *vim-tutor-mode*
4
 
@@ -16,21 +16,28 @@ by double-clicking them.
16
  1.1 Commands
17
  ------------
18
  *:Tutor*
19
- :Tutor {tutorial} Opens a tutorial. Command-line completion for
20
- {tutorial} is provided, the candidates are a list of
21
- '.tutor' files found in the 'tutor/' folder in
22
- the 'runtimepath'. Tutorials prefixed with 'vim-'
23
  will always be shown first.
24
 
25
- If no {tutorial} is provided, the command starts the
26
- 'vim-01-beginner' tutorial, which is equivalent to
27
- Vim's `vimtutor`.
28
 
 
 
 
 
 
 
 
29
  =============================================================================
30
  2. Creating tutorials *vim-tutor-create*
31
 
32
  Writing vim-tutor-mode tutorials is easy. For an overview of the format used,
33
- please consult the 'tutor.tutor' file: >
34
 
35
  :Tutor tutor
36
  <
1
+ *pi_tutor.txt* For Vim version 9.1. Last change: 2024 Dec 16
2
 
3
  INTERACTIVE TUTORIALS FOR VIM *vim-tutor-mode*
4
 
16
  1.1 Commands
17
  ------------
18
  *:Tutor*
19
+ :Tutor [tutorial] Opens a tutorial. Command-line completion for
20
+ [tutorial] is provided, the candidates are a list of
21
+ ".tutor" files found in the "tutor/<lang>/" folder in
22
+ the 'runtimepath'. Tutorials prefixed with "vim-"
23
  will always be shown first.
24
 
25
+ If no [tutorial] is provided, the command starts the
26
+ "vim-01-beginner" tutorial, which is equivalent to
27
+ Vim's `vimtutor`, chapter 1.
28
 
29
+ Uses the translated tutorial for the current message
30
+ language if possible (|v:lang|), e.g. to open the
31
+ chapter 1 of the Italian tutor, use: >
32
+
33
+ :lang it_IT.utf-8
34
+ :Tutor
35
+ <
36
  =============================================================================
37
  2. Creating tutorials *vim-tutor-create*
38
 
39
  Writing vim-tutor-mode tutorials is easy. For an overview of the format used,
40
+ please consult the "tutor.tutor" file: >
41
 
42
  :Tutor tutor
43
  <
runtime/doc/quickfix.txt CHANGED
@@ -1,4 +1,4 @@
1
- *quickfix.txt* For Vim version 9.1. Last change: 2024 Nov 28
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
@@ -1349,7 +1349,7 @@ It scans the Java bytecode of all classes in the currently open buffer.
1349
  (Therefore, `:compiler! spotbugs` is not supported.)
1350
 
1351
  Commonly used compiler options can be added to 'makeprg' by setting the
1352
- "b:" or "g:spotbugs_makeprg_params" variable. For example: >
1353
 
1354
  let b:spotbugs_makeprg_params = "-longBugCodes -effort:max -low"
1355
 
@@ -1359,22 +1359,25 @@ By default, the class files are searched in the directory where the source
1359
  files are placed. However, typical Java projects use distinct directories
1360
  for source files and class files. To make both known to SpotBugs, assign
1361
  their paths (distinct and relative to their common root directory) to the
1362
- following properties (using the example of a common Maven project): >
1363
 
1364
  let g:spotbugs_properties = {
1365
- \ 'sourceDirPath': 'src/main/java',
1366
- \ 'classDirPath': 'target/classes',
1367
- \ 'testSourceDirPath': 'src/test/java',
1368
- \ 'testClassDirPath': 'target/test-classes',
1369
  \ }
1370
 
 
 
 
1371
  Note that values for the path keys describe only for SpotBugs where to look
1372
  for files; refer to the documentation for particular compiler plugins for more
1373
  information.
1374
 
1375
  The default pre- and post-compiler actions are provided for Ant, Maven, and
1376
  Javac compiler plugins and can be selected by assigning the name of a compiler
1377
- plugin to the "compiler" key: >
1378
 
1379
  let g:spotbugs_properties = {
1380
  \ 'compiler': 'maven',
@@ -1384,7 +1387,7 @@ This single setting is essentially equivalent to all the settings below, with
1384
  the exception made for the "PreCompilerAction" and "PreCompilerTestAction"
1385
  values: their listed |Funcref|s will obtain no-op implementations whereas the
1386
  implicit Funcrefs of the "compiler" key will obtain the requested defaults if
1387
- available. >
1388
 
1389
  let g:spotbugs_properties = {
1390
  \ 'PreCompilerAction':
@@ -1393,10 +1396,10 @@ available. >
1393
  \ function('spotbugs#DefaultPreCompilerTestAction'),
1394
  \ 'PostCompilerAction':
1395
  \ function('spotbugs#DefaultPostCompilerAction'),
1396
- \ 'sourceDirPath': 'src/main/java',
1397
- \ 'classDirPath': 'target/classes',
1398
- \ 'testSourceDirPath': 'src/test/java',
1399
- \ 'testClassDirPath': 'target/test-classes',
1400
  \ }
1401
 
1402
  With default actions, the compiler of choice will attempt to rebuild the class
@@ -1404,23 +1407,42 @@ files for the buffer (and possibly for the whole project) as soon as a Java
1404
  syntax file is loaded; then, `spotbugs` will attempt to analyze the quality of
1405
  the compilation unit of the buffer.
1406
 
1407
- When default actions are not suited to a desired workflow, consider writing
1408
- arbitrary functions yourself and matching their |Funcref|s to the supported
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1409
  keys: "PreCompilerAction", "PreCompilerTestAction", and "PostCompilerAction".
1410
 
1411
  The next example re-implements the default pre-compiler actions for a Maven
1412
- project and requests other default Maven settings with the "compiler" entry: >
1413
-
1414
  function! MavenPreCompilerAction() abort
1415
  call spotbugs#DeleteClassFiles()
1416
  compiler maven
1417
  make compile
 
1418
  endfunction
1419
 
1420
  function! MavenPreCompilerTestAction() abort
1421
  call spotbugs#DeleteClassFiles()
1422
  compiler maven
1423
  make test-compile
 
1424
  endfunction
1425
 
1426
  let g:spotbugs_properties = {
@@ -1433,14 +1455,46 @@ project and requests other default Maven settings with the "compiler" entry: >
1433
 
1434
  Note that all entered custom settings will take precedence over the matching
1435
  default settings in "g:spotbugs_properties".
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1436
 
1437
  The "g:spotbugs_properties" variable is consulted by the Java filetype plugin
1438
  (|ft-java-plugin|) to arrange for the described automation, and, therefore, it
1439
  must be defined before |FileType| events can take place for the buffers loaded
1440
  with Java source files. It could, for example, be set in a project-local
1441
- |vimrc| loaded by [0].
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1442
 
1443
- [0] https://github.com/MarcWeber/vim-addon-local-vimrc/
 
 
1444
 
1445
  GNU MAKE *compiler-make*
1446
 
1
+ *quickfix.txt* For Vim version 9.1. Last change: 2024 Dec 16
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
1349
  (Therefore, `:compiler! spotbugs` is not supported.)
1350
 
1351
  Commonly used compiler options can be added to 'makeprg' by setting the
1352
+ "b:" or "g:spotbugs_makeprg_params" variable. For example: >vim
1353
 
1354
  let b:spotbugs_makeprg_params = "-longBugCodes -effort:max -low"
1355
 
1359
  files are placed. However, typical Java projects use distinct directories
1360
  for source files and class files. To make both known to SpotBugs, assign
1361
  their paths (distinct and relative to their common root directory) to the
1362
+ following properties (using the example of a common Maven project): >vim
1363
 
1364
  let g:spotbugs_properties = {
1365
+ \ 'sourceDirPath': ['src/main/java'],
1366
+ \ 'classDirPath': ['target/classes'],
1367
+ \ 'testSourceDirPath': ['src/test/java'],
1368
+ \ 'testClassDirPath': ['target/test-classes'],
1369
  \ }
1370
 
1371
+ Note that source and class path entries are expected to come in pairs: define
1372
+ both "sourceDirPath" and "classDirPath" when you are considering at least one,
1373
+ and apply the same logic to "testSourceDirPath" and "testClassDirPath".
1374
  Note that values for the path keys describe only for SpotBugs where to look
1375
  for files; refer to the documentation for particular compiler plugins for more
1376
  information.
1377
 
1378
  The default pre- and post-compiler actions are provided for Ant, Maven, and
1379
  Javac compiler plugins and can be selected by assigning the name of a compiler
1380
+ plugin (`ant`, `maven`, or `javac`) to the "compiler" key: >vim
1381
 
1382
  let g:spotbugs_properties = {
1383
  \ 'compiler': 'maven',
1387
  the exception made for the "PreCompilerAction" and "PreCompilerTestAction"
1388
  values: their listed |Funcref|s will obtain no-op implementations whereas the
1389
  implicit Funcrefs of the "compiler" key will obtain the requested defaults if
1390
+ available. >vim
1391
 
1392
  let g:spotbugs_properties = {
1393
  \ 'PreCompilerAction':
1396
  \ function('spotbugs#DefaultPreCompilerTestAction'),
1397
  \ 'PostCompilerAction':
1398
  \ function('spotbugs#DefaultPostCompilerAction'),
1399
+ \ 'sourceDirPath': ['src/main/java'],
1400
+ \ 'classDirPath': ['target/classes'],
1401
+ \ 'testSourceDirPath': ['src/test/java'],
1402
+ \ 'testClassDirPath': ['target/test-classes'],
1403
  \ }
1404
 
1405
  With default actions, the compiler of choice will attempt to rebuild the class
1407
  syntax file is loaded; then, `spotbugs` will attempt to analyze the quality of
1408
  the compilation unit of the buffer.
1409
 
1410
+ Vim commands proficient in 'makeprg' [0] can be composed with default actions.
1411
+ Begin by considering which of the supported keys, "DefaultPreCompilerCommand",
1412
+ "DefaultPreCompilerTestCommand", or "DefaultPostCompilerCommand", you need to
1413
+ write an implementation for, observing that each of these keys corresponds to
1414
+ a particular "*Action" key. Follow it by defining a new function that always
1415
+ declares an only parameter of type string and puts to use a command equivalent
1416
+ of |:make|, and assigning its |Funcref| to the selected key. For example:
1417
+ >vim
1418
+ function! GenericPostCompilerCommand(arguments) abort
1419
+ execute 'make ' . a:arguments
1420
+ endfunction
1421
+
1422
+ let g:spotbugs_properties = {
1423
+ \ 'DefaultPostCompilerCommand':
1424
+ \ function('GenericPostCompilerCommand'),
1425
+ \ }
1426
+
1427
+ When default actions are not suited to a desired workflow, proceed by writing
1428
+ arbitrary functions yourself and matching their Funcrefs to the supported
1429
  keys: "PreCompilerAction", "PreCompilerTestAction", and "PostCompilerAction".
1430
 
1431
  The next example re-implements the default pre-compiler actions for a Maven
1432
+ project and requests other default Maven settings with the "compiler" entry:
1433
+ >vim
1434
  function! MavenPreCompilerAction() abort
1435
  call spotbugs#DeleteClassFiles()
1436
  compiler maven
1437
  make compile
1438
+ cc
1439
  endfunction
1440
 
1441
  function! MavenPreCompilerTestAction() abort
1442
  call spotbugs#DeleteClassFiles()
1443
  compiler maven
1444
  make test-compile
1445
+ cc
1446
  endfunction
1447
 
1448
  let g:spotbugs_properties = {
1455
 
1456
  Note that all entered custom settings will take precedence over the matching
1457
  default settings in "g:spotbugs_properties".
1458
+ Note that it is necessary to notify the plugin of the result of a pre-compiler
1459
+ action before further work can be undertaken. Using |:cc| after |:make| (or
1460
+ |:ll| after |:lmake|) as the last command of an action is the supported means
1461
+ of such communication.
1462
+
1463
+ Two commands, "SpotBugsRemoveBufferAutocmd" and "SpotBugsDefineBufferAutocmd",
1464
+ are provided to toggle actions for buffer-local autocommands. For example, to
1465
+ also run actions on any |BufWritePost| and |SigUSR1| event, add these lines to
1466
+ `~/.vim/after/ftplugin/java.vim`: >vim
1467
+
1468
+ if exists(':SpotBugsDefineBufferAutocmd') == 2
1469
+ SpotBugsDefineBufferAutocmd BufWritePost SigUSR1
1470
+ endif
1471
+
1472
+ Otherwise, you can turn to `:doautocmd java_spotbugs User` at any time.
1473
 
1474
  The "g:spotbugs_properties" variable is consulted by the Java filetype plugin
1475
  (|ft-java-plugin|) to arrange for the described automation, and, therefore, it
1476
  must be defined before |FileType| events can take place for the buffers loaded
1477
  with Java source files. It could, for example, be set in a project-local
1478
+ |vimrc| loaded by [1].
1479
+
1480
+ Both "g:spotbugs_properties" and "b:spotbugs_properties" are recognized and
1481
+ must be modifiable (|:unlockvar|). The "*Command" entries are always treated
1482
+ as global functions to be shared among all Java buffers.
1483
+
1484
+ The SpotBugs Java library and, by extension, its distributed shell scripts do
1485
+ not support in the `-textui` mode listed pathnames with directory filenames
1486
+ that contain blank characters [2]. To work around this limitation, consider
1487
+ making a symbolic link to such a directory from a directory that does not have
1488
+ blank characters in its name and passing this information to SpotBugs: >vim
1489
+
1490
+ let g:spotbugs_alternative_path = {
1491
+ \ 'fromPath': 'path/to/dir_without_blanks',
1492
+ \ 'toPath': 'path/to/dir with blanks',
1493
+ \ }
1494
 
1495
+ [0] https://github.com/Konfekt/vim-compilers
1496
+ [1] https://github.com/MarcWeber/vim-addon-local-vimrc
1497
+ [2] https://github.com/spotbugs/spotbugs/issues/909
1498
 
1499
  GNU MAKE *compiler-make*
1500
 
runtime/doc/syntax.txt CHANGED
@@ -1,4 +1,4 @@
1
- *syntax.txt* For Vim version 9.1. Last change: 2024 Dec 12
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
@@ -5857,6 +5857,8 @@ PmenuThumb Popup menu: Thumb of the scrollbar.
5857
  PmenuMatch Popup menu: Matched text in normal item.
5858
  *hl-PmenuMatchSel*
5859
  PmenuMatchSel Popup menu: Matched text in selected item.
 
 
5860
  *hl-PopupNotification*
5861
  PopupNotification
5862
  Popup window created with |popup_notification()|. If not
1
+ *syntax.txt* For Vim version 9.1. Last change: 2024 Dec 16
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
5857
  PmenuMatch Popup menu: Matched text in normal item.
5858
  *hl-PmenuMatchSel*
5859
  PmenuMatchSel Popup menu: Matched text in selected item.
5860
+ *hl-ComplMatchIns*
5861
+ ComplMatchIns Matched text of the currently inserted completion.
5862
  *hl-PopupNotification*
5863
  PopupNotification
5864
  Popup window created with |popup_notification()|. If not
runtime/doc/todo.txt CHANGED
@@ -1,4 +1,4 @@
1
- *todo.txt* For Vim version 9.1. Last change: 2024 Dec 04
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
@@ -1093,9 +1093,6 @@ Problem with 'delcombine'. (agguser, 2017 Nov 10, #2313)
1093
  MS-Windows: buffer completion doesn't work when using backslash (or slash)
1094
  for a path separator. (xtal8, #2201)
1095
 
1096
- Would be nice for Insert mode completion to highlight the text that was added
1097
- (and may change when picking another completion).
1098
-
1099
  Test more runtime files.
1100
 
1101
  Window not closed when deleting buffer. (Harm te Hennepe, 2017 Aug 27, #2029)
1
+ *todo.txt* For Vim version 9.1. Last change: 2024 Dec 16
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
1093
  MS-Windows: buffer completion doesn't work when using backslash (or slash)
1094
  for a path separator. (xtal8, #2201)
1095
 
 
 
 
1096
  Test more runtime files.
1097
 
1098
  Window not closed when deleting buffer. (Harm te Hennepe, 2017 Aug 27, #2029)
runtime/doc/usr_01.txt CHANGED
@@ -1,4 +1,4 @@
1
- *usr_01.txt* For Vim version 9.1. Last change: 2024 Nov 03
2
 
3
  VIM USER MANUAL - by Bram Moolenaar
4
 
@@ -110,8 +110,8 @@ For more info see |vimrc| and |compatible-default|.
110
  For the interactive tutor, see |vim-tutor-mode|
111
 
112
  Instead of reading the text (boring!) you can use the vimtutor to learn your
113
- first Vim commands. This is a 30-minute tutorial that teaches the most basic
114
- Vim functionality hands-on.
115
 
116
  On Unix, if Vim has been properly installed, you can start it from the shell:
117
  >
1
+ *usr_01.txt* For Vim version 9.1. Last change: 2024 Dec 16
2
 
3
  VIM USER MANUAL - by Bram Moolenaar
4
 
110
  For the interactive tutor, see |vim-tutor-mode|
111
 
112
  Instead of reading the text (boring!) you can use the vimtutor to learn your
113
+ first Vim commands. This is a 30-minute tutorial provided in 2 chapters, that
114
+ teaches the most basic Vim functionality hands-on.
115
 
116
  On Unix, if Vim has been properly installed, you can start it from the shell:
117
  >
runtime/doc/version9.txt CHANGED
@@ -1,4 +1,4 @@
1
- *version9.txt* For Vim version 9.1. Last change: 2024 Dec 06
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
@@ -41653,6 +41653,7 @@ Autocommands: ~
41653
 
41654
  Highlighting: ~
41655
 
 
41656
  |hl-MsgArea| highlighting of the Command-line and messages area
41657
  |hl-PmenuMatch| Popup menu: highlighting of matched text
41658
  |hl-PmenuMatchSel| Popup menu: highlighting of matched text in selected
@@ -41661,7 +41662,8 @@ Highlighting: ~
41661
  Commands: ~
41662
 
41663
  |[r| and |]r| to move the cursor to previous/next rare word
41664
-
 
41665
 
41666
  Options: ~
41667
 
1
+ *version9.txt* For Vim version 9.1. Last change: 2024 Dec 16
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
41653
 
41654
  Highlighting: ~
41655
 
41656
+ |hl-ComplMatchIns| matched text of the currently inserted completion.
41657
  |hl-MsgArea| highlighting of the Command-line and messages area
41658
  |hl-PmenuMatch| Popup menu: highlighting of matched text
41659
  |hl-PmenuMatchSel| Popup menu: highlighting of matched text in selected
41662
  Commands: ~
41663
 
41664
  |[r| and |]r| to move the cursor to previous/next rare word
41665
+ |:pbuffer| Edit buffer [N] from the buffer list in the preview
41666
+ window
41667
 
41668
  Options: ~
41669
 
runtime/doc/windows.txt CHANGED
@@ -1,4 +1,4 @@
1
- *windows.txt* For Vim version 9.1. Last change: 2024 Dec 14
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
@@ -1005,6 +1005,15 @@ CTRL-W g } *CTRL-W_g}*
1005
  it. Make the new Preview window (if required) N high. If N is
1006
  not given, 'previewheight' is used.
1007
 
 
 
 
 
 
 
 
 
 
1008
  *:ped* *:pedit*
1009
  :ped[it][!] [++opt] [+cmd] {file}
1010
  Edit {file} in the preview window. The preview window is
1
+ *windows.txt* For Vim version 9.1. Last change: 2024 Dec 16
2
 
3
 
4
  VIM REFERENCE MANUAL by Bram Moolenaar
1005
  it. Make the new Preview window (if required) N high. If N is
1006
  not given, 'previewheight' is used.
1007
 
1008
+ *:pb* *:pbuffer*
1009
+ :[N]pb[uffer][!] [+cmd] [N]
1010
+ Edit buffer [N] from the buffer list in the preview window.
1011
+ If [N] is not given, the current buffer remains being edited.
1012
+ See |:buffer-!| for [!]. This will also edit a buffer that is
1013
+ not in the buffer list, without setting the 'buflisted' flag.
1014
+ The notation with single quotes does not work here, `:pbuffer
1015
+ 12'345'` uses 12'345 as a buffer name. Also see |+cmd|.
1016
+
1017
  *:ped* *:pedit*
1018
  :ped[it][!] [++opt] [+cmd] {file}
1019
  Edit {file} in the preview window. The preview window is