config: fix accidental codeblock indents
In our webgen we treat 4 consecutive spaces as a code block, which is often triggered by mistake when a paragraph is encased within a list. We should probably fix this more thoroughly at some point since I don't think actual Markdown parsers have the same behavior, but for now we just fall back to using 3-space indents.pull/8284/head
parent
ed603b07a5
commit
2421132d80
|
|
@ -1330,7 +1330,9 @@ class: ?[:0]const u8 = null,
|
|||
/// The keybind trigger can be prefixed with some special values to change
|
||||
/// the behavior of the keybind. These are:
|
||||
///
|
||||
/// * `all:` - Make the keybind apply to all terminal surfaces. By default,
|
||||
/// * `all:`
|
||||
///
|
||||
/// Make the keybind apply to all terminal surfaces. By default,
|
||||
/// keybinds only apply to the focused terminal surface. If this is true,
|
||||
/// then the keybind will be sent to all terminal surfaces. This only
|
||||
/// applies to actions that are surface-specific. For actions that
|
||||
|
|
@ -1338,37 +1340,41 @@ class: ?[:0]const u8 = null,
|
|||
///
|
||||
/// Available since: 1.0.0
|
||||
///
|
||||
/// * `global:` - Make the keybind global. By default, keybinds only work
|
||||
/// within Ghostty and under the right conditions (application focused,
|
||||
/// sometimes terminal focused, etc.). If you want a keybind to work
|
||||
/// globally across your system (e.g. even when Ghostty is not focused),
|
||||
/// specify this prefix. This prefix implies `all:`. Note: this does not
|
||||
/// work in all environments; see the additional notes below for more
|
||||
/// information.
|
||||
/// * `global:`
|
||||
///
|
||||
/// Available since: 1.0.0 (on macOS)
|
||||
/// Available since: 1.2.0 (on GTK)
|
||||
/// Make the keybind global. By default, keybinds only work within Ghostty
|
||||
/// and under the right conditions (application focused, sometimes terminal
|
||||
/// focused, etc.). If you want a keybind to work globally across your system
|
||||
/// (e.g. even when Ghostty is not focused), specify this prefix.
|
||||
/// This prefix implies `all:`.
|
||||
///
|
||||
/// * `unconsumed:` - Do not consume the input. By default, a keybind
|
||||
/// will consume the input, meaning that the associated encoding (if
|
||||
/// any) will not be sent to the running program in the terminal. If
|
||||
/// you wish to send the encoded value to the program, specify the
|
||||
/// `unconsumed:` prefix before the entire keybind. For example:
|
||||
/// `unconsumed:ctrl+a=reload_config`. `global:` and `all:`-prefixed
|
||||
/// keybinds will always consume the input regardless of this setting.
|
||||
/// Since they are not associated with a specific terminal surface,
|
||||
/// they're never encoded.
|
||||
/// Note: this does not work in all environments; see the additional notes
|
||||
/// below for more information.
|
||||
///
|
||||
/// Available since: 1.0.0 on macOS, 1.2.0 on GTK
|
||||
///
|
||||
/// * `unconsumed:`
|
||||
///
|
||||
/// Do not consume the input. By default, a keybind will consume the input,
|
||||
/// meaning that the associated encoding (if any) will not be sent to the
|
||||
/// running program in the terminal. If you wish to send the encoded value
|
||||
/// to the program, specify the `unconsumed:` prefix before the entire
|
||||
/// keybind. For example: `unconsumed:ctrl+a=reload_config`. `global:` and
|
||||
/// `all:`-prefixed keybinds will always consume the input regardless of
|
||||
/// this setting. Since they are not associated with a specific terminal
|
||||
/// surface, they're never encoded.
|
||||
///
|
||||
/// Available since: 1.0.0
|
||||
///
|
||||
/// * `performable:` - Only consume the input if the action is able to be
|
||||
/// performed. For example, the `copy_to_clipboard` action will only
|
||||
/// consume the input if there is a selection to copy. If there is no
|
||||
/// selection, Ghostty behaves as if the keybind was not set. This has
|
||||
/// no effect with `global:` or `all:`-prefixed keybinds. For key
|
||||
/// sequences, this will reset the sequence if the action is not
|
||||
/// performable (acting identically to not having a keybind set at
|
||||
/// all).
|
||||
/// * `performable:`
|
||||
///
|
||||
/// Only consume the input if the action is able to be performed.
|
||||
/// For example, the `copy_to_clipboard` action will only consume the input
|
||||
/// if there is a selection to copy. If there is no selection, Ghostty
|
||||
/// behaves as if the keybind was not set. This has no effect with `global:`
|
||||
/// or `all:`-prefixed keybinds. For key sequences, this will reset the
|
||||
/// sequence if the action is not performable (acting identically to not
|
||||
/// having a keybind set at all).
|
||||
///
|
||||
/// Performable keybinds will not appear as menu shortcuts in the
|
||||
/// application menu. This is because the menu shortcuts force the
|
||||
|
|
@ -1522,23 +1528,31 @@ keybind: Keybinds = .{},
|
|||
///
|
||||
/// Valid values:
|
||||
///
|
||||
/// * `none` - All window decorations will be disabled. Titlebar,
|
||||
/// borders, etc. will not be shown. On macOS, this will also disable
|
||||
/// tabs (enforced by the system).
|
||||
/// * `none`
|
||||
///
|
||||
/// * `auto` - Automatically decide to use either client-side or server-side
|
||||
/// All window decorations will be disabled. Titlebar, borders, etc. will
|
||||
/// not be shown. On macOS, this will also disable tabs (enforced by the
|
||||
/// system).
|
||||
///
|
||||
/// * `auto`
|
||||
///
|
||||
/// Automatically decide to use either client-side or server-side
|
||||
/// decorations based on the detected preferences of the current OS and
|
||||
/// desktop environment. This option usually makes Ghostty look the most
|
||||
/// "native" for your desktop.
|
||||
///
|
||||
/// * `client` - Prefer client-side decorations.
|
||||
/// * `client`
|
||||
///
|
||||
/// Prefer client-side decorations.
|
||||
///
|
||||
/// Available since: 1.1.0
|
||||
///
|
||||
/// * `server` - Prefer server-side decorations. This is only relevant
|
||||
/// on Linux with GTK, either on X11, or Wayland on a compositor that
|
||||
/// supports the `org_kde_kwin_server_decoration` protocol (e.g. KDE Plasma,
|
||||
/// but almost any non-GNOME desktop supports this protocol).
|
||||
/// * `server`
|
||||
///
|
||||
/// Prefer server-side decorations. This is only relevant on Linux with GTK,
|
||||
/// either on X11, or Wayland on a compositor that supports the
|
||||
/// `org_kde_kwin_server_decoration` protocol (e.g. KDE Plasma, but almost
|
||||
/// any non-GNOME desktop supports this protocol).
|
||||
///
|
||||
/// If `server` is set but the environment doesn't support server-side
|
||||
/// decorations, client-side decorations will be used instead.
|
||||
|
|
|
|||
Loading…
Reference in New Issue