Skip to content

TerminalFont (Alacritty): fix font size never being parsed from config - #2501

Merged
CarterLi merged 1 commit into
fastfetch-cli:devfrom
HashimAbdulaziz:fix/alacritty-font-size-query-count
Aug 9, 2026
Merged

TerminalFont (Alacritty): fix font size never being parsed from config#2501
CarterLi merged 1 commit into
fastfetch-cli:devfrom
HashimAbdulaziz:fix/alacritty-font-size-query-count

Conversation

@HashimAbdulaziz

Copy link
Copy Markdown
Contributor

Summary

detectAlacritty() passes numQueries = 2 to ffParsePropFileConfigValues(), but fontQueryToml has three entries. { "size =", &fontSize } sits at index 2 and is never queried, so fontSize stays empty and the hardcoded 11.25 fallback is used for every Alacritty user.

Introduced in dd30c82, which added { "family =", &fontFamily } to the middle of the array without bumping the count, and shipped in 2.67.0. It fails silently — the family is still correct and only the size is wrong, so there is no error to notice.

Testing

Fedora 43, Alacritty 0.17.0, ~/.config/alacritty/alacritty.toml:

size = in config before after
20 JetBrainsMono Nerd Font (11.25pt, Regular) JetBrainsMono Nerd Font (20pt, Regular)
13.5 JetBrainsMono Nerd Font (11.25pt, Regular) JetBrainsMono Nerd Font (13.5pt, Regular)

Both sizes were checked against the actual rendered window, not just the reported string.

Related issue (required for new logos for new distros)

N/A — no existing report; found while investigating #2348.

Changes

  • Pass 3 instead of 2 as numQueries for all three Alacritty config paths, so size = is actually queried.

Screenshots

No visual changes — the fix only corrects the reported value.

Checklist

  • I have tested my changes locally.

The query array gained a third entry in
dd30c82 but numQueries stayed at 2, so
`size =` was never queried and every Alacritty user silently got the
hardcoded 11.25 fallback.
@CarterLi
CarterLi merged commit 4c2af40 into fastfetch-cli:dev Aug 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants