Quick and stupid: Don't set unlimited on the buffer size of Terminal

4 Comments

If you're a developer and use Terminal.app, don't set "unlimited" on the buffer size. After a day of using it heavily to review logs and whatnot your computer will be *really* slow. It's Terminal.app keeping in RAM what you did yesterday. Stupid and Obvious, but still figured I'd write it down.

Share this
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Google Bookmarks
  • email
  • Slashdot
  • TwitThis
  • Live
  • Meneame

4 Comments (+add yours?)

  1. Rob Meyer
    Jan 14, 2009 @ 14:54:05

    Great point. Certainly don’t do that, and then do “cat /dev/zero”. ;-)

  2. Steve Jenson
    Jan 17, 2009 @ 00:13:27

    Cmd-K will clear the buffer, it’s a command I use all the time to help me keep track of the most recent logfile (or whatever) I’m looking at.

  3. Philip Jenvey
    Jan 19, 2009 @ 13:48:22

    I prefer the unlimited size, it has actually saved me a couple of times

    I’ve programmed myself to regularly cmd-k, though

  4. Hackerdude
    Jan 19, 2009 @ 22:34:22

    Ah, you mean… discipline, right? I’ve heard that’s a nice feature if you have it ;-)

Leave a Reply