|
|
Log in / Subscribe / Register

A look at terminal emulators, part 1

A look at terminal emulators, part 1

Posted Apr 1, 2018 18:17 UTC (Sun) by xtifr (guest, #143)
In reply to: A look at terminal emulators, part 1 by jwilk
Parent article: A look at terminal emulators, part 1

If you don't use ^O (which seems likely if you didn't know it existed), you should be able to remap the key to something else without any problems, either using bash's "bind" command or, more generally, using .inputrc.

Not a universal solution, I realize, but should provide a good stopgap, if you're personally worried about this.


to post comments

A look at terminal emulators, part 1

Posted Apr 2, 2018 7:01 UTC (Mon) by tpo (subscriber, #25713) [Link] (1 responses)

In the case of bash unbinding ^O would be:

bind -r "^O"

You need to enter the "^O" there as CTRL-v CTRL-o.

A look at terminal emulators, part 1

Posted Apr 2, 2018 7:38 UTC (Mon) by xtifr (guest, #143) [Link]

bind -r "\C-o" works for me.

It's a little confusing that it doesn't use the same syntax as .inputrc, but such is life...

You can also say "bind -u operate-and-get-next" to remove the binding of that function from *all* keys.

Though honestly, now that I look at it, it's a handy command I wish I'd known about before, and I may end up binding it to some other key, despite it's (relatively mild) danger.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds