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,242
    • Issues 2,242
    • 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
  • #4957

Closed
Open
Opened Jul 18, 2016 by Enrico Ghirardi@cHoco1

Baseline difference from other OSX applications

  • iTerm2 version: Build 3.0.20160717-nightly
  • OS version: 10.11.5

The baseline computation algorithm used by iTerm seems to be different from the one used by other OS X applications.

For example with the Source Code Pro font using regular font style at 12 point size, I noticed that the baseline is 2 pixels above the baseline computed by Safari (in general all Webkit based apps), TextEdit and Terminal.app

As a possible/alternative solution it would be cool adding an option to modify the baseline value manually. (just like vertical and horizontal spacing)

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