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

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

Rob MeyerJanuary 14th, 2009 at 2:54 pm

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

Steve JensonJanuary 17th, 2009 at 12:13 am

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.

Philip JenveyJanuary 19th, 2009 at 1:48 pm

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

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

HackerdudeJanuary 19th, 2009 at 10:34 pm

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

Leave a comment

Your comment