Ctrl+s keybinding not working in Neovim/LazyVim

[awaken233]

Issue Description

The Ctrl+s keybinding (commonly used for 'Save') does not work when using Neovim (LazyVim) inside Ghostty on macOS. The keypress seems to be consumed by the terminal or not forwarded to the application, effectively ignoring the input.

• I have verified that no other application is intercepting Ctrl+s.
• This issue makes it impossible to save files using the standard LazyVim binding (<C-s>).

Expected Behavior

When running Neovim inside Ghostty, pressing Ctrl+s should send the corresponding key code to Neovim, triggering the "Save" action.

Actual Behavior

Pressing Ctrl+s does nothing. Neovim does not receive the input, and the file is not saved.

Reproduction Steps

1. Open Ghostty.
2. Start Neovim (LazyVim distribution).
3. Open any file or create a new buffer.
4. Make a change to the buffer.
5. Press Ctrl+s to attempt to save.
6. Observe that the file is not saved and no 'written' message appears in Neovim command line.

Ghostty Logs

2025-12-17 11:43:38.219210+0800 0xc4dcb    Info        0x0                  18029  0    ghostty: [com.mitchellh.ghostty:ghostty] known but unimplemented action action=37
2025-12-17 11:43:38.223119+0800 0xc4dcb    Info        0x0                  18029  0    ghostty: [com.mitchellh.ghostty:io_exec] found Ghostty resources dir: /Applications/Ghostty.app/Contents/Resources/ghostty
2025-12-17 11:43:38.223366+0800 0xc4dcb    Info        0x0                  18029  0    ghostty: [com.mitchellh.ghostty:io_exec] shell integration automatically injected shell=termio.shell_integration.Shell.zsh
2025-12-17 11:43:38.223736+0800 0xc4dcb    Info        0x0                  18029  0    ghostty: [com.mitchellh.ghostty:ghostty] known but unimplemented action action=20
2025-12-17 11:43:38.227729+0800 0xc6f1f    Info        0x0                  18029  0    ghostty: [com.mitchellh.ghostty:io_exec] started subcommand path=/usr/bin/login pid=18918
2025-12-17 11:43:38.507059+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented ESC action: ESC  k
2025-12-17 11:43:41.679943+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented ESC action: ESC  k
2025-12-17 11:43:41.722309+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented mode: 34
2025-12-17 11:43:45.271286+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented mode: 34
2025-12-17 11:43:45.273175+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented ESC action: ESC  k
2025-12-17 11:43:45.298485+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC callback: terminal.osc.Command{ .end_of_command = terminal.osc.Command__struct_18710{ .exit_code = 0 } }
2025-12-17 11:43:45.298539+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC command: end_of_command
2025-12-17 11:43:53.461910+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented ESC action: ESC  k
2025-12-17 11:43:53.488299+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC callback: terminal.osc.Command{ .end_of_command = terminal.osc.Command__struct_18710{ .exit_code = null } }
2025-12-17 11:43:53.488352+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC command: end_of_command
2025-12-17 11:43:53.645147+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented ESC action: ESC  k
2025-12-17 11:43:53.670342+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC callback: terminal.osc.Command{ .end_of_command = terminal.osc.Command__struct_18710{ .exit_code = null } }
2025-12-17 11:43:53.670393+0800 0xc6f22    Error       0x0                  18029  0    ghostty: [com.mitchellh.ghostty:stream] unimplemented OSC command: end_of_command

Ghostty Version

Ghostty 1.2.3
Version
  - version: 1.2.3
  - channel: stable
Build Config
  - Zig version   : 0.14.1
  - build mode    : builtin.OptimizeMode.ReleaseFast
  - app runtime   : apprt.Runtime.none
  - font engine   : font.main.Backend.coretext
  - renderer      : renderer.generic.Renderer(renderer.Metal)
  - libxev        : kqueue

OS Version Information

macOS 13.7.1(22H221)

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

font-family = "JetBrainsMono Nerd Font Mono"
maximize = true
font-size = 12
theme = dark:Catppuccin Frappe,light:Catppuccin Latte
shell-integration = detect
shell-integration-features = ssh-terminfo,ssh-env,no-cursor
macos-titlebar-style = hidden
quick-terminal-animation-duration = 0
cursor-style = block
cursor-style-blink = false
copy-on-select = clipboard

Additional Relevant Configuration

Neovim Version:

NVIM v0.11.4
Build type: Release
LuaJIT 2.1.1753364724

LazyVim Version:

"LazyVim": { "branch": "main", "commit": "6e3a06306d72a7f7a401c007f56706023a6c00ea" }

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[ianebeckett]

If you run showkey -a in your shell, what keycode is shown by pressing <c-s>? If it matches this:

$ showkey -a

Press any keys - Ctrl-D will terminate this program

^S       19 0023 0x13

then the issue is most likely due to either Neovim or your Neovim configuration. It could also be an issue with LazyVim.

If your keycodes being sent to Neovim are correct, then you can rule out Neovim by testing it with nvim --clean

[danielwe]

Your keybinding isn't being triggered in this screenshot. It should look like this (note the "Triggered Binding" line):

[danielwe]

Try fully restarting Ghostty. Make sure the process has been terminated before restarting, for example using cmd+q, or right-clicking the dock icon and choosing "Quit". (Closing all windows is not enough, the process will remain alive in the background unless you take one of these steps.)

[awaken233]

I've been cmd+q'ing out every time, because I've found that reloading the configuration doesn't work.

[danielwe]

I see. Then I really don't understand what's going on. Sorry I couldn't be of more help. If you end up upgrading your OS, I'd be really curious to know if that fixes it.

[awaken233]

Ok, thank you very much for your patience and help 👍. I need stability in my work environment, I will update the system later and I will send the test results of the new system here.

[ianebeckett]

You can also see what keycode Neovim sees by going into insert mode, then pressing <C-v> to escape input, then pressing <C-s>. When I do this, Neovim inserts '^S' into the buffer.

[awaken233]

I tested it with nvim --clean, and iTerm2, as you said, does see the insertion of ^S, but ghostty I don't see, nothing happens.

[umutuygar]

Add this to your config/keymaps.lua

vim.keymap.set({ "n", "x", "o", "i" }, "<D-s>", "<Nop>", { desc = "Disable Cmd+S" })