Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!mit-eddie!apollo!pcc From: pcc@apollo.COM (Peter Craine) Newsgroups: comp.sys.apollo Subject: Re: su Message-ID: <443365b7.20291@apollo.COM> Date: 3 Jul 89 15:30:00 GMT References: <366@quintro.UUCP> <552@parcplace.pplace.COM> Reply-To: pcc@starchai.UUCP (Peter Craine) Distribution: usa Organization: Apollo Computer, Chelmsford, MA Lines: 55 In article <552@parcplace.pplace.COM> khaw@pplace.COM (Mike Khaw) writes: > > I have to do "stty -tabs" to get ls listings to line > up right, but I don't have to do that for non-root > logins. Users probably have "ts 9 -r" in their startup_dm.. Put one in root's startup_dm and this will probably go away. > > Hitting the HELP key only gets you generic Domain_OS > help, but not man files. Non-root accounts get both > Domain_OS help and man files with the HELP key. Sounds like key definitions. Check out one non-root account's key definitions and do appropriate 'kd's for root. > >(Not-necessarily-root) Domain_OS vi weirdities (no flames >about using vi, please -- I have to work on many different Unix >machines and it's not worth the aggravation to me to learn the DM >editor): > > Occasionally, if you open a shell window and start up > vi immediately, vi prints some complaint about not > knowing what an apollo_ terminal type is, goes > into line mode and then some state where it's hung. > If I kill the vi process and then again try vi in the > same window, it works fine. Sounds like it's time for the generic vi problem-fixer. 1) log on as root 2) rm -rf /dev/ttyp* /dev/pty* 3) /etc/mkdev /dev pty 4) reboot the node. This clears up the majority of vi problems. For anything else, I'd call the 800 number. > > (Must be a keymap problem ...) ^^ (control-caret) doesn't > do anything (it's supposed to take you to the previous file > you were editing). I also wish the bsd environment did > proper keymaps for ^u (kill line) and ^w (kill word). Use your own keydefs. Try (in the command window) kd ^u cms;tl;xd line_del ke This will delete the line that your cursor is on. [this is the current keydef for the key. >Mike Khaw Peter Craine, NACS I know I put my .signature with the appropriate disclaimer in here somewhere!