Custom Glyphs Disabled in Auxiliary Windows
usabilityActiveStableThe recent update disables custom glyphs in auxiliary terminal windows, impacting usability for users relying on these features.
Score Breakdown
Heuristic ranking from public discussion signals — not a validated prediction of commercial opportunity, demand, or willingness to pay.
Composite 59/100 (Medium, unvalidated). Top driver: Severity (25% weight, 17.5 pts).
Heuristic only — often urgency map or random scaffolding on ingest, not measured mention frequency. Maps to XPS relevance (with market size).
LLM/mock judgment of intensity from title/summary text — not ops or ticket data. Maps to XPS quality (with willingness to pay).
LLM/mock purchase-intent guess from text — not invoices, surveys, or paid seats. Maps to XPS quality.
Heuristic/scaffold (often random or fixed on insert) — not a verified mention trajectory. Maps to XPS novelty.
Heuristic/scaffold (often random or fixed) — not TAM research. Maps to XPS relevance (with frequency).
Catalog notes (not predictive analysis)
Custom Glyphs Disabled in Auxiliary Windows (usability). Catalog heuristic opportunity score: 59/100 — a chosen formula over discussion-signal facets, not evidence of demand, conversion, or willingness to pay. Treat as browsing rank, not a commercial prediction.
The recent update disables custom glyphs in auxiliary terminal windows, impacting usability for users relying on these features.
Source Examples
“Custom glyphs are disabled in auxiliary terminal windows Regression from: https://github.com/microsoft/vscode/pull/330777 Related: https://github.com/microsoft/vscode/issues/327958 PR #330777 patched the terminal rendering crash from #327958 by recreating the WebGL addon with `customGlyphs: false` whenever the terminal is in an auxiliary window. This avoids the `drawPatternChar` crash, but it also disables all xterm custom glyphs for the entire time the terminal is in a dedicated window. That includes box drawing, block elements, Braille, Powerline and progress symbols, even though the original failure was limited to the pattern glyph path creating a temporary canvas through the auxiliary document. Current behavior: ```text Main window Dedicated window Back in main custom glyphs ON -> custom glyphs OFF -> custom glyphs ON ``` I have an xterm.js fix ready that creates the temporary pattern source with `OffscreenCanvas`, with a main-document canvas fallback. The regression test reproduces the original `drawPatternChar` -> auxiliary-document `createElement` failure against the old implementation and passes with the change. Once the xterm fix lands and VS Code consumes that version, we should remove the auxiliary-window custom-glyph guard and the window-driven WebGL addon recreation so custom glyphs stay enabled in dedicated terminal windows.”
Competitive Landscape
- Existing solutions are either too expensive or too limited
- Most competitors target enterprise, leaving mid-market underserved
- Community scripts and manual processes are the primary alternative
Recommended Next Steps
- ✓Validate pain intensity with 5-10 target customer interviews
- ✓Build minimal viable solution addressing the core workflow
- ✓Test pricing with early adopters from community forums
Related Pain Points
Target Customers
- IT teams at mid-size organizations (100-2000 employees)
- MSPs and consultants managing multiple client environments
- Teams without dedicated specialist staff for this domain
Monetization Ideas
- 1SaaS subscription model ($99-$499/month depending on scale)
- 2Usage-based pricing aligned with value delivered
- 3Freemium tier to drive adoption and prove value