diff options
| author | zeertzjq <zeertzjq@outlook.com> | 2024-04-24 16:20:19 +0800 |
|---|---|---|
| committer | zeertzjq <zeertzjq@outlook.com> | 2025-02-28 18:21:08 +0800 |
| commit | 6750d00fe96a04ab19cfc55fb406f6b40dbf970f (patch) | |
| tree | 1cce38d22bbaccd9d250db074d7c3ba236526ce2 /runtime | |
| parent | a3a9f86d4a11029542a94b00044b5a181a68c9cd (diff) | |
| download | rneovim-6750d00fe96a04ab19cfc55fb406f6b40dbf970f.tar.gz rneovim-6750d00fe96a04ab19cfc55fb406f6b40dbf970f.tar.bz2 rneovim-6750d00fe96a04ab19cfc55fb406f6b40dbf970f.zip | |
vim-patch:8.2.4603: sourcing buffer lines is too complicated
Problem: Sourcing buffer lines is too complicated.
Solution: Simplify the code. Make it possible to source Vim9 script lines.
(Yegappan Lakshmanan, closes vim/vim#9974)
https://github.com/vim/vim/commit/85b43c6cb7d56919e245622f4e42db6d8bee4194
This commit changes the behavior of sourcing buffer lines to always have
a script ID, although sourcing the same buffer always produces the same
script ID.
vim-patch:9.1.0372: Calling CLEAR_FIELD() on the same struct twice
Problem: Calling CLEAR_FIELD() on the same struct twice.
Solution: Remove the second CLEAR_FIELD(). Move the assignment of
cookie.sourceing_lnum (zeertzjq).
closes: vim/vim#14627
https://github.com/vim/vim/commit/f68517c1671dfedcc1555da50bc0b3de6d2842f6
Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
Diffstat (limited to 'runtime')
| -rw-r--r-- | runtime/doc/repeat.txt | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt index 4c95066998..d653a8f9fd 100644 --- a/runtime/doc/repeat.txt +++ b/runtime/doc/repeat.txt @@ -201,7 +201,9 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|. 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. + 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. *:source!* :so[urce]! {file} @@ -394,10 +396,10 @@ An alternative is to put the commands in a file, and execute them with the ':source!' command. Useful for long command sequences. Can be combined with the ':map' command to put complicated commands under a function key. -The ':source' command reads Ex commands from a file line by line. You will -have to type any needed keyboard input. The ':source!' command reads from a -script file character by character, interpreting each character as if you -typed it. +The ':source' command reads Ex commands from a file or a buffer line by line. +You will have to type any needed keyboard input. The ':source!' command reads +from a script file character by character, interpreting each character as if +you typed it. Example: When you give the ":!ls" command you get the |hit-enter| prompt. If you ':source' a file with the line "!ls" in it, you will have to type the |