From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30505@debbugs.gnu.org
Subject: bug#30505: Starting console/terminal Unicode support
Date: Mon, 26 Feb 2018 18:09:53 +0100 [thread overview]
Message-ID: <87sh9nvfry.fsf@gnu.org> (raw)
In-Reply-To: <20180225135704.3c437152@scratchpost.org> (Danny Milosavljevic's message of "Sun, 25 Feb 2018 13:57:04 +0100")
Hey,
Danny Milosavljevic <dannym@scratchpost.org> skribis:
>> Usually I'm not a fan of overriding user settings (in this case the kernel
>> command line) but in this case it's OK since the rest of the system at least
>> can be sure that we have UTF-8 VTs.
>
> Aha, the gnu/services/base.scm tries to make sure that an UTF-8 aware unicode
> font is already loaded before switching the tty to UTF-8. We would have to
> set default_utf8 earlier (before even the vt is activated), otherwise the
> setting wouldn't be copied to the new terminal.
You’re talking about %default-console-font? What does that change?
I’m lost. :-)
We have the following options:
1. status quo, i.e., tcsetattr without %G in the ‘term-ttyN’ services;
2. remove the tcsetattr call, write “1” to
/sys/module/vt/parameters/default_utf8;
3. do nothing (no tcsetattr, no /sys, no %G).
It seems that systemd does everything: %G, tcsetattr, and /sys.
What do we do now?
Ludo’.
next prev parent reply other threads:[~2018-02-26 17:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 0:01 bug#30505: marionette/virtio-console issues lead to test failures Ludovic Courtès
2018-02-18 10:48 ` Danny Milosavljevic
2018-02-19 15:54 ` Ludovic Courtès
2018-02-19 17:08 ` Danny Milosavljevic
2018-02-19 20:35 ` Ludovic Courtès
2018-02-19 22:35 ` Danny Milosavljevic
2018-02-21 22:21 ` bug#30505: Starting console/terminal Unicode support Ludovic Courtès
2018-02-21 23:01 ` Danny Milosavljevic
2018-02-23 21:41 ` Ludovic Courtès
2018-02-25 12:31 ` Danny Milosavljevic
2018-02-25 12:57 ` Danny Milosavljevic
2018-02-26 17:09 ` Ludovic Courtès [this message]
2018-02-26 22:23 ` Danny Milosavljevic
2018-02-27 9:25 ` Ludovic Courtès
2018-03-15 10:41 ` Ludovic Courtès
2018-02-19 21:53 ` bug#30505: marionette/virtio-console issues lead to test failures Ludovic Courtès
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=87sh9nvfry.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30505@debbugs.gnu.org \
--cc=dannym@scratchpost.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).