Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!samsung!caen!uflorida!mlb.semi.harris.com!rtpark.rtp.semi.harris.com!mcnc!rti!mozart!sherman From: sherman@unx.sas.com (Chris Sherman) Newsgroups: comp.sys.hp Subject: Re: observations on the (9000/7x0 series) Message-ID: Date: 22 Jun 91 08:53:58 GMT References: <1474@theseas.ntua.gr> <1991Jun21.191139.11313@wlbr.imsd.contel.com> Sender: news@unx.sas.com (Noter of Newsworthy Events) Distribution: sas Organization: SAS Institute Inc. Lines: 83 Nntp-Posting-Host: foster.unx.sas.com In <1991Jun21.191139.11313@wlbr.imsd.contel.com> mh@roger.imsd.contel.com (Mike Hoegeman) writes: >I have a demo unit sitting here also that i am porting some sun stuff >to. So I`ll ad my two cents worth. Yes, It's pretty fast >computationally, it's a bit slower doing nfs i/o. What machine is doing nfs quickly??? I haven't found one yet. >>cons (in no particular order): >> a. Very bad keyboard, especially the escape key and a rather plastic touch. >> NO DELETE key! (very bad) and very small control key. >> proposal: make it a customer option. I would love to have something >> reasonable like a Northgate keyboard. Me too!!! The RS/6000 keyboard is ok. Does anyone use the white keys to the right of the Return key??? >Yes. The keyboard sucks *big* time. two small keys the caps lock and >the ctrl key are right next to each other to the left of 'a'. >thankfully the control key is closest to the 'a' but i still hit caps >lock by accident an awful lot. there is a delete key labeled delete >char. but it's off in the sticks way to the right of the return key. >the keys themselves seem kind cheap too. also there are no nubs on the >home keys which i think is really lame. Here is a keyboard modification command to fix this (I use it, actually). It changes the break key to delete, the Caps to CNTL, and the BackSpace to Delete. (Use this in your .x11start or .xsession script). xmodmap - << MODMAP remove Lock = Caps_Lock add Control = Caps_Lock keysym Break = Escape keysym BackSpace = Delete MODMAP >> b. I don't like (really!) the mechanical mouse. It'll need a piece of paper >> at least in order to stop it from slipping. >> proposal: give us optical mice with flexible mouse pads. >I kinda like the mouse. It is certainly better than most mechanical >mice. I like the nub that on the left mouse button. I'not sure i'd >take it over a optical mouse though.. Optical mise should DIE!!! The mechanical mouse can be pushed around with little effort. You have to grab the optical mouse with both hands (one for the mouse, one for the pad). >> c. The vi and more don't behave so well when I work with more than >> 24x80 text (console, resizing xterms,etc. Neither eval resize >> does the trick). I hope that the solution is just a manual away. >Yes i hated this too. it does not matter if there is some way to do it >in the manual though, it should just do it by default. it does not even >seem to understand anything but your standard terminal size. if you >bring up a terminal with 34 lines vi should use 43 lines. And no i do >not want to make a bunch of bogus terminal definitions for every size >terminal that I want. I will probably resort to porting elvis to it if >I have it long enough. Ahhhh, BSD types. I can spot people like you on a mountain face 5 miles away while looking in the other direction. SYSV does not include the special resize signal which BSD uses to tell non-X applications that the window has resized. (This signal is SIGWINCH [signal: WINdow CHanged] in BSD land). To tell the environment that you have resized a window, do the following: if the system has 'resize', do a eval `resize` If not, do a (under csh, in this example) setenv LINES 24 setenv COLUMNS 80 Unfortunately, nothing you can do will get a running vi to resize in an xterm automatically. -- Chris Sherman .................... sherman@unx.sas.com | ,-----------------------------------------' / Q: How many IBM CPU's does it take to execute a job? | A: Four; three to hold it down, and one to rip its head off.