RFC: Font Configuration
I've been thinking about many of the current limitations of how Alacritty's font configuration and possible solutions. This is an RFC for a fully capable font configuration section. Feedback is very much invited! I may have missed out on some important requirement, and I may have missed out on an obviously better solution. Please feel welcome to comment and suggest improvements or add to the list of use cases this should handle. ## Font Configuration, today Current font configuration is achieved through the following block of YAML. Most of the comments are preserved for clarity. ```yaml font: # The normal (roman) font face to use. normal: family: monospace style: Regular # The bold font face bold: family: monospace style: Bold # The italic font face italic: family: monospace style: Italic # Point size of the font size: 11.0 # Offset is the extra space around each character. offset.y can be thought of # as modifying the linespacing, and offset.x as modifying the letter spacing. offset: x: 0.0 y: 0.0 # Glyph offset determines the locations of the glyphs within their cells with # the default being at the bottom. Increase the x offset to move the glyph to # the right, increase the y offset to move the glyph upward. glyph_offset: x: 0.0 y: 0.0 # OS X only: use thin stroke font rendering. Thin strokes are suitable # for retina displays, but for non-retina you probably want this set to # false. u
Posted by jwilm on Dec 23, 2017, 1:31 AM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
RFC: Font Configuration
I've been thinking about many of the current limitations of how Alacritty's font configuration and possible solutions. This is an RFC for a fully capable font configuration section. Feedback is very much invited! I may have missed out on some important requirement, and I may have missed out on an obviously better solution. Please feel welcome to comment and suggest improvements or add to the list of use cases this should handle. ## Font Configuration, today Current font configuration is achieved through the following block of YAML. Most of the comments are preserved for clarity. ```yaml font: # The normal (roman) font face to use. normal: family: monospace style: Regular # The bold font face bold: family: monospace style: Bold # The italic font face italic: family: monospace style: Italic # Point size of the font size: 11.0 # Offset is the extra space around each character. offset.y can be thought of # as modifying the linespacing, and offset.x as modifying the letter spacing. offset: x: 0.0 y: 0.0 # Glyph offset determines the locations of the glyphs within their cells with # the default being at the bottom. Increase the x offset to move the glyph to # the right, increase the y offset to move the glyph upward. glyph_offset: x: 0.0 y: 0.0 # OS X only: use thin stroke font rendering. Thin strokes are suitable # for retina displays, but for non-retina you probably want this set to # false. u
Comments (0)
No comments yet. Start the discussion.