Vim configure options

[chris@…]

A few points about configure options for Vim:

1. If I'm reading src/feature.h correctly, multibyte support should be enabled with the "normal" feature set, which is the default (--with-features=normal). Therefore, I believe --enable-multibyte is redundant.

2. Any reason why --with-features=huge isn't used? It builds just fine for me in a minimal LFS chroot setup; it doesn't try enabling support for X or other stuff that's not found there.

3. Is there any downside to using --enable-perlinterp? Perl is already installed in LFS anyway.

[bdubbs@…]

1. It looks like multibyte support is now built by default. Can we get someone who uses it to validate?

2. huge would include big. The features I see are:

'langmap' option. Only useful in a special language mode, e.g. Greek
'keymap' option.
Right-to-left editing/typing support
farsi Keymap support.
tag_binary
Cscope support.
'conceal' option.
+signs Allow signs to be displayed to the left of text lines.
+autochdir           'autochdir' option.
+profile             Profiling for functions and scripts.

I really think that if a user wants these, then they can add them themselves. To do it for everyone seems to be bloat to me.

3. Has anyone used perlinterp? Again, this feels like bloat. If it goes anywhere, I'd say it should go in BLFS.

[ken@…]

I've just started what might be a "throwaway" build, I'll try omitting --enable-multibyte.

[ken@…]

hexdump of text including multibyte chars

[ken@…]

Looks good to me. Attachment shows hexdump of lines of text in 'U+nnnn description X\n' format which I input in the console : everything beyond ASCII is multibyte (UTF-8), including the accents which have the same codepoints as in latin-1. Took me a while to find something using more than 2 bytes, and which is in my font, until I remembered Welsh accented letters.

[ken@…]

For points 2 and 3, I agree with Bruce. Looking around, I did not find any obvious usage for the perl interpreter. I'll remove --enable-multibyte, the rest can perhaps go in BLFS.

[ken@…]

Point 1. done in r10688.

Returning to the list in case there are any further thoughts on points 2 and 3.

[bdubbs@…]

Marking fixed for point 1.

Points 2 and 3 are wontfix.