Skip to main content

Configuring Mac OS X Terminal

The post you're reading is ancient, and yet slightly inexplicably popular :) I've recently started blogging again in 2020 with some fresh content. Check out some of the new topics about blogging again, dynamic method invocation, and aapt2.

I recently installed Leopard (Mac OSX 10.5) on a new mac. There are a few factory settings I usually change on a new installation, although by far fewer than I do typically with Windows. One of them is the default keyboard configuration for Ctrl+Left Arrow, Ctrl+Right Arrow, Page Up, Page Down, Home, and End in Terminal. The default settings drive me a bit potty since I'm used to using Linux and emacs every day at work.

Changing them is easy, fortunately. Just visit Keyboard under Settings in Terminal->Preferences, and modify the following keys, so that their action matches the value shown. You can edit the keystroke for an item by double clicking on it, selecting "send string to shell", and typing the indicated keys.

Key Action Keystrokes
control cursor left \033b ESC b
control cursor right \033f ESC f
end \005 CTRL+e
home \001 CTRL+a
page down \026 CTRL+v
page up \033v ESC v

Comments

  1. This would be a good tip, if it weren't completely unnecessary. Every Mac OS X configuration I've ever set up or used had the Emacs keys already working in Bash right out of the box.

    ReplyDelete
  2. not if you ssh into a Linux box from Console.

    ReplyDelete
  3. ... And also home / end / page up / page down don't work in bash in Console the way they do in Linux.

    ReplyDelete
  4. This is a fantastic tip! I do all of my work on a remote linux box and feel like I spend a large chunk of my day scrolling through text. Thanks for saving me a lot of time.

    ReplyDelete
  5. Do you happen to know the code that Tiger sent by default when you used pgup/pgdn? I think it was an actual pgup/pgdn character. One of the things I use via terminal is screen+irssi, and without my pgup/pgdn I don't have access to scrollback anymore with Leopard - note that irssi scrollback is different from terminal scrollback; shift-pgup/pgdn was what I always used to use to scroll through the terminal scrollback buffer.

    I tried just pressing the pgup/pgdn key, but nothing showed up in the field. (Note I'm on a laptop so I have to use fn-arrow, there is no separate key.)

    Thanks for any suggestions...

    ReplyDelete
  6. An alternative: look at the termcap entry on the machine you are sshing into and change your cursor keys etc... to match:

    up: \033OA
    down: \033OB
    left: \033OD
    right: \033OC
    home: \033[1~
    end: \033[4~

    etc...

    ReplyDelete
  7. my last macbook pro complaint is resolved. thanks!

    ReplyDelete
  8. Seems like Shift-Page(up/down) sends the right thing to bash :-)

    ReplyDelete
  9. janra-

    I was fooling around with scrollback in irssi and found that shift+fn+pageup/down is used for scrollback.

    ReplyDelete
  10. Great tip, thanks!

    ReplyDelete
  11. Thank you! Now my Terminal finally behaves the way I expect it to.

    ReplyDelete
  12. Great, Thanks !

    ReplyDelete
  13. I have been complaining about this for years. Thank you

    ReplyDelete

Post a Comment

Popular posts from this blog

Java Blooper #2: Must be a Better Way...

The post you're reading is ancient, and yet slightly inexplicably popular :) I've recently started blogging again in 2020 with some fresh content. Check out some of the new topics about blogging again, dynamic method invocation, and aapt2.It's Monday, which means it's time for another blooper... What's wrong with this code? boolean hasThing( List things, Thing thing ) { for ( int i=0; i < things.size(); i++ ) { if ( thing.equals( things.get( i ) ) ) { return true; } } return false; } Update: Minor edit to add missing parenthesis from if statement that got "lost in translation" en-route to the blog :)

Java Blooper #1: Ternary Insanity

The post you're reading is ancient, and yet slightly inexplicably popular :) I've recently started blogging again in 2020 with some fresh content. Check out some of the new topics about blogging again, dynamic method invocation, and aapt2.From time to time, we all write code that could be clearer. Sometimes in the rush of solving a problem, we don't pay attention to the micro details of the code flowing from our fingertips. Other times, we refactor some existing code, and don't necessarily take the opportunity to clean up as much as we could.I find it useful sometimes when reading code to think about whether it could be rewritten in a more straightforward way, and if so whether any lessons can be learned about writing tight and expressive, and most importantly, readable code.Over the next few weeks, I'm going to blog weekly examples of some Java code bloopers that I've seen. All the examples are real and have been observed "in the wild". However some…