Skip to content

Commit f177d12

Browse files
committed
{popup,repeat,syntax}.txt: Update Vim 8.2.2817
1 parent dd78773 commit f177d12

File tree

3 files changed

+19
-18
lines changed

3 files changed

+19
-18
lines changed

en/popup.txt

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
*popup.txt* For Vim version 8.2. Last change: 2021 Feb 06
1+
*popup.txt* For Vim version 8.2. Last change: 2021 Feb 21
22

33

44
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -693,8 +693,8 @@ The second argument of |popup_create()| is a dictionary with options:
693693
the left.
694694
border List with numbers, defining the border thickness
695695
above/right/below/left of the popup (similar to CSS).
696-
Only values of zero and non-zero are recognized.
697-
An empty list uses a border all around.
696+
Only values of zero and non-zero are currently
697+
recognized. An empty list uses a border all around.
698698
borderhighlight List of highlight group names to use for the border.
699699
When one entry it is used for all borders, otherwise
700700
the highlight for the top/right/bottom/left border.
@@ -742,10 +742,10 @@ The second argument of |popup_create()| is a dictionary with options:
742742
line or to another window.
743743
mousemoved Like "moved" but referring to the mouse pointer
744744
position
745-
cursorline non-zero: Highlight the cursor line. Also scrolls the
746-
text to show this line (only works properly
747-
when 'wrap' is off).
748-
zero: Do not highlight the cursor line.
745+
cursorline TRUE: Highlight the cursor line. Also scrolls the
746+
text to show this line (only works properly
747+
when 'wrap' is off).
748+
zero: Do not highlight the cursor line.
749749
Default is zero, except for |popup_menu()|.
750750
filter A callback that can filter typed characters, see
751751
|popup-filter|.

en/repeat.txt

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
*repeat.txt* For Vim version 8.2. Last change: 2021 Jan 23
1+
*repeat.txt* For Vim version 8.2. Last change: 2021 Feb 13
22

33

44
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -677,9 +677,9 @@ Your directory layout would be like this:
677677
opt/fooextra/doc/tags " help tags
678678

679679
This allows for the user to do: >
680-
mkdir ~/.vim/pack/myfoobar
681-
cd ~/.vim/pack/myfoobar
682-
git clone https://github.com/you/foobar.git
680+
mkdir ~/.vim/pack
681+
cd ~/.vim/pack
682+
git clone https://github.com/you/foobar.git myfoobar
683683
684684
Here "myfoobar" is a name that the user can choose, the only condition is that
685685
it differs from other packages.
@@ -879,7 +879,7 @@ DEFINING BREAKPOINTS
879879
valid in the script where it has been defined and if that
880880
script is called from several other scripts, this will stop
881881
whenever that particular variable will become visible or
882-
unaccessible again.
882+
inaccessible again.
883883

884884
The [lnum] is the line number of the breakpoint. Vim will stop at or after
885885
this line. When omitted line 1 is used.

en/syntax.txt

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
*syntax.txt* For Vim version 8.2. Last change: 2021 Jan 21
1+
*syntax.txt* For Vim version 8.2. Last change: 2021 Apr 02
22

33

44
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -1741,8 +1741,8 @@ The coloring scheme for tags in the HTML file works as follows.
17411741

17421742
The <> of opening tags are colored differently than the </> of a closing tag.
17431743
This is on purpose! For opening tags the 'Function' color is used, while for
1744-
closing tags the 'Type' color is used (See syntax.vim to check how those are
1745-
defined for you)
1744+
closing tags the 'Identifier' color is used (See syntax.vim to check how those
1745+
are defined for you)
17461746

17471747
Known tag names are colored the same way as statements in C. Unknown tag
17481748
names are colored with the same color as the <> or </> respectively which
@@ -2236,9 +2236,10 @@ can use them.
22362236

22372237
For example, Linux and BSD distributions use groff as their default text
22382238
processing package. In order to activate the extra syntax highlighting
2239-
features for groff, add the following option to your start-up files: >
2239+
features for groff, arrange for files to be recognized as groff (see
2240+
|ft-groff-syntax|) or add the following option to your start-up files: >
22402241
2241-
:let b:nroff_is_groff = 1
2242+
:let nroff_is_groff = 1
22422243
22432244
Groff is different from the old AT&T n/troff that you may still find in
22442245
Solaris. Groff macro and request names can be longer than 2 characters and
@@ -4676,7 +4677,7 @@ matches, nextgroup, etc. But there are a few differences:
46764677
- A line continuation pattern can be given. It is used to decide which group
46774678
of lines need to be searched like they were one line. This means that the
46784679
search for a match with the specified items starts in the first of the
4679-
consecutive that contain the continuation pattern.
4680+
consecutive lines that contain the continuation pattern.
46804681
- When using "nextgroup" or "contains", this only works within one line (or
46814682
group of continued lines).
46824683
- When using a region, it must start and end in the same line (or group of

0 commit comments

Comments
 (0)