fix(lua): wrong script context for option set by func from nvim_exec2 (#32659)

Problem:  Wrong script context for option set by function defined by
          nvim_exec2 in a Lua script.
Solution: Call nlua_set_sctx() after adding SOURCING_LNUM and always set
          sc_lnum for a Lua script.

This is a bug discovered when testing #28486. Not sure if this actually
happens in practice, but it's easy to fix and required for #28486.
This commit is contained in:
zeertzjq
2025-02-27 21:49:57 +08:00
committed by GitHub
parent f25dd7a8d5
commit 89d6d6f25c
3 changed files with 37 additions and 7 deletions

View File

@@ -2106,12 +2106,20 @@ bool nlua_execute_on_key(int c, char *typed_buf)
return discard;
}
// Sets the editor "script context" during Lua execution. Used by :verbose.
// @param[out] current
/// Sets the editor "script context" during Lua execution. Used by :verbose.
/// @param[out] current
void nlua_set_sctx(sctx_T *current)
{
if (p_verbose <= 0 || (current->sc_sid > 0 && current->sc_lnum > 0)
|| !script_is_lua(current->sc_sid)) {
if (!script_is_lua(current->sc_sid)) {
return;
}
// This function is called after adding SOURCING_LNUM to sc_lnum.
// SOURCING_LNUM can sometimes be non-zero (e.g. with ETYPE_UFUNC),
// but it's unrelated to the line number in Lua scripts.
current->sc_lnum = 0;
if (p_verbose <= 0) {
return;
}
lua_State *const lstate = global_lstate;