From: John Soo <jsoo1@asu.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36014@debbugs.gnu.org
Subject: bug#36014: [PATCH] Attempt to use console-fonts not provided by kbd if they are installed
Date: Fri, 12 Jul 2019 09:05:45 -0700 [thread overview]
Message-ID: <D71D5F21-02A9-41C2-8421-2115C3106E97@asu.edu> (raw)
In-Reply-To: <87pnmgpa8q.fsf@gnu.org>
Ok so I tried your suggestion and it works! I’m so surprised but I think I’ll update the docs to reflect this possibility instead of the current patch.
- John
> On Jul 11, 2019, at 1:49 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hi John,
>
> John Soo <jsoo1@asu.edu> skribis:
>
>> I looked hard at a nicer way to provide a flag to start kbd pointing to a
>> directory or file. There is a flag to point to a file for a font which
>> could be nice. However setfont also prioritizes the current directory over
>> the kbd directory. The following patch attempts to chdir to a directory
>> where more console fonts may be installed.
>
> What about doing something like this in your config
>
> (console-font-service "tty1"
> (file-append some-font-package
> "/share/consolefonts/whatever"))
>
> ?
>
> Does it work for you?
>
> This approach has the advantage that the service doesn’t need to be
> changed, and it doesn’t need to change the current directory of PID 1
> either.
>
> Thanks,
> Ludo’.
next prev parent reply other threads:[~2019-07-12 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 19:21 bug#36014: Allow console-font service to use fonts other than those packaged with kbd John Soo
2019-07-11 14:27 ` bug#36014: [PATCH] Attempt to use console-fonts not provided by kbd if they are installed John Soo
2019-07-11 20:49 ` Ludovic Courtès
2019-07-11 22:29 ` John Soo
2019-07-12 16:05 ` John Soo [this message]
2019-07-12 20:40 ` Ludovic Courtès
2019-08-16 18:01 ` John Soo
2019-08-22 16:00 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D71D5F21-02A9-41C2-8421-2115C3106E97@asu.edu \
--to=jsoo1@asu.edu \
--cc=36014@debbugs.gnu.org \
--cc=ludo@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 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.