[vim/vim] runtime: Remove 'formatprg' from ftplugins (PR #19108)

dkearns

unread,

Jan 6, 2026, 10:08:47 AM (3 days ago) Jan 6

to vim/vim, Subscribed

Effective use of 'formatprg' requires both an understanding of the
specific capabilities of the formatting tool and Vim's formatting
commands. This is overly burdensome for some users.

Rather than address each complaint on a filetype by filetype basis,
remove 'formatprg' settings from all ftplugins.

It is expected that formatter plugins will be available in the near
future as a better solution. See #17145 (Add "formatter" feature using
"compiler" as a template).

See: #18650 (rust.vim: stop setting formatprg to rustfmt)

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

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

Commit Summary

866647e runtime: Remove 'formatprg' from ftplugins

File Changes

(6 files)

Patch Links:

—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.

dkearns

unread,

Jan 6, 2026, 10:12:22 AM (3 days ago) Jan 6

to vim/vim, Push

@dkearns pushed 1 commit.

f0aad7f runtime: Remove 'formatprg' from ftplugins

—
View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.

D. Ben Knoble

unread,

Jan 7, 2026, 4:00:55 PM (2 days ago) Jan 7

to vim/vim, Subscribed

benknoble left a comment (vim/vim#19108)

Racket: I'm willing to accept this change in Vim's default ftplugins, but I'll probably keep it upstream for now. When the newer mechanism is available, I'll convert. That said, is #17145 still moving?

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

You are receiving this because you are subscribed to this thread.

Enno

unread,

Jan 8, 2026, 2:45:44 PM (yesterday) Jan 8

to vim/vim, Subscribed

Konfekt left a comment (vim/vim#19108)

Effective use of 'formatprg' requires both an understanding of the
specific capabilities of the formatting tool and Vim's formatting
commands. This is overly burdensome for some users.

Those who prefer predictable behavior use gw instead, which is almost always what was intended when gq is used. The latter is likely just better known as it came first. Without formatprg/expr, what's the value provided by gq over gw ? So I'd rather argue for the opposite coupled with a recommendation of gw

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

You are receiving this because you are subscribed to this thread.

Phạm Bình An

unread,

Jan 8, 2026, 7:50:29 PM (22 hours ago) Jan 8

to vim/vim, Subscribed

brianhuster left a comment (vim/vim#19108)

While I think that Vim shouldn't have to chase the ecosystem (development tools) of every language, hence Vim shouldn't set formatprg by default for any languages without one yet, wouldn't this PR be a breaking change? People already familiar with formatprg of those filetypes will suddenly be presented with something as dumb as gw.

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

You are receiving this because you are subscribed to this thread.

dkearns

unread,

Jan 8, 2026, 9:27:31 PM (20 hours ago) Jan 8

to vim/vim, Subscribed

dkearns left a comment (vim/vim#19108)

This PR is simply following through on the decision already made in the referenced PR (see #18650 (rust.vim: stop setting formatprg to rustfmt)).

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

You are receiving this because you are subscribed to this thread.

Christian Brabandt

unread,

1:29 PM (4 hours ago) 1:29 PM

to vim/vim, Subscribed

chrisbra left a comment (vim/vim#19108)

I agree with this approach in principle. However to not surprise users too much, let's merge this after the release.