vim-patch:8.2.4607: sourcing buffer lines may lead to errors for conflicts

Problem:    Sourcing buffer lines may lead to errors for conflicts.
Solution:   Add the ++clear argument. (Yegappan Lakshmanan, closes vim/vim#9991)

https://github.com/vim/vim/commit/35dc17634dd6da5b90bd1b0160c4ed9e394f4b87

Documentation changes only. Vim9script is N/A.
Cherry-pick another documentation change for :source from latest Vim.

Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>

1 files changed, 9 insertions, 7 deletions

diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt
index d653a8f9fd..158ea6a4a1 100644
--- a/runtime/doc/repeat.txt
+++ b/runtime/doc/repeat.txt
@@ -197,13 +197,15 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|.
 			Triggers the |SourcePre| autocommand.
 
 :[range]so[urce]	Read Ex commands or Lua code from the [range] of lines
-			in the current buffer.  The buffer is treated as Lua
-			code if 'filetype' is "lua" or its filename ends with
-			".lua".  When sourcing commands or Lua code from the
-			current buffer, the same script-ID |<SID>| is used
-			even if the buffer is sourced multiple times. If a
-			buffer is sourced more than once, then the functions
-			in the buffer are redefined again.
+			in the current buffer.  When [range] is omitted read
+			all lines.  The buffer is treated as Lua code if its
+			'filetype' is "lua" or its filename ends with ".lua".
+
+			When sourcing commands or Lua code from the current
+			buffer, the same script-ID |<SID>| is used even if the
+			buffer is sourced multiple times. If a buffer is
+			sourced more than once, then the functions in the
+			buffer are defined again.
 
 							*:source!*
 :so[urce]! {file}