From: Eric Bavier <bavier@posteo.net>
To: 58451-done@debbugs.gnu.org
Subject: bug#58451: cool-retro-term's fonts are broken
Date: Wed, 12 Oct 2022 15:25:58 +0000 [thread overview]
Message-ID: <FD5AE0D6-02F7-4367-A03C-4E8C79F7D731@posteo.net> (raw)
In-Reply-To: <87a662jhe5.fsf@dustycloud.org>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
Hi Christine,
Thanks for the report. This should be fixed in https://git.savannah.gnu.org/cgit/guix.git/commit/?id=86ec52f66735b122b9035eba56516fd16f3be958
The "Cannot read property 'fontlist' of null" is still present, but was/is also present in the earlier 1.1.1 release, and seems to be mostly harmless.
Cheers,
`~Eric
On October 11, 2022 7:08:29 PM UTC, Christine Lemmer-Webber <cwebber@dustycloud.org> wrote:
>I realize we've made some modifications to cool-retro-term's font stuff
>back in Bavier's original patches adding cool-retro-term. Particularly,
>some mentions of fonts are emoved. However, something has gone wrong,
>you can no longer increase font sizes, and there aren't really any fonts
>listed. The culprit seems hinted by looking at the output from running
>cool-retro-term from another terminal:
>
>qrc:/Fonts.qml:206:1: Expected token `}'
>qrc:/Fonts.qml:206:1: Expected token `}'
>qrc:/ApplicationSettings.qml:173: TypeError: Cannot read property 'count' of undefined
>qrc:/ApplicationSettings.qml:126: TypeError: Cannot read property 'fontlist' of null
>
>I'm guessing the code that's trying to remove mentions of forbidden
>fonts is accidentally dropping a closing brace somehow.
>
>
>
>
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
[-- Attachment #2: Type: text/html, Size: 1781 bytes --]
prev parent reply other threads:[~2022-10-12 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 19:08 bug#58451: cool-retro-term's fonts are broken Christine Lemmer-Webber
2022-10-12 15:25 ` Eric Bavier [this message]
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=FD5AE0D6-02F7-4367-A03C-4E8C79F7D731@posteo.net \
--to=bavier@posteo.net \
--cc=58451-done@debbugs.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).