~= displays as ligature instead of =~ (Ruby)
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 82k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
Under the Ruby section, the readme suggests that =~ will display as a ligature. However, for me ~= is converted to a ligature, while =~ is not.
Using Atom 1.58.0 x64 on Ubuntu 20.04.4 LTS, Fira version 2+dfsg1-1 downloaded via apt.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Ruby section of the README and reproduce the reported behavior in Atom 1.58.0 x64 on Ubuntu 20.04.4 LTS using Fira version 2+dfsg1-1. Compare rendering of =~ and ~=; done means the README and observed ligature behavior agree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby, ubuntu
- Domain
- desktop, developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100