gemini-cli - 💡(How to fix) Fix Ctrl+O for viewing truncated shell output fails due to TTY and Shell-level interception [1 participants]

What would you like to be added?

I am using gemini-cli (v0.40.0-nightly) in a standard Bash environment on a Mac (tried this with both Iterm2 and Ghostty). The new feature to expand truncated lines uses Ctrl+O, but the shortcut was completely unresponsive for me.

Turns out it conflicts with long-established terminal hotkey: Ctrl+O is used for Discard/Operate. According to AI:

In Bash (and other shells using Readline), Ctrl+O is bound by default to the operate-and-get-next function.

Reference: GNU Readline Library - Default Bindings.

Conflict: When running in "Shell Mode," the underlying shell intercepts the sequence to manage history execution, preventing the CLI's UI-layer from catching the event.

Steps to verify: Open your terminal and run bind -P | grep "\C-o", it would show what it's bound to, and if operate-and-get-next appears there, it's a problem.

Steps to Reproduce: Use a standard terminal emulator (e.g., Ghostty, iTerm2, or Alacritty) with default stty settings.

Launch gemini-cli (v0.40.0-nightly or similar).

Trigger a truncated output.

Press Ctrl+O.

Observed Result: Nothing happens (or the shell attempts to execute the current line from history).

Expected Result: The truncated lines should expand/open in the pager.

So looks like Ctrl+O is a poor choice, at least for this environment, it's like trying to rebind Ctrl+R or Ctrl+W, both classic terminal shortcuts. Can we default to something else instead?

Why is this needed?

Being able to easily expand shell output is a critical requirement for my workflow.

Additional context

No response