[vim/vim] Consider aliasing the "normal" build to "huge" (Issue #19567)

8 views
Skip to first unread message

Martin Tournoij

unread,
Mar 3, 2026, 9:49:03 AM (4 days ago) Mar 3
to vim/vim, Subscribed
arp242 created an issue (vim/vim#19567)

Here are the sizes of the normal and huge builds:

3,548K │ normal-O2
3,078K │ normal-Os

3,754K │ huge-O2     +206K
3,261K │ huge-Os     +172K

The huge build is about 200K larger, which is not that much on 3.5M. Even more so since most people will use the runtime files, which is 47M for a full install, or 27M if you remove translated docs and GUI stuff. Many additional features in the normal build require the runtime files.

I'm not really aware of any distro that ships separate "huge" and "normal" builds?

So I propose "normal" to include all the features currently in "huge" and "huge" is made an alias of "normal", similar to how "big" and "small" were aliased to "huge" and "tiny" a few years ago.

This would simplify the build selection a bit, can simplify the CI a bit, etc.


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

Christian Brabandt

unread,
Mar 5, 2026, 5:28:11 AM (2 days ago) Mar 5
to vim/vim, Subscribed
chrisbra left a comment (vim/vim#19567)

I'd say this is a resonable suggestion.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/19567/4004026911@github.com>

Ajit Thakkar

unread,
Mar 5, 2026, 7:27:35 AM (2 days ago) Mar 5
to vim_dev
Agreed. 

I used normal builds for 25 or more years. I switched to huge a few years ago when I noticed that the relative size difference had shrunk over the years.

If the builds are made identical, the default name should be normal rather than huge. 

Reply all
Reply to author
Forward
0 new messages