On 2022/06/08 14:12, Yifei Zhan wrote: > On 22/06/08 12:28PM, Omar Polo wrote: > > Yifei Zhan <openbsd@zhan.science> wrote: > > > On 22/06/08 09:56AM, Omar Polo wrote: > > > > Yifei Zhan <openbsd@zhan.science> wrote: > > > > > [...] > > > > > +To use fcitx with kitty terminal, also add the following line: > > > > > + > > > > > +export GLFW_IM_MODULE=ibus > > > > > > > > I guess this is not needed only for kitty, but also for other > > > > applications using GLFW? > > > > > > I'm not sure, I can't validate as I'm not aware of any other > > > application requiring this variable despite some grepping in the ports > > > tree/searching on the web. However, if that's the case, I'm not > > > against changing it :) > > > > despite the name, it seems that only kitty uses that environment > > variable. (verified also with debian codesearch) > > > > https://github.com/kovidgoyal/kitty/issues/3206#issuecomment-753740868 > > > > a bit sad that this is not even mentioned in the manpage. > > > > in theory the best place to document this would be the kitty port, but > > since we're already documenting the other toolkit-dependent env vars in > > the fcitx readme adding a note about kitty seems the easier and less > > intrusive option. (even thought patching kitty' manpage and upstreaming > > the diff is also an option.) > > Thanks for checking! I prefer to just put it as a sidenote on fcitx's > README now, because I don't use kitty often enough to maintain a > patch/upstreaming it, also I'm trying to maintain a single source of > truth for IME config as having those details spread across different > ports can be hard for me to keep track of. >
Makes sense, though I note this information is on upstream's wiki https://www.fcitx-im.org/wiki/Setup_Fcitx_5 which might be worth referring to?
