From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 38810@debbugs.gnu.org
Subject: [bug#38810] [PATCH] services: console-font: Update example with HDPI font suggestion.
Date: Mon, 30 Dec 2019 22:58:59 +0100 [thread overview]
Message-ID: <877e2d1nmk.fsf@gnu.org> (raw)
In-Reply-To: <87h81ihxt0.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Mon, 30 Dec 2019 12:12:27 +0100")
Hi!
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> Another HDPI-inspired patch; since Marrakech I finally have a readable
> console font, thanks to Bernhard M. Wiedemann.
:-)
> This solution enters the manual in a kind of tricksy way. More
> seriously, when updating the `guix system search console font' example
> output, I found that mingetty and login and ... entries to be missing.
> Is that a bug, or should the output be fixed? We could also change
> the example command to `guix search console', then those entries are
> present again.
Yeah, we should just change the example to “guix search console”.
>>From 1b0d736405354c2c1aeb7aee00e63307d956ceae Mon Sep 17 00:00:00 2001
> From: Jan Nieuwenhuizen <janneke@gnu.org>
> Date: Mon, 30 Dec 2019 11:56:58 +0100
> Subject: [PATCH] services: console-font: Update example with HDPI font
> suggestion.
>
> This solution was kindly provided by Bernard M. Wiedemann.
>
> * gnu/services/base.scm (console-font-service-type): Add ter132n (terminus 132
> nomal) font example, for HDPI displays.
> * doc/guix.texi (Invoking guix system): Update `guix system search console
> font' example output.
LGTM!
> +@cindex HDPI
Do people expect “HDPI” or “HiDPI”? Wikipedia says both:
<https://en.wikipedia.org/wiki/Pixel_density#Named_pixel_densities>.
Perhaps add two cindex entries then?
Thanks!
Ludo’.
next prev parent reply other threads:[~2019-12-30 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 11:12 [bug#38810] [PATCH] services: console-font: Update example with HDPI font suggestion Jan Nieuwenhuizen
2019-12-30 21:58 ` Ludovic Courtès [this message]
2019-12-30 22:40 ` bug#38810: " Jan Nieuwenhuizen
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=877e2d1nmk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38810@debbugs.gnu.org \
--cc=janneke@gnu.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).