From: mnipritom <firstname.lastname@example.org>
Subject: Re: Package request: `ibus-sunpinyin`
Date: Thu, 01 Sep 2022 21:56:42 +0200 [thread overview]
Message-ID: <20220901195642.uaUyHgCLWS6jkrwDPoM3eeAt3QW4lhejOAodGFx5dTY@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 698 bytes --]
New comment by mnipritom on void-packages repository
Hi @sgn sorry for the late reply.
At this moment, just making `sunpinyin` available, regardless of either backend would bring much convenience.
On a personal note, I have been using `ibus` for all my input methods almost a decade now, across multiple distributions without any major issues. And I'm confident I can't be the only one. Although, I would completely understand if you guys would like to prioritise `fcitx5` over `ibus` (or even `fcitx`), since `ibus` is an aging platform.
Thank you taking a look at this. Really appreciate it.
next prev parent reply other threads:[~2022-09-01 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 12:37 [ISSUE] Package request: mnipritom
2022-09-01 1:39 ` Package request: `ibus-sunpinyin` sgn
2022-09-01 19:56 ` mnipritom [this message]
2022-09-06 10:44 ` [ISSUE] [CLOSED] " sgn
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).