You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by levito February 16, 2025
According to https://ghostty.org/docs/config#syntax, options with empty values should set them to the default. But with keybind =, all keybinds are removed, including the default ones.
Also, according to https://ghostty.org/docs/config#file-location, multiple config files are applied after one another, with the macOS config in ~/Library overwriting the ~/.config one.
With this behavior, I wanted to create two config files to have dotfiles working on both Linux and macOS:
~/.config/ghostty/config with options for both systems and keybinds for Linux
~/Library/Application\ Support/com.mitchellh.ghostty/config should then unset the Linux keybinds with keybinds = and set different ones for macOS
Did I miss anything, or is the current behavior that keybind = removes all keybinds including the default ones a bug?
The text was updated successfully, but these errors were encountered:
As an implementation note, I think the best way to do this is to pull out all our default keybind setting into a function (if it isn't already, I can't remember) and call that directly from the Keybind parse CLI flags when empty instead of clearing.
Discussed in #5816
Originally posted by levito February 16, 2025
According to https://ghostty.org/docs/config#syntax, options with empty values should set them to the default. But with
keybind =
, all keybinds are removed, including the default ones.Also, according to https://ghostty.org/docs/config#file-location, multiple config files are applied after one another, with the macOS config in
~/Library
overwriting the~/.config
one.With this behavior, I wanted to create two config files to have dotfiles working on both Linux and macOS:
~/.config/ghostty/config
with options for both systems and keybinds for Linux~/Library/Application\ Support/com.mitchellh.ghostty/config
should then unset the Linux keybinds withkeybinds =
and set different ones for macOSDid I miss anything, or is the current behavior that
keybind =
removes all keybinds including the default ones a bug?The text was updated successfully, but these errors were encountered: