xtermjs/xterm.js

OSC 50 (get/set font) VT sequence

Open

#3,367 opened on Jun 11, 2021

View on GitHub
 (12 comments) (0 reactions) (0 assignees)TypeScript (1,574 forks)batch import
help wantedtype/enhancement

Repository metrics

Stars
 (16,196 stars)
PR merge metrics
 (Avg merge 2d 10h) (16 merged PRs in 30d)

Description

As per ctlseqs.txt from xterm, OSC 50 is used to query/set the use font.

I was actually looking into neofetch and how it is detecting the font being used, and I think they all got it wrong (fishing the font by looking into the config file of the detected terminal). The proper way to communicate with the TE is to use the PTY, so through some VT sequence.

There is already OSC 50 and at least xterm and mintty (and mine) are supporting that. I'd wonder if you have interest in supporting that too (at least the getter part).

Many thanks, Christian.

Contributor guide

Research direction
Study OSC 50 implementation in xterm and mintty source code, then examine xterm.js's existing OSC handlers (e.g., OSC 0-10) to understand the pattern for adding new sequences.
Tech stack
typescript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Terminal emulation basicsVT sequence knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55