Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
iterm2
iterm2
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,246
    • Issues 2,246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • George Nachman
  • iterm2iterm2
  • Issues
  • #4955

Closed
Open
Opened Jul 18, 2016 by David Z. Chen@davidzchen

Spacing and rendering of ligatures inconsistent depending on coloring on macOS Sierra

  • iTerm2 version: Build 3.0.20160717-nightly
  • OS version: macOS Sierra 10.12 Beta 16A239j
  • com.googlecode.iterm2.plist
  • debuglog.txt
  • Screencast: screencast.mov

On macOS Sierra Beta 2, the spacing and rendering of ligatures seems to be inconsistent depending on the context in which the characters are output. In the screencast above, the ligature for the character sequence ==>is rendered incorrectly when it is by itself but renders correctly as a string argument to echo. Further, the string "==>" renders incorrectly as well:

Screen_Shot_2016-07-17_at_7.09.06_PM

Further, ==> renders in yet another way in the output of brew upgrade, where the => portion of the character sequence renders as the greater-equals ligature:

Screen_Shot_2016-07-17_at_7.04.08_PM

Other ligatures, such as +++, have similar problems:

Screen_Shot_2016-07-17_at_7.03.50_PM

Assignee
Assign to
Feature Complete 3.1
Milestone
Feature Complete 3.1 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gnachman/iterm2#4955