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,244
    • Issues 2,244
    • 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
  • #4152

Closed
Open
Opened Jan 24, 2016 by Roger Steve Ruiz@rogeruiz🏋🏽

Possible text rendering issue using `spark`

Issue requirements:

  • iTerm2 version: 2.1.4 √
  • OS version: 10.10.5 √
  • Attached ~/Library/Preferences/com.googlecode.iterm2.plist √
  • Attached a debug log √

Originally, this issue was thought to be related to another library called spark. It's not necessary to be familiar with it, but here's the link. It outputs some specific characters to produce spark charts in the terminal.

I'm posting this issue here because it seems related to iTerm2 and not necessarily related to the spark library. I've tried using different fonts with iTerm2 and previously the spark library looked visually fine before Yosemite.

I'm including a screenshot within the attachment that includes the plist and the debug log.

Here's a command that can be run to produce a spark chart once the library is installed.

    spark 900 1400 1200 2500 12 1300 324 5466

Once you've run that command, you'll notice that the spark lines appear to fall below the bottom of the chart in iTerm2 but not in Terminal.app. Here's a link to the issue on Github for spark for more insight into the bug.

Thanks so much for iTerm2, it's a pleasure to use it daily for both work and fun! :D

iterm2-issue-attachments.zip

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#4152