tonsky / tonsky/FiraCode

Question: how to deal with non-monospace ligatures?

Open
#1,258 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Clojure
Stars
82k
Forks
3.2k
PR merge metrics
No merged PRs in 30d

Description

I'm wondering how to deal with long ligatures since they are effectively not monospace? For example underlines of headers in markdown:

gscreenshot_2021-06-23-171702

or simply trying to draw some boxes in ascii:

gscreenshot_2021-06-24-141149

gscreenshot_2021-06-24-142233

(the character before the right +s is a - even though it looks like a )

I'm using latest ttf-fira-code from the arch repository in neovim 0.5

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the three screenshots and reproducing the reported behavior in Neovim 0.5 with the latest Arch ttf-fira-code package. The issue names no source files or tests and asks how to handle non-monospace ligatures, so work is complete only when the behavior has a documented resolution or a clearly scoped fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown, neovim
Domain
desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.