Commit: runtime(doc): clarify how setbufvar() handles window options

Christian Brabandt <[email protected]>
Newsgroups gmane.editors.vim.devel
Message-ID <[email protected]>
runtime(doc): clarify how setbufvar() handles window options

Commit: https://github.com/vim/vim/commit/76f1eed3a5f8fe12a7b01725a99c582a95e69000
Author: Hirohito Higashi <[email protected]>
Date:   Thu Aug 20 19:35:57 2026 +0000

    runtime(doc): clarify how setbufvar() handles window options
    
    related: https://github.com/vim/vim/issues/21089
    closes:  https://github.com/vim/vim/issues/21104
    
    Signed-off-by: Hirohito Higashi <[email protected]>
    Signed-off-by: Christian Brabandt <[email protected]>

diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt
index 737cac1fe..9effcec54 100644
--- a/runtime/doc/builtin.txt
+++ b/runtime/doc/builtin.txt
@@ -1,4 +1,4 @@
-*builtin.txt*	For Vim version 9.2.  Last change: 2026 Aug 18
+*builtin.txt*	For Vim version 9.2.  Last change: 2026 Aug 20
 
 
 		  VIM REFERENCE MANUAL	  by Bram Moolenaar
@@ -9984,9 +9984,13 @@ setbufline({buf}, {lnum}, {text})			*setbufline()*
 setbufvar({buf}, {varname}, {val})			*setbufvar()*
 		Set option or local variable {varname} in buffer {buf} to
 		{val}.
-		This also works for a global or local window option, but it
-		doesn't work for a global or local window variable.
-		For a local window option the global value is unchanged.
+		This also works for a global option or a window-local option,
+		but it doesn't work for a global or local window variable.  A
+		window-local option is set in a window of the current tab page
+		that displays {buf}, and the global value is unchanged.  When
+		no window in the current tab page displays {buf} the option is
+		not set and no error is given; use |setwinvar()| or
+		|win_execute()| for that.
 		For the use of {buf}, see |bufname()| above.
 		The {varname} argument is a string.
 		Note that the variable name without "b:" must be used.

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/vim_dev/E1wx8hD-00DzkS-Id%40256bit.org.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.