ghostty.git/src/cli/edit_config.zig, branch main Unnamed repository; edit this file 'description' to name the repository. Zig 0.15: zig build test 2025-10-03T14:10:43+00:00 Mitchell Hashimoto m@mitchellh.com 2025-10-01T20:10:40+00:00 cb295b84a0ec274a43da59041fa4a199e799798d 






cli: use sh to launch editor
2025-09-24T22:47:29+00:00

Jeffrey C. Ollie
jeff@ocjtech.us

2025-09-24T20:27:46+00:00

bff758f03b077c0c76aa2e677927b9fb26f9efa4












cli: make the action parser (+foo) generic and reusable
2025-07-09T22:06:24+00:00

Mitchell Hashimoto
m@mitchellh.com

2025-07-08T15:55:34+00:00

1739418f6f6fab3bb7df9c2c84eba91ddabe91b2












cli: +edit-config command to open the config file in $EDITOR
2025-06-24T11:17:05+00:00

Mitchell Hashimoto
m@mitchellh.com

2025-06-23T16:29:24+00:00

865ba546a99cb685a263f3801def16891f45ae95

This adds a new CLI `ghostty +edit-config`. This will open the config
file in the user's specified `$EDITOR`. If Ghostty has never been
configured, this will also create the initial config file with some
default templated contents (the same as that which we introduced back in
Ghostty 1.0.1 or something -- not new behavior here).

This is useful on its own because it will find the correct configuration
path to open. If users are terminal users anyway (not a big stretch
since this is a terminal app), this will allow them to easily edit
config right away.

This is also forward looking: I want to replace our "Open Config" action
to open a Ghostty window executing this command so that users can edit
their config in a terminal editor. This has been heavily requested since
forever (short of a full GUI settings editor, which is not ready yet). I
don't do this in this PR but plan to in a future PR.





This adds a new CLI `ghostty +edit-config`. This will open the config
file in the user's specified `$EDITOR`. If Ghostty has never been
configured, this will also create the initial config file with some
default templated contents (the same as that which we introduced back in
Ghostty 1.0.1 or something -- not new behavior here).

This is useful on its own because it will find the correct configuration
path to open. If users are terminal users anyway (not a big stretch
since this is a terminal app), this will allow them to easily edit
config right away.

This is also forward looking: I want to replace our "Open Config" action
to open a Ghostty window executing this command so that users can edit
their config in a terminal editor. This has been heavily requested since
forever (short of a full GUI settings editor, which is not ready yet). I
don't do this in this PR but plan to in a future PR.