From: Akib Azmain Turja <akib@disroot.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: UTF-8 progress bar
Date: Sun, 29 Jan 2023 10:21:23 +0600 [thread overview]
Message-ID: <87bkmim0n0.fsf@disroot.org> (raw)
In-Reply-To: <20230128141735.33077405@sybil.lepiller.eu> (Julien Lepiller's message of "Sat, 28 Jan 2023 14:17:35 +0100")
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
Julien Lepiller <julien@lepiller.eu> writes:
> Hi Guix!
>
> I have a patch waiting (https://issues.guix.gnu.org/59975) that will
> change progress bars to use some unicode characters. I think they look
> better, but I'm a bit afraid they might not look right on some config,
> so I'd like to know if your terminal is able to show these characters:
>
> "▏▎▍▌▋▊▉█▏▕"
>
> If you are not using a unicode locale, this change will not affect you
> as guix will fallback to the ascii style. If your terminal can't show
> these characters and you have a UTF-8 locale (you'd run echo $LANG to
> know that), please report your config (name of terminal app, locale,
> fonts, …)!
>
They won't work in Linux (kernel) console, despite $LANG="en_US.utf8".
--
Akib Azmain Turja, GPG key: 70018CE5819F17A3BBA666AFE74F0EFA922AE7F5
Fediverse: akib@hostux.social
Codeberg: akib
emailselfdefense.fsf.org | "Nothing can be secure without encryption."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2023-01-29 4:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 13:17 UTF-8 progress bar Julien Lepiller
2023-01-28 13:49 ` Maxime Devos
2023-01-28 17:34 ` Kaelyn
2023-01-29 4:21 ` Akib Azmain Turja [this message]
2023-01-30 22:02 ` Ludovic Courtès
2023-01-30 23:34 ` bokr
2023-01-31 0:26 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-01-31 10:55 ` Akib Azmain Turja
2023-01-31 13:03 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
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=87bkmim0n0.fsf@disroot.org \
--to=akib@disroot.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.