Terminal.app resize bug?

Perhaps it is an emacs bug. Have you tried installing the latest version? I'm guessing that since emacs is Stallman's baby it is another GPLv3 program that hasn't been updated on MacOSX since 2007 and never will be.

What other bug are you referring to? The 256 color issue? I believe that was fixed in Lion with the 256 color terminal emulator.

You could try iterm or iterm2

<http://iterm.sourceforge.net/>

<http://www.iterm2.com/>

You can always ssh -Y (or ssh -X) into your Linux system and export xterm's back to your Mac (although I'm not personally a fan of xterm, some people like it).

And of course there is always the gui version of emacs and have it export its X11 windows back to your Mac.

NOTE: I am not an emacs user, so anything I say about emacs is based on things I read on the intertubes :-)

You could VNC to your Linux box (although that generally speaking requires a rather fast network corrected to be anywhere usable for an editing session), also the build-in Mac OS X VNC client (Screen Sharing) does not always play nice outside the Mac family, so you should consider alternative VNC clients, such as Chicken (formally Chicken of the VNC), JollysFastVNC, tightvnc (via MacPorts.org), to name a few.

Finally, if you feel there is a real bug in Terminal that needs to be addressed, please file a bug report with Apple so they will have a chance to see and maybe fix it

BugReporter

<http://bugreporter.apple.com>

Free ADC (Apple Developer Connection) account needed for BugReporter.

Anyone can get a free account at:

<http://developer.apple.com/programs/register/>

I just tried emacs both locally and running on Linux remotely. Everything works fine, even in 256 colors.

quantamos wrote:

I believe it is a bug, I'm just wondering whether other people have noticed and/or figured out exactly what to put in a bug report.

One thing you will definitely need is a sequence of steps to reproduce the error. Advanced tools like Terminal, Xcode, etc. don't get much attention from Apple. Apple seems to feel that these are professional tools and professionals can be expected to put up with things and work around them. Unless you have a bug that can be easily reproduced, they aren't likely to bother with Terminal.

Should I send this in as a bug report?

Yes, HOWEVER, I cannot reproduce your problem on my Mac OS X 10.7.2 Lion system.

After resizing my new tabbed window with /usr/bin/vi, and :quit, my window remains the same size. stty -a shows the correct after resize rows and columns.

You might want to try an experiment. Create a new account (System Preferences -> Accounts). Does Terminal behave the same in this new account? If it does not, then perhaps there is something in your primary account affecting the behavior of your Terminal session, your vi session, your emacs session.

If you have another Mac available, like maybe a friends that has not shared shell initializations, nor editor initializations, and see if it behaves the same. You could even just visit an Apple Store (if one is near by), and try your test on one of those systems.

But if you want to report this, use BugReporter

<http://bugreporter.apple.com>

Free ADC (Apple Developer Connection) account needed for BugReporter.

Anyone can get a free account at:

<http://developer.apple.com/programs/register/>

quantamos wrote:

I'll see if I can get someone else to reproduce it.

I can definitely reproduce it. However, I can just as easily reproduce it in 10.6. I doubt you will get it fixed any time soon. I've had 5-10 terminal sessions open a day for several years and hadn't noticed this.

I do that too. But I never run a vi session in a resized window. When I'm working with code, I don't want to have to scroll left and right and up and down. I keep my editing terminal windows at 80 characters, which gives me 76 characters with the line numbers. I run tail -f and all kinds of other commands in resized windows, but never an editor.

This problem can be reproduced on my machine. It seems that running VIM in the second tab, then resizing the window, messes vim up. But sometimes, an action I take cleans things up. Problem seems worse when shelling into a remote machine. stty reports the SAME on all machines.

I'm not seeing the actual window resize... the problem is mostly within VIM, when scrolling through a document, VIM overdraws the wrong file lines on top of other lines.

I've NOT noticed it prior to 10.7.x ... I'm running Terminal 2.2.2 (303) on OSX 10.7.3, so it may be worth keeping track of versions that exhibit the problem. My TERM is rxvt.

# stty -a

speed 9600 baud; rows 60; columns 186; line = 0;

intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = M-^?; eol2 = M-^?; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O;

min = 1; time = 0;

-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts

-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc ixany imaxbel -iutf8

opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0

isig icanon iexten echo echoe -echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke

# echo $TERM

rxvt

I realize this thread is old but I came across it while trying to chase down a similar problem. Turned out that in my Terminal.app setup I was invoking a script to run when launched that sudo'd me to a different utility account I use for work. With the script I saw that stty -a never kept up with resizes but if I ditched the script and ran the sudo command directly it works just fine. Only posting this in case someone is searching and comes across the thread and this information saves you a headache. 😉

I found one method that seems to work. Typically, when I launch the Terminal application, the window is somehow 2 characters wider than the previous time it was opened/launched, and with every time I launch the application, the window keeps getting wider and wider. The height seems to stay the same. Even though I've set up all the settings to be, and STAY, at 80X24, the application seems to ignore this for some reason. It later opens as 82X24, then later as 84X24, then later as 86X24, etc.

What I do now is a few steps. When it opens in the wrong size, I open a new window in Terminal with command-N and that new window WILL BE at the correct width. I close each window firstthen quit out of Terminal. When I launch it again, THIS TIME, this ONE time, it will have the correct width!

Unfortunately, after quitting out of the application yet again, it reverts back to its buggy width-growing. So I just repeat command-N to open a new correctly-sized window - close each window - then quit - and finally Terminal should open with the correct-sized window for that very next one instance again.

This is useful for me, since some of my scripts won't work if the window grows too wide, and after re-launching Terminal enough times, it can grow clean out of the monitor view!

It's a bit of a clunky solution, but it works for me. I wish I could automate it.