From: nihilismus <nihilismus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] font-tamzen: cannot load font.
Date: Tue, 01 Sep 2020 19:25:29 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24590@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
New issue by nihilismus on void-packages repository
https://github.com/void-linux/void-packages/issues/24590
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
`Void 5.6.19_1 x86_64 GenuineIntel uptodate rFFFFFF`
* package:
`font-tamzen-1.11.4_1`
### Expected behavior
`xterm` should use the `tamzen` bitmap font when one executes `xterm -fn '-*-tamzen-medium-*-*-*-16-*-*-*-*-*-*-*'`,
### Actual behavior
`xterm` does not use the `tamzen` bitmap font and prints the message: `xterm: cannot load font "-*-tamzen-medium-*-*-*-16-*-*-*-*-*-*-*"`
### Steps to reproduce the behavior
Execute `xterm -fn '-*-tamzen-medium-*-*-*-16-*-*-*-*-*-*-*'` in a terminal.
### Notes
- `tamzen` bitmap font is installed inside `/usr/share/fonts/misc`
- `/usr/share/fonts/misc` is not part of the *font path* when querying it with `xset q | grep -A 1 'Font Path:'`.
- A workaround is to add `/usr/share/fonts/misc` to the *font path* with `xset fp+ /usr/share/fonts/misc`.
- A solution to this package would be to move the `tamzen` bitmap font from `/usr/share/fonts/misc` to `/usr/share/fonts/X11/misc` since `terminus-font` (another bitmap font) does not present this issue with `xterm` and is installed inside this last directory.
next reply other threads:[~2020-09-01 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 17:25 nihilismus [this message]
2020-09-28 8:50 ` devvesa
2020-09-28 8:54 ` devvesa
2022-04-19 2:12 ` github-actions
2022-05-03 2:13 ` [ISSUE] [CLOSED] " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24590@inbox.vuxu.org \
--to=nihilismus@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).