Hi Kevin, > This happens to a terminal when it trys to display ascii code 14 > (ctrl-N), which switches the display to the top 128 ascii characters.
Yes, that's it. Your test case reliably garbles the output of the version of Gnome Terminal in RH4. > Now, I've never seen this happen for anyone else. So I'm guessing there > is something in your saved session or config files which is causing this > to happen. We might be able to work out what if you can send the full > coot log output. > > If you do > > coot >& coot.log I had my user do exactly this, and the resulting coot.log file doesn't have any ctrl-Ns in it. Also, it's occurring on multiple machines, for multiple users at a single site. The Coot installation is shared via NFS to a group of machines. I'm starting wonder if there's some gunkus in the coot start up script that is doing this, since it happens as soon as they hit enter after the coot command. There's more information on this particular bit of terminal oddness here: http://www.in-ulm.de/~mascheck/various/alternate_charset/ I was thinking I might do something sledgehammery and just add a 'reset' at the top of the Coot start up script. Unfortunately I can't duplicate this issue on any machines I directly control, so narrowing down the problem to come up with a more elegant solution may be more trouble that it's worth (to me). -ben -- | Ben Eisenbraun | Software Sysadmin | | Structural Biology Grid | http://sbgrid.org | | Harvard Medical School | http://hms.harvard.edu |
