Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!samsung!usc!apple!bbn!jr@bbn.com From: jr@bbn.com (John Robinson) Newsgroups: comp.emacs Subject: Re: Need help with emacs screen management! Message-ID: <50272@bbn.COM> Date: 2 Jan 90 16:59:00 GMT References: <7094@ohstpy.mps.ohio-state.edu> Sender: news@bbn.COM Reply-To: jr@bbn.com (John Robinson) Organization: BBN Systems and Technologies Corporation, Cambridge MA Lines: 60 In-reply-to: tale@cs.rpi.edu (David C Lawrence) In article , tale@cs (David C Lawrence) writes: >Please, when posting to comp.emacs, mention what Emacs you are using. >Based on the content of the cited article I will be answering from the >GNU vantage. Hear hear! Same comment even if you are sending to info-gnu-emacs, or unix-emacs. >Much of GNU Emacs' display management is based on the baud rate, or >what it believes that speed to be. Normally it is very efficient >about screen updates but it can make the wrong decisions when working >with inaccurate understanding of the terminal's capabilities or with >an unrealistic baud value. I noticed an improvement (at least for my home Concept AVT) in the screen management when moving from 18.53 to 18.55. If the original poster (John E. Davis) was using an older version, upgrading might help. >As far as baud is concerned, ... I don't know how you can change it on >your system if this is indeed one of the sources of your problem. For unix systems, the usual way is with the stty command. E.g. `stty 1200'. This can be fatal if you are coming over a hard-wired port and can't change you terminal to the new speed, but when there is a network protocol of some sort in between, the baud rate is meaningless as far as the wiring is concerned, but it does have meaning to emacs as David said; hence changing it won't hurt and then emacs will know the right speed. >Use the register commands, typically bound in the C-x map to r, x, g, >/ and j. Apropos on "register" for different functions you could >examine. They don't work precisely like marks do, but having multiple >markers in a buffer slows Emacs down because they need to be updated >with every change in the buffer. In GNU Emacs, marks are saved on a ring (stack with limited depth that wraps back around). You can go back to earlier ones with a prefix argument to the set-mark command, i.e. (with standard bindings) ^U^@. >I really don't know much about the regular GNU Emacs manual, but I >suspect that the comment you read was directed at Emacs Lisp >programmers who are inclined to make the user's mark for their own >purposes. The comment is in the function documentation for "set-mark-command", the binding of ^@. It points to the documentation of "set-mark", q.v. (that is, type ^H f set-mark RET). The marks are supposed to be for the user; emacs lisp code you write should use variables to remember positions in a buffer. > I don't think this is offered in GNU Emacs, though (default >configuration) hitting C-s after starting isearch will fill in the >text of the last isearch that exited normally. In other words, you can think of "repeat-previous-successful-isearch" as being bound to ^S^S. Similar remark for ^R^R. -- /jr, nee John Robinson Life did not take over the globe by combat, jr@bbn.com or bbn!jr but by networking -- Lynn Margulis