info-mac@uw-beaver (01/25/85)
From: Carl Weir <LRC.Weir@UTEXAS-20.ARPA> I just recently purchased a Macintosh along with MacTerminal and an Apple 1200. Since I am writing a thesis, I had hoped to get a lot of use out of the Mac as a terminal emulator, working in Emacs on a Dec 20. However, I haven't been very happy with the performance of MacTerminal when doing Emacs; often certain command sequences cause flakey things to happen. For example, on occasion I will do a series of control-Bs and then begin to insert text only to find that the text doesn't appear on the screen (blank spaces will, though). Also, garbage will sometimes be inserted at the beginning of the paragraph I am working in. This is not the only problem I have encountered. On occasion I will issue a series of commands--I haven't discovered which series is responsible yet--and the font being displayed on the screen will change. I assume that changes to MacTerminal will improve its performance when using Emacs on a Dec 20; does anyone know if the people working on MacTerminal are aware of these problems and are trying do something about them? What do people with pre-release copies of MacTerminal version 1.2 think? Sorry if I've covered exactly the same ground as other messages about MacTerminal. -------
info-mac@uw-beaver (01/28/85)
From: Werner Uhrig <CMP.WERNER@UTEXAS-20.ARPA> Carl, your problems seem to be way out of line with what I have encountered with the Emacs-Mac combination. sounds as if you may be able to improve things somewhat by changing some parameters both on the R20 and on the Mac-side. Let me jsut tell you the way I am set up: on the 20 I use terminal type VT100, in EMACS I use M-X Set Terminal Type$VT100 (well, actually, I have my EMACS.INIT set up to use this as default when on a dial-up line) On the Mac-side, I use VT100 in ANSI mode,8bits, no parity, XON/XOFF enabled (the last is very important when using 9600Baud lines) notice that I suspect your problem to be caused by not having XON/XOFF enabled. the Mac does not seem to be able to keep up with even 1200 Baud without it. An undesirable side-effect of XON/XOFF is that ^S, the Emacs-SEARCH command, and ^Q the Emacs QUOTE command are misinterpreted by the Mac. when in EMACS using ^S to SEARCH, Mac thinks that you just wanted to stop output, so nothing is displayed further until you type ^Q. Reason seems to be that the screen display can't keep up with the characters coming "down the pipe", so MacTerminal assumes when it sees a ^S, you want scrolling to stop NOW, rather than display every- thing already received into the buffer. So rather than just passing the ^S to the main-frame to decide what to do with it, MacTerminal tries to "second guess" the user. Sigh ....makes using EMACS a real drag. try it at 9600 Baud sometimes, and watch how Mac and 20 get confused when MacTerminal sends a ^S to tell the 20 to stop sending stuff - and Emacs on the 20 thinks you jsut typed a SEARCH-command. Curse ...... -------
info-mac@uw-beaver (01/30/85)
From: Daniel Breslau <MDC.BRESLA%MIT-OZ@MIT-MC.ARPA> Most Emacs versions have a command to tell Emacs to pass ^S and ^Q to the system. In Gosling Emacs (NOT -20 emacs), it's M-X Set-terminal-characteristics "xon-protocol" 1 Try looking in the manual for the -20 command; I've grown less familiar with -20 Emacs lately. (sigh) Hope I've helped. Dan Breslau -------