Re: Are the --enable-hangulinput and --enable-xim confilct?

On Thu, Nov 21, 2019 at 4:47 PM Bram Moolenaar <Bram@moolenaar.net> wrote:
>
>
> Namsh wrote:
>
> > >> 2019-08-25 오후 2:25에 Hongyi Zhao 이(가) 쓴 글:
> > >>> Hi,
> > >>>
> > >>> I try to build vim with the --enable-hangulinput and --enable-xim
> > >>> confilct at the same time, but failed with error:
> > >>>
> > >>> -------------------------
> > >>> vim.h:1585:63: error: called object 'size_t' is not a function or
> > >>> function pointer
> > >>> #define STRNCMP(d, s, n) strncmp((char *)(d), (char *)(s), (size_t)(n))
> > >>> ^
> > >>> ex_docmd.c:8459:6: note: in expansion of macro 'STRNCMP'
> > >>> if (STRNCMP(arg, "FALLBACK ", 9) == 0)
> > >>> ^~~~~~~
> > >>> In file included from /usr/include/wchar.h:887:0,
> > >>> from spell.h:250,
> > >>> from vim.h:2110,
> > >>> from ex_docmd.c:14:
> > >>> /usr/include/x86_64-linux-gnu/bits/wchar2.h:507:20: note: declared here
> > >>> __fortify_function size_t
> > >>> ^~~~~~
> > >>> Makefile:3059: recipe for target 'objects/ex_docmd.o' failed
> > >>> make[1]: *** [objects/ex_docmd.o] Error 1
> > >>> make[1]: Leaving directory '/home/werner/software/editor/vim/vim.git/src'
> > >>> Makefile:26: recipe for target 'first' failed
> > >>> make: *** [first] Error 2
> > >>> -----------------------------
> > >>>
> > >>> Are these two options conflict?
> > >>
> > >> Regardless of compilation error, the hangulin feature is for
> > >> environments where XIM is not available.
> > >>
> > >> You can find next line with ':help hangul'.
> > >> ./configure --with-x --enable-multibyte --enable-hangulinput \
> > >> --disable-xim
> > >
> > > That's a bit of a disadvantage when someone tries to build a version
> > > that works with multiple languages. Can we make this a runtime choice
> > > instead of a compile time choice? No idea how much work that would be.
> >
> > Here is a minimal patch (no documentation, no indenting to minimize).
> > If vim supports both xim and hangulinpt and user set 'imdisable',
> > hangulinput feature is selected.
> >
> > I tested this patch by adding '--enable-xim --enable-hangulinput' to my
> > default configure option.
> > $ auto/configure --enable-perlinterp=no --disable-gpm
> > --enable-python3interp=dynamic --enable-tclinterp=no --enable-cscope
> > --with-features=huge --enable-terminal --enable-multibyte --enable-xim
> > --enable-hangulinput --prefix=/opt/local --with-x --enable-gui=gtk3
> >
> > While testing this patch, I noticed one glitch.
> > Though I set 'imdisable' in the vimrc and I confirmed the setting with
> > ':set imdisable?', when I typed S-Space for the first time, vim connects
> > to XIM. After that, go to english input mode and type S-Space again, vim
> > enters to hangulinput mode. My system environement may cause this glitch??
>
> Now that I try this patch I notice that hangulin.c doesn't build.
> Since nobody complained and this input method is unmaintained, let's
> just remove it.
>
> I hope someone can re-implement this for utf-8 encoding.

IIRC, +hangul_input was incompatible with GTK[1-3]. But don't take my
word for it, I don't speak Korean.

Best regards,
Tony.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CAJkCKXtTanRCNAozjEo%2BSeSa%3Db%3DobNbinUfr7t_8c_22FhQs4Q%40mail.gmail.com.