Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"
Hi,
I have no idea which is better but here is a technical implementation idea.
Add one optional commented out parameter to /etc/default/im-config
, e.g.: FCITX_IM_ENV
Make im-config use it to override internal default.
So anyone got in to trouble can work around situation easily.
Add this fact to README.Debian...
On Mon, 2021-06-07 at 14:51 +0800, Shengjing Zhu wrote:
> On Mon, Jun 07, 2021 at 08:04:14AM +0200, Gunnar Hjalmarsson wrote:
> > On 2021-06-07 07:08, Shengjing Zhu wrote:
> > > On Sat, Jun 05, 2021 at 11:58:14PM +0200, Gunnar Hjalmarsson wrote:
> > > > What's the conclusion then as regards this bug? Is it time to
> > > > change to "fcitx" in im-config in unstable (and somehow also in
> > > > bullseye) without worrying about users who have both fcitx 4 and
> > > > fcitx 5 installed?
> > >
> > > We eventually need to align with upstream for the IM_MODULE env. But
> > > I'm not sure what should be done before bullseye release.
> >
> > How about uploading the "fcitx5" -> "fcitx" change to experimental for now?
> > And possibly upload to bullseye soon after the release of Debian 11.
> >
>
> Yes, please. And after release, the change could be updated in unstable ASAP
> to get more feedback from users.
>
> > FWIW I have tested to have both fcitx 4 and fcitx 5 installed, and didn't
> > notice any issues when running fcitx 5 with IM_MODULE=fcitx.
> >
> > --
> > Gunnar
>
Reply to: