From: Vagrant Cascadian <vagrant@debian.org>
To: Efraim Flashner <efraim@flashner.co.il>,
adriano <randomlooser@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: glibc-locales
Date: Mon, 31 Jan 2022 10:03:21 -0800 [thread overview]
Message-ID: <878ruvdbpy.fsf@contorta> (raw)
In-Reply-To: <Yfeh2nS2sIDHWTG4@3900XT>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
On 2022-01-31, Efraim Flashner wrote:
> On Mon, Jan 31, 2022 at 08:40:27AM +0100, adriano wrote:
>> Running Guix the package manager on Ubuntu 21.10 for the first time
>> after some years
>>
>> I installed glibc-locales according the the indications in
>> "Applications Setup" in the manual
>>
>> BUT
>>
>> runnig Emacs in the terminal and then quitting it, I get
>>
>> ~$ emacs
>>
>> (process:55779): Gtk-WARNING **: 08:13:44.529: Locale not supported by
>> C library.
>> Using the fallback 'C' locale.
>> Gtk-Message: 08:13:44.641: Failed to load module "canberra-gtk-module"
>> Gtk-Message: 08:13:44.642: Failed to load module "canberra-gtk-module"
>>
>>
>> We'll get to the canberra thing later
>>
>> As for the C locale, what's wrong with that ?
> 'C' isn't actually a locale in glibc but is something added by Debian.
'C' is definitely a default locale in glibc, but 'C.UTF-8' is added by
various distros. Ubuntu might only support UTF-8 locales...
> You'll want to try one of the other locales while running programs from
> Guix. You can set it with 'LOCALE=EN_US.UTF-8 emacs' and it'll only take
> effect for that command.
But yeah, you want a UTF-8 locale, at least; there is not "generic"
upstream UTF-8 locale, and guix just uses the upstream locales from
glibc.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-01-31 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 7:40 glibc-locales adriano
2022-01-31 8:46 ` glibc-locales Efraim Flashner
2022-01-31 18:03 ` Vagrant Cascadian [this message]
2022-01-31 18:37 ` glibc-locales adriano
2022-01-31 20:02 ` glibc-locales Vagrant Cascadian
2022-01-31 20:37 ` glibc-locales adriano
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ruvdbpy.fsf@contorta \
--to=vagrant@debian.org \
--cc=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=randomlooser@riseup.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).