aniani/vim
0
0
Fork 1
mirror of https://github.com/vim/vim.git synced 2025-07-26 11:04:33 -04:00
Code

runtime(doc): Fix to two-space convention in user manual

Browse Source 
closes: #15802

Signed-off-by: h-east <h.east.727@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
This commit is contained in:
h-east 2024-10-05 16:44:27 +02:00 committed by Christian Brabandt
parent 7b27fc49a8
commit 8ee0e0b8e3
No known key found for this signature in database
GPG Key ID: F3F92DA383FDDE09
6 changed files with 25 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
runtime/doc/usr_02.txt
View File

@ -1,4 +1,4 @@
*usr_02.txt* For Vim version 9.1. Last change: 2021 Apr 24 *usr_02.txt* For Vim version 9.1. Last change: 2024 Oct 05
VIM USER MANUAL - by Bram Moolenaar VIM USER MANUAL - by Bram Moolenaar
@ -32,7 +32,7 @@ To start Vim, enter this command: >
In UNIX you can type this at any command prompt. If you are running Microsoft In UNIX you can type this at any command prompt. If you are running Microsoft
Windows, open a Command Prompt and enter the command. Windows, open a Command Prompt and enter the command.
In either case, Vim starts editing a file called file.txt. Because this In either case, Vim starts editing a file called file.txt. Because this
is a new file, you get a blank window. This is what your screen will look is a new file, you get a blank window. This is what your screen will look
like: like:
+---------------------------------------+ +---------------------------------------+
@ -322,7 +322,7 @@ the "a" (append) command.
to to
and that's not saying much for the turtle!!! ~ and that's not saying much for the turtle!!! ~
move the cursor over to the dot at the end of the line. Then type "x" to move the cursor over to the dot at the end of the line. Then type "x" to
delete the period. The cursor is now positioned at the end of the line on the delete the period. The cursor is now positioned at the end of the line on the
e in turtle. Now type > e in turtle. Now type >
@ -535,7 +535,7 @@ Summary: *help-summary* >
< And for the 'guioptions' flags: > < And for the 'guioptions' flags: >
:help go-<letter> :help go-<letter>
4) Normal mode commands do not have a prefix. To go to the help page for the 4) Normal mode commands do not have a prefix. To go to the help page for the
"gt" command: > "gt" command: >
:help gt :help gt
@ -585,7 +585,7 @@ Summary: *help-summary* >
at: > at: >
:help pattern.txt :help pattern.txt
12) Registers always start with "quote". To find out about the special ":" 12) Registers always start with "quote". To find out about the special ":"
register: > register: >
:help quote: :help quote:
@ -604,7 +604,7 @@ Summary: *help-summary* >
< talks about the append Vim script function rather than how to append text < talks about the append Vim script function rather than how to append text
in the current buffer. in the current buffer.
14) Mappings are talked about in the help page :h |map.txt|. Use > 14) Mappings are talked about in the help page :h |map.txt|. Use >
:help mapmode-i :help mapmode-i
< to find out about the |:imap| command. Also use :map-topic < to find out about the |:imap| command. Also use :map-topic
to find out about certain subtopics particular for mappings. e.g: > to find out about certain subtopics particular for mappings. e.g: >
@ -640,7 +640,7 @@ Summary: *help-summary* >
friendly way. Start at |usr_toc.txt| to find the table of content (as you friendly way. Start at |usr_toc.txt| to find the table of content (as you
might have guessed): > might have guessed): >
:help usr_toc.txt :help usr_toc.txt
< Skim over the contents to find interesting topics. The "Digraphs" and < Skim over the contents to find interesting topics. The "Digraphs" and
"Entering special characters" items are in chapter 24, so to go to that "Entering special characters" items are in chapter 24, so to go to that
particular help page: > particular help page: >
:help usr_24.txt :help usr_24.txt

4
runtime/doc/usr_05.txt
View File

@ -1,4 +1,4 @@
*usr_05.txt* For Vim version 9.1. Last change: 2024 Jun 28 *usr_05.txt* For Vim version 9.1. Last change: 2024 Oct 05
VIM USER MANUAL - by Bram Moolenaar VIM USER MANUAL - by Bram Moolenaar
@ -446,7 +446,7 @@ This way you can use the plugin with the default key bindings `gc` and similar
for commenting (which is a well-established mapping in the Vim community). for commenting (which is a well-established mapping in the Vim community).
If you add this line to your vimrc file, then you need to restart Vim to have If you add this line to your vimrc file, then you need to restart Vim to have
the package loaded. Once the package is loaded, read about it at: > the package loaded. Once the package is loaded, read about it at: >
:h comment.txt :h comment.txt

8
runtime/doc/usr_06.txt
View File

@ -1,4 +1,4 @@
*usr_06.txt* For Vim version 9.1. Last change: 2021 Nov 07 *usr_06.txt* For Vim version 9.1. Last change: 2024 Oct 05
VIM USER MANUAL - by Bram Moolenaar VIM USER MANUAL - by Bram Moolenaar
@ -184,7 +184,7 @@ this command: >
:runtime syntax/colortest.vim :runtime syntax/colortest.vim
You will see text in various color combinations. You can check which ones are You will see text in various color combinations. You can check which ones are
readable and look nice. These aren't the only colors available to you though. readable and look nice. These aren't the only colors available to you though.
You can specify #rrggbb hex colors and you can define new names for hex You can specify #rrggbb hex colors and you can define new names for hex
colors in |v:colornames| like so: > colors in |v:colornames| like so: >
@ -196,7 +196,7 @@ to define these colors only when they do not exist: >
call extend(v:colornames, {'mine_red': '#aa0000'}, 'keep') call extend(v:colornames, {'mine_red': '#aa0000'}, 'keep')
This allows users of the color scheme to override the precise definition of This allows users of the color scheme to override the precise definition of
that color prior to loading your color scheme. For example, in a |.vimrc| that color prior to loading your color scheme. For example, in a |.vimrc|
file: > file: >
runtime colors/lists/css_colors.vim runtime colors/lists/css_colors.vim
@ -204,7 +204,7 @@ file: >
colorscheme yourscheme colorscheme yourscheme
As a color scheme author, you should be able to rely on some color names for As a color scheme author, you should be able to rely on some color names for
GUI colors. These are defined in `colors/lists/default.vim`. All such files GUI colors. These are defined in `colors/lists/default.vim`. All such files
found on the |'runtimepath'| are loaded each time the colorscheme command is found on the |'runtimepath'| are loaded each time the colorscheme command is
run. A canonical list is provided by the vim distribution, which should run. A canonical list is provided by the vim distribution, which should
include all X11 colors (previously defined in rgb.txt). include all X11 colors (previously defined in rgb.txt).

14
runtime/doc/usr_22.txt
View File

@ -1,4 +1,4 @@
*usr_22.txt* For Vim version 9.1. Last change: 2020 Mar 28 *usr_22.txt* For Vim version 9.1. Last change: 2024 Oct 05
VIM USER MANUAL - by Bram Moolenaar VIM USER MANUAL - by Bram Moolenaar
@ -41,8 +41,8 @@ check/ ~
Makefile ~ Makefile ~
autocmd.txt ~ autocmd.txt ~
change.txt ~ change.txt ~
eval.txt~ ~ eval.txt ~
filetype.txt~ ~ filetype.txt ~
help.txt.info ~ help.txt.info ~
You can see these items: You can see these items:
@ -214,11 +214,11 @@ directory, it will go back to using the shared directory.
TAB LOCAL DIRECTORY TAB LOCAL DIRECTORY
When you open a new tab page, it uses the directory of the window in the When you open a new tab page, it uses the directory of the window in the
previous tab page from which the new tab page was opened. You can change the previous tab page from which the new tab page was opened. You can change the
directory of the current tab page using the `:tcd` command. All the windows in directory of the current tab page using the `:tcd` command. All the windows in
a tab page share this directory except for windows with a window-local a tab page share this directory except for windows with a window-local
directory. Any new windows opened in this tab page will use this directory as directory. Any new windows opened in this tab page will use this directory as
the current working directory. Using a `:cd` command in a tab page will not the current working directory. Using a `:cd` command in a tab page will not
change the working directory of tab pages which have a tab local directory. change the working directory of tab pages which have a tab local directory.
When the global working directory is changed using the `:cd` command in a tab When the global working directory is changed using the `:cd` command in a tab
page, it will also change the current tab page working directory. page, it will also change the current tab page working directory.

6
runtime/doc/usr_41.txt
View File

@ -1,4 +1,4 @@
*usr_41.txt* For Vim version 9.1. Last change: 2024 Sep 23 *usr_41.txt* For Vim version 9.1. Last change: 2024 Oct 05
VIM USER MANUAL - by Bram Moolenaar VIM USER MANUAL - by Bram Moolenaar
@ -30,13 +30,13 @@ Table of contents: |usr_toc.txt|
*41.1* Introduction *vim-script-intro* *script* *41.1* Introduction *vim-script-intro* *script*
Let's start with some nomenclature. A Vim script is any file that Vim can Let's start with some nomenclature. A Vim script is any file that Vim can
interpret and execute. This includes files written in Vim's scripting language interpret and execute. This includes files written in Vim's scripting language
like for example .vim files or configuration files like .vimrc and .gvimrc. like for example .vim files or configuration files like .vimrc and .gvimrc.
These scripts may define functions, commands and settings that Vim uses to These scripts may define functions, commands and settings that Vim uses to
customize and extend its behavior. customize and extend its behavior.
With a slight abuse of nomenclature, we will use "Vim script" to refer to the With a slight abuse of nomenclature, we will use "Vim script" to refer to the
Vim scripting language throughout this documentation. This shorthand helps to Vim scripting language throughout this documentation. This shorthand helps to
streamline explanations and discussions about scripting with Vim. streamline explanations and discussions about scripting with Vim.
A Vim plugin is a collection of one or more Vim scripts, along with additional A Vim plugin is a collection of one or more Vim scripts, along with additional

4
runtime/doc/usr_43.txt
View File

@ -1,4 +1,4 @@
*usr_43.txt* For Vim version 9.1. Last change: 2015 Oct 23 *usr_43.txt* For Vim version 9.1. Last change: 2024 Oct 05
VIM USER MANUAL - by Bram Moolenaar VIM USER MANUAL - by Bram Moolenaar
@ -63,7 +63,7 @@ buffer. This works with any mapping command: ":map!", ":vmap", etc. The
The line to set b:undo_ftplugin is for when the filetype is set to another The line to set b:undo_ftplugin is for when the filetype is set to another
value. In that case you will want to undo your preferences. The value. In that case you will want to undo your preferences. The
b:undo_ftplugin variable is executed as a command. Watch out for characters b:undo_ftplugin variable is executed as a command. Watch out for characters
with a special meaning inside a string, such as a backslash. with a special meaning inside a string, such as a backslash.
You can find examples for filetype plugins in this directory: > You can find examples for filetype plugins in this directory: >