Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 2
    I just tried this in my own bash running in an xterm on NetBSD, and it doesn't work! Are there settings that can influence this? I have no .inputrc file. C-o is not mentioned in the manual page for readline(3). Commented Jan 16, 2018 at 10:24
  • @Rhialto Are you using vi line editing (enabled with set -o vi) or emacs? Because Ctrl-O won't work with the former as far as I can tell. Commented Feb 13, 2018 at 13:17
  • ...but this can be remedied with the command: bind "\C-o":operate-and-get-next (or add everything after bind to ~/.inputrc) Commented Feb 14, 2018 at 15:34
  • 1
    I found out what my problem is: ^O is taken as the Flush Output character (not supported on Linux), and readline doesn't disable this while it is active. I supplied a simple patch but the bash and readline maintainer maintains that this is Not A Bug. I disagree. See lists.gnu.org/archive/html/bug-readline/2018-01/msg00004.html Commented Feb 14, 2018 at 21:15