Skip to content

[Feature]: Let the Ghostty import read a config file you pick #18658

Description

@DeVFirmino

Problem or use case

The Ghostty import reads only the config paths that Ghostty uses. The import has no file picker.

Orca imports terminal appearance from a Ghostty config. The import sets font family, size, weight, line height, cursor, padding, opacity, and the 16 ANSI colors. The import shows a preview. The user must apply the change. That import reads only the locations that Ghostty uses. If the file is in a different location, you must copy the file to ~/.config/ghostty/config first.

I copied a terminal appearance from a different program into Orca. I overwrote an unrelated config. That config belongs to a program that I do not have installed. I did this to use a feature that Orca already supports.

The Warp theme import is in the same section. That import is next to the Ghostty import. The Warp theme import lets you pick a file (auto | chooseFile | chooseFolder).

Proposed solution

Give the Ghostty import an optional source, { kind: 'auto' | 'chooseFile' }. This is the same file-picker origin that Warp already has.

  • Auto-discovery stays the default. The no-argument call does not change.
  • A picked file uses the same read, parse, map, and diff pipeline. The same size ceiling applies.
  • If you dismiss the picker, the function returns a canceled preview. The function applies nothing.

Only the source of the file changes. Parser, mapper, preview, and apply stay as they are. Ghostty has no chooseFolder. This import reads a config file. It does not read a theme directory.

Alternatives or additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions