From: linhvng <linhvng@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: x-unikey-1.0.4
Date: Sun, 08 Aug 2021 16:54:58 +0200 [thread overview]
Message-ID: <20210808145458.cxDm39SpMCSFGsQ0kTaJ9NgG3TMWFaDd9lQ809jnhlw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32405@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
New comment by linhvng on void-packages repository
https://github.com/void-linux/void-packages/pull/32405#issuecomment-894809534
Comment:
> I've fixed the build for musl libc, however, it's hung when typing.
>
> Anyway, just out of curiosity, have you tried another input framework?
> I'm not really sure if it's worth to include this package for 1 user. :-p
I have tried fcitx but it puts my CPU to 100% for some reasons; I was using fluxbox and the tray icon for fcitx keeps flashing in the toolbar, which makes me suspect fluxbox might be trying to update/refresh the toolbar along with fcitx tray icon too much, thus pushing the CPU usage...
Your reason is totally understandable, it is a niche tool after all and the fact that it's broken on musl doesn't help either :sweat_smile:
I'm totally happy with keeping it in my forked repo and I'll try to bother you again when I get it to work on musl once I get my hand on more hardware :laughing: It's been a pleasant working with you :hugs:
next prev parent reply other threads:[~2021-08-08 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 7:55 [PR PATCH] " linhvng
2021-08-08 7:58 ` linhvng
2021-08-08 7:59 ` linhvng
2021-08-08 8:43 ` [PR REVIEW] " sgn
2021-08-08 8:52 ` sgn
2021-08-08 9:08 ` linhvng
2021-08-08 9:28 ` [PR PATCH] [Updated] " linhvng
2021-08-08 9:30 ` linhvng
2021-08-08 13:41 ` [PR PATCH] [Updated] " sgn
2021-08-08 13:44 ` sgn
2021-08-08 14:54 ` linhvng [this message]
2021-08-08 16:22 ` sgn
2021-08-08 17:45 ` linhvng
2021-08-09 2:24 ` [PR PATCH] [Closed]: " sgn
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210808145458.cxDm39SpMCSFGsQ0kTaJ9NgG3TMWFaDd9lQ809jnhlw@z \
--to=linhvng@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).