[vim/vim] docs(if_pyth): clarify vim.eval behavior with Vim special variables (PR #19157)

[Phạm Bình An]

Problem:

• The behavior of vim.eval with Vim special variables is not clearly documented. It is (partly) the reason why Nvim Python's vim.eval gives different output when evaluating v:true and v:false

Solution:

• Clearly document it.

---

You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/19157

Commit Summary

• 11a0d71 docs(if_pyth): clarify vim.eval behavior with Vim special variables

File Changes

(1 file)

• M runtime/doc/if_pyth.txt (8)

Patch Links:

• https://github.com/vim/vim/pull/19157.patch
• https://github.com/vim/vim/pull/19157.diff

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19157@github.com>

[Phạm Bình An]

brianhuster left a comment (vim/vim#19157)

I just realize that vim.eval("function('input')") returns None instead of a funcref. So I'm not sure if the fact that v:null and v:none are evaluated to Python None is intended or just "they are not supported, so we throw None"

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19157/c3735188660@github.com>

[Christian Brabandt]

chrisbra left a comment (vim/vim#19157)

Yeah, not sure either, but the doc update is good nevertheless, thanks

—
Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19157/c3735252377@github.com>

[Christian Brabandt]

Closed #19157 via 1e54023.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19157/issue_event/21973693869@github.com>