[vim/vim] fsync option cannot be set per buffer (PR #19019)

3 views
Skip to first unread message

glepnir

unread,
Dec 26, 2025, 4:44:36 AM (2 days ago) Dec 26
to vim/vim, Subscribed

Problem: 'fsync' option is global, cannot be customized per buffer
Solution: Make 'fsync' can local to buffer

relate neovim/neovim#36936


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

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

Commit Summary

  • 499e5a9 fsync option cannot be set per buffer

File Changes

(8 files)

Patch Links:


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/19019@github.com>

zeertzjq

unread,
Dec 26, 2025, 4:49:46 AM (2 days ago) Dec 26
to vim/vim, Subscribed
zeertzjq left a comment (vim/vim#19019)

Missing documentation update


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/19019/c3692603538@github.com>

glepnir

unread,
Dec 26, 2025, 4:52:19 AM (2 days ago) Dec 26
to vim/vim, Push

@glepnir pushed 1 commit.

  • b37f111 fsync option cannot be set per buffer


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/19019/before/499e5a91c94e31974ebcd5430a6ae6f626c024a7/after/b37f1113c30cddca2f4cbd5b5488bcc4a80a02bd@github.com>

Christian Brabandt

unread,
Dec 27, 2025, 9:21:06 AM (yesterday) Dec 27
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#19019)

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/19019/c3694007452@github.com>

Christian Brabandt

unread,
Dec 27, 2025, 9:34:17 AM (yesterday) Dec 27
to vim/vim, Subscribed

Closed #19019 via 4d5b303.


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/19019/issue_event/21765854275@github.com>

Reply all
Reply to author
Forward
0 new messages