CodeEditApp / CodeEditApp/CodeEditSourceEditor

✨ Allow configuring the line number font

Open Beginner friendly
#376 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Swift
Stars
719
Forks
160
PR merge metrics
No merged PRs in 30d

Description

### Description

`SourceEditorConfiguration.Appearance.font` configures the editor text font, but the line-number gutter replaces it with `font.rulerFont` in `didSetOnController`. There is currently no public API for choosing the exact font and point size used by line numbers.

A use case is an editor configured with Monaco 12 pt that should also render its line numbers in Monaco 12 pt. At present, this requires maintaining a fork and changing:

```swift
controller.gutterView.font = font.rulerFont
```

A backward-compatible API could be:

```swift
public var lineNumberFont: NSFont?
```

The current behavior could remain the default:

```swift
controller.gutterView.font = lineNumberFont ?? font.rulerFont
```

### Alternatives Considered

- Making `GutterView.font` public. Keeping the option in `Appearance` seems preferable because it avoids exposing the view implementation.
- Always using `Appearance.font` for the gutter. This would change the existing default appearance, so an optional override is safer.

### Additional Context

This request is different from #58 and #157: those issues addressed the default ruler font appearance and proportional scaling. This request is specifically about allowing API consumers to override that default.

Observed on current `main` at revision `1fa4d3c`.

### Screenshots

Not applicable.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at SourceEditorConfiguration.Appearance.font and its didSetOnController handling, then inspect GutterView.font to understand how the ruler font is assigned. Add the proposed optional lineNumberFont API while preserving font.rulerFont as the default, and verify that consumers can override the gutter font without changing existing appearance behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
desktop-dev
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.