changeset 34223:89a385d68777

runtime(doc): style fixes in vim9.txt (#13918) Commit: https://github.com/vim/vim/commit/4d49643c3c8237db68f7717b3600459fad911291 Author: h_east <h.east.727@gmail.com> Date: Sat Jan 27 19:22:28 2024 +0900 runtime(doc): style fixes in vim9.txt (https://github.com/vim/vim/issues/13918) Remove backticks and a few other style fixes Signed-off-by: h-east <h.east.727@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
author Christian Brabandt <cb@256bit.org>
date Sat, 27 Jan 2024 11:30:07 +0100
parents a54012b82efe
children 753702283749
files runtime/doc/vim9.txt
diffstat 1 files changed, 8 insertions(+), 8 deletions(-) [+]
line wrap: on
line diff
--- a/runtime/doc/vim9.txt
+++ b/runtime/doc/vim9.txt
@@ -1265,7 +1265,7 @@ level.  They cannot be created in a func
 			yet.  This will report any errors found during
 			compilation.
 
-:defc[ompile] MyClass  Compile all methods in a class |class-compile|.
+:defc[ompile] MyClass	Compile all methods in a class. |class-compile|
 
 :defc[ompile] {func}
 :defc[ompile] debug {func}
@@ -1720,8 +1720,8 @@ an example for each category: >
 Vim does not have a familiar null value; it has various null_<type> predefined
 values, for example |null_string|, |null_list|, |null_job|. Primitives do not
 have a null_<type>. The typical use cases for null_<type> are:
-- to `clear a variable` and release its resources;
-- as a `default for a parameter` in a function definition, see |null-compare|.
+- to clear a variable and release its resources;
+- as a default for a parameter in a function definition, see |null-compare|.
 
 For a specialized variable, like `job`, null_<type> is used to clear the
 resources. For a container variable, resources can also be cleared by
@@ -1773,7 +1773,7 @@ an empty container, do not use null_<typ
 	F(null_list)	# output: "null"
 	F([])		# output: "not null, empty"
 	F([''])		# output: "not null, not empty"
-The above function takes a `list of strings` and reports on it.
+The above function takes a list of strings and reports on it.
 Change the above function signature to accept different types of arguments: >
 	def F(arg: list<any> = null_list)   # any type of list
 	def F(arg: any = null)		    # any type
@@ -1791,18 +1791,18 @@ with vim9 null semantics, the programmer
 comparisons and/or other situations.
 
 Elsewhere in the documentation it says:
-	Quite often a null value is handled the same as an
-	empty value, but not always
+	Quite often a null value is handled the same as an empty value, but
+	not always
 Here's an example: >
 	vim9script
 	var s1: list<string>
 	var s2: list<string> = null_list
 	echo s1		    # output: "[]"
 	echo s2		    # output: "[]"
-	
+
 	echo s1 + ['a']     # output: "['a']"
 	echo s2 + ['a']     # output: "['a']"
-	
+
 	echo s1->add('a')   # output: "['a']"
 	echo s2->add('a')   # E1130: Can not add to null list
 <