Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2021-06-08 Thread Gunnar Hjalmarsson
On 2021-06-07 08:51, Shengjing Zhu wrote: On Mon, Jun 07, 2021 at 08:04:14AM +0200, Gunnar Hjalmarsson wrote: 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 cha

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2021-06-07 Thread Gunnar Hjalmarsson
Hi Osamu! On 2021-06-07 09:38, Osamu Aoki wrote: 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 troubl

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2021-06-07 Thread Osamu Aoki
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 fa

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2021-06-06 Thread Shengjing Zhu
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 unstabl

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2021-06-06 Thread Gunnar Hjalmarsson
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

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2021-06-06 Thread Shengjing Zhu
On Sat, Jun 05, 2021 at 11:58:14PM +0200, Gunnar Hjalmarsson wrote: > On 2021-06-05 22:51, Shengjing Zhu wrote: > > Situation has changed since fcitx5 5.0.4, which includes a compatible > > frontend for fcitx4 module. > > https://salsa.debian.org/input-method-team/fcitx5/-/commit/7780c8f7f9bcde2fcf

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2021-06-05 Thread Gunnar Hjalmarsson
On 2021-06-05 22:51, Shengjing Zhu wrote: Situation has changed since fcitx5 5.0.4, which includes a compatible frontend for fcitx4 module. https://salsa.debian.org/input-method-team/fcitx5/-/commit/7780c8f7f9bcde2fcff6ae7fc3ce5ab2c40ebe63 The origin purpose is to support property software which

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2021-06-05 Thread Shengjing Zhu
On Sun, Jun 6, 2021 at 4:51 AM Shengjing Zhu wrote: > > On Sun, Jun 6, 2021 at 4:06 AM Gunnar Hjalmarsson wrote: > > > > If both fcitx 4 and fcitx 5 are installed, the IM_MODULE value "fcitx" > > would result in a fcitx 4 im module being loaded when using fcitx 5. We > > have so far assumed that

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2021-06-05 Thread Shengjing Zhu
On Sun, Jun 6, 2021 at 4:06 AM Gunnar Hjalmarsson wrote: > > If both fcitx 4 and fcitx 5 are installed, the IM_MODULE value "fcitx" > would result in a fcitx 4 im module being loaded when using fcitx 5. We > have so far assumed that that would be a problem, if I understand it > correctly, and that

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2021-06-05 Thread Gunnar Hjalmarsson
If both fcitx 4 and fcitx 5 are installed, the IM_MODULE value "fcitx" would result in a fcitx 4 im module being loaded when using fcitx 5. We have so far assumed that that would be a problem, if I understand it correctly, and that's the reason why the fix of this bug was postponed. Question:

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2020-12-15 Thread Shengjing Zhu
On Tue, Dec 15, 2020 at 9:24 PM Gunnar Hjalmarsson wrote: > > On 2020-12-12 15:19, Gunnar Hjalmarsson wrote: > > On 2020-12-12 14:48, Shengjing Zhu wrote: > >> According to > >> https://github.com/fcitx/fcitx5/pull/161#issuecomment-735234080 > >> Upstream wants people to use "fcitx" in *_IM_MODULE

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2020-12-15 Thread Gunnar Hjalmarsson
On 2020-12-12 15:19, Gunnar Hjalmarsson wrote: On 2020-12-12 14:48, Shengjing Zhu wrote: According to https://github.com/fcitx/fcitx5/pull/161#issuecomment-735234080 Upstream wants people to use "fcitx" in *_IM_MODULE environment. This was commit by Boyuan Yang a while ago: https://salsa.deb

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2020-12-12 Thread Gunnar Hjalmarsson
On 2020-12-12 14:48, Shengjing Zhu wrote: According to https://github.com/fcitx/fcitx5/pull/161#issuecomment-735234080 Upstream wants people to use "fcitx" in *_IM_MODULE environment. This was commit by Boyuan Yang a while ago: https://salsa.debian.org/input-method-team/im-config/-/commit/0dc2

Bug#977203: IM_MODULE env for fcitx5 should be "fcitx"

2020-12-12 Thread Shengjing Zhu
Package: im-config Severity: normal X-Debbugs-Cc: z...@debian.org According to https://github.com/fcitx/fcitx5/pull/161#issuecomment-735234080 Upstream wants people to use "fcitx" in *_IM_MODULE environment. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: