githubnext / githubnext/monaspace

Bug <> paired forced typed which don't need to get ligature for <

Open
#401 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
19.6k
Forks
322
PR merge metrics
No merged PRs in 30d

Description

**<> paired forced typed which don't need to get ligature for <**
On Visual studio code with font ligature enabled and using Argon,Krypton .. Monaspace frozen ttf fonts,
Vscode typed forced <> pairing for < character when user try to type a < character,
at that time, prompt cursor never get back to front of one character > but front of < if user try to type left arrow key.
Anyway, that works properly if turn off "font ligature" option.

Tested environment
OS: Fedora 44
Editor: Visual Studio Code (1.131.1)
Font: Monaspace 1.400 Frozen True type Argon, Krypton. Radon

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file or test is named in the report. First reproduce the issue in Visual Studio Code 1.131.1 with the Monaspace Frozen Argon, Krypton, or Radon fonts and font ligatures enabled, then compare left-arrow behavior with ligatures disabled. Done means typing < produces the expected paired > behavior and the cursor moves in front of > rather than back in front of <.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
design
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.