From: jhe2 <jhe2@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: gomuks-0.2.2
Date: Fri, 09 Apr 2021 12:20:02 +0200 [thread overview]
Message-ID: <20210409102002.a2xnHmPmANco71nsinMkTmK0mV3BdToGkC8KAzsC6XI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27721@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
New comment by jhe2 on void-packages repository
https://github.com/void-linux/void-packages/pull/27721#issuecomment-816582503
Comment:
The tmux issue is caused by gomuks deciding instead of using what's in the TERM environment variable ("screen") to change it to "tmux" internally when the TMUX environment variable is found. On Void the problem could be mitigated by including a tmux entry for the terminfo database, although I think the proper way of solving this would be to simply respect the TERM setting and not use something different instead. Of course having the tmux terminfo on Void when tmux is installed might still be desirable.
I've also commented on the bug mentioned above ( https://github.com/tulir/gomuks/issues/250 ) and sent a pull request to fix that issue.
next prev parent reply other threads:[~2021-04-09 10:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 20:47 [PR PATCH] " FollieHiyuki
2021-01-08 23:03 ` kawaiiamber
2021-01-08 23:38 ` [PR PATCH] [Updated] " FollieHiyuki
2021-01-08 23:39 ` FollieHiyuki
2021-01-08 23:42 ` FollieHiyuki
2021-01-14 21:41 ` kawaiiamber
2021-01-14 23:30 ` [PR REVIEW] " ericonr
2021-01-15 6:06 ` [PR PATCH] [Updated] " FollieHiyuki
2021-01-15 6:07 ` [PR REVIEW] " FollieHiyuki
2021-01-15 18:43 ` ericonr
2021-01-15 18:43 ` ericonr
2021-01-15 18:43 ` ericonr
2021-01-15 19:24 ` FollieHiyuki
2021-01-15 19:40 ` FollieHiyuki
2021-01-15 21:54 ` ericonr
2021-01-15 22:15 ` ericonr
2021-01-16 5:53 ` FollieHiyuki
2021-01-16 8:05 ` travankor
2021-01-16 8:06 ` travankor
2021-01-16 8:07 ` kawaiiamber
2021-01-16 12:53 ` ericonr
2021-01-16 13:35 ` FollieHiyuki
2021-02-19 17:13 ` [PR PATCH] [Updated] [WIP] " FollieHiyuki
2021-02-19 17:16 ` FollieHiyuki
2021-02-19 17:32 ` kawaiiamber
2021-02-19 17:41 ` FollieHiyuki
2021-02-19 17:44 ` kawaiiamber
2021-02-19 17:55 ` kawaiiamber
2021-04-09 10:20 ` jhe2 [this message]
2021-04-09 10:30 ` jhe2
2021-10-18 21:45 ` ElDifinitivo
2021-10-24 16:13 ` ericonr
2021-12-07 22:31 ` motorto
2021-12-08 1:41 ` ericonr
2021-12-08 1:41 ` ericonr
2021-12-08 9:27 ` motorto
2022-05-02 2:15 ` github-actions
2022-05-17 2:13 ` [PR PATCH] [Closed]: " github-actions
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=20210409102002.a2xnHmPmANco71nsinMkTmK0mV3BdToGkC8KAzsC6XI@z \
--to=jhe2@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).