MOST annoying. So, if anyone has any idea what might be causing these crashes, or can shed any light on this stuff, please let me know! Since I do a lot of editing, I find Terminal crashes several times a day. So, with both Terminal and vi set to use the right encoding, it all works: I can see all the extended characters, and edit them in the usual way. EXCEPT that there's some bug or incompatibility lurking there. Every so often, when I'm editing in vi, the Terminal will suddenly quit for no reason. It happens often enough to be fairly sure that it's related to the extended characters and to vi - it's never happened when editing plain 7-bit ASCII files, nor when using extended characters in the shell. I suspect it may be related to extended characters appearing at the extreme right or bottom of the screen, and/or to the VTwhatever formatting codes (which I don't really understand).
Mac os best terminal emulator mac os x#
I use the vi editor you can tell it the character encoding through the $LC_CTYPE environment variable. The only problem is that although Mac OS X comes with several character encodings (in /usr/share/locale), it doesn't come with one for Windows Latin-1 (aka CP1252). So I've created my own (with the mklocale(1) command. I've even submitted the result to Apple in the hope that they might include it with future versions.
Mac os best terminal emulator iso#
 Most of my text files use the Windows Latin-1 encoding (the same as the default ISO Latin-1, but with curly quotes and other useful control characters in an otherwise-unused range). No problem for the Terminal: you can set the character encoding in Window Settings->Display. I hit this one a LOT. It's a real annoyance. If the terminal app crashes you lose ALL of your terminals! So, is there a secret terminal port from NeXTSTEP lurking in the pocket of some intrepid young hacker, who is, as I write this, poised to lead us to salvation?"
Sure, transparency is nice, and with some hacking about (when was the last time you had to force "stty erase"?) you can get decent enough color xterm emulation, but. Apple's Terminal is slow (though performance has been better in 10.2.x), doesn't support xterm mousing, and for some reason refuses to send PgUp/PgDn through to any applications running in the terminal (gah!)."Take, for instance, the following options: What's your answer to the state of terminal emulation on the Mac?" Drawoc summarizes the currently available offerings and their drawbacks, below.
Unfortunately for me, decent terminal emulation seems to be one area where Mac OS X is quite lacking. However, due to the sort of development work I do, I spend a great deal of my time in a terminal.
Drawoc Suomynona asks: "After settling into Mac OS X over the last four months, I'm generally impressed.
0 kommentar(er)
