tom@mims-iris.uucp (Tom Haapanen) (05/24/89)
> Mark Callow <sgi!msc%ramoth.SGI.COM@ucbvax.berkeley.edu> writes: >> No, no, no! Never edit init.ps unless you really know what you are doing. fsfacca@LERC08.NAS.NASA.GOV (Tony Facca) writes: > I agree that init.ps is not a file which should be modified. OK, so I suppose you could figure out a way to modify the size and font of the default window using PostScript in user.ps, but for me, it was a lot easier looking it up in init.ps, and changing the window to be 40x80 in font ScreenBold. Have I committed a deadly sin? (The default window size/placement is very annoying, as the pointer is initially outside the window, so the window isn't active & you can't type). \tom haapanen tom@mims-iris.UWaterloo.CA watmims research group university of waterloo "Now, you didn't really expect my views to agree with my employer's, did you?"
fsfacca@LERC08.NAS.NASA.GOV (Tony Facca) (05/24/89)
Tom Haapanen <jarvis.csri.toronto.edu!utgpu!watmath!maytag!watvlsi!watale!mims-iris!tom@rutgers.edu> writes: [ background stuff deleted ] >OK, so I suppose you could figure out a way to modify the size and font >of the default window using PostScript in user.ps, but for me, it was a >lot easier looking it up in init.ps, and changing the window to be 40x80 >in font ScreenBold. Have I committed a deadly sin? I can't speak for Mark, but changing init.ps is not "really" that dangerous, if, as Mark points out, you know what you are doing. If you goof, the window manager may not come up at all. If you have a backup and know how to recover, there is not much to worry aboout. I have done EXACTLY the same thing as you did in the past. With each new release, I had to re-edit the init.ps file and do it again. It turns out to be much less hassel to bite the bullet and learn how to use the window manager. Actually, the 4Sight documentation is quite helpful in this area. >(The default window size/placement is very annoying, as the pointer is >initially outside the window, so the window isn't active & you can't type). I don't understand at all why SGI does this. Why not supply a window default configuration that can be used as is?? Is this to force us to learn how to do it ourselves? I have included the following lines to the default /usr/NeWS/lib/user.ps file which makes it at least bearable for users who don't care to modify their own user.ps files: ---------------------------- sample user.ps ------------------------------ % % User customization file. % % Author: Tony Facca % Date: October 20, 1988 % % This files contains information needed to configure the window manager % for each user. % % You can modify this file to your taste. /RestartActions [ { (demochest) forkunix } { (wsh -n c_shell -t"$USER on `hostname`" -fScreenBold.12) forkunix} { (clock) forkunix } ] def (clock) 1150 20 110 100 makepreference (c_shell) 100 150 preforigin (console) 165 820 600 150 makepreference ------------------------ end of user.ps code segment ------------------------ This just moves the console out of the way, and starts a "wsh" with better placement and font size. It also provides an example (clock) of how to add your own favorite tools, etc. to the user.ps file, for users who care to add to it. -- ----------------------------------------------------------------------------- Tony Facca | phone: 216-433-8318 NASA Lewis Research Center | Cleveland, Ohio 44135 | email: fsfacca@lerc08.nas.nasa.gov -----------------------------------------------------------------------------
archer@elysium.sgi.com (Archer Sully) (05/24/89)
In article <3172@watale.waterloo.edu> tom@mims-iris.waterloo.edu.UUCP (Tom Haapanen) writes: >> Mark Callow <sgi!msc%ramoth.SGI.COM@ucbvax.berkeley.edu> writes: >>> No, no, no! Never edit init.ps unless you really know what you are doing. > >fsfacca@LERC08.NAS.NASA.GOV (Tony Facca) writes: >> I agree that init.ps is not a file which should be modified. > >OK, so I suppose you could figure out a way to modify the size and font >of the default window using PostScript in user.ps, but for me, it was a >lot easier looking it up in init.ps, and changing the window to be 40x80 >in font ScreenBold. Have I committed a deadly sin? > Yes, and you >>will<< burn forever in H-E double toothpicks for it :-). Whenever I want to modify the behavior of something I first look in the standard PostScript files to see how its done. Then I copy the code to my user.ps, and make modifications there. This usually works, and it preserves my changes arcross releases. To change the console you can just copy the code from init.ps to user.ps, and change the font, placement, etc... There should be an example of this particular technique in the 4Dgifts account, by the by. Archer Sully (archer@sgi.com) "life is short, filled with stuff" -- Lux Interior
msc@ramoth.sgi.com (Mark Callow) (05/25/89)
In article <3172@watale.waterloo.edu>, tom@mims-iris.uucp (Tom Haapanen) writes: > > Mark Callow <sgi!msc%ramoth.SGI.COM@ucbvax.berkeley.edu> writes: > >> No, no, no! Never edit init.ps unless you really know what you are doing. > > fsfacca@LERC08.NAS.NASA.GOV (Tony Facca) writes: > > I agree that init.ps is not a file which should be modified. > > OK, so I suppose you could figure out a way to modify the size and font > of the default window using PostScript in user.ps, but for me, it was a > lot easier looking it up in init.ps, and changing the window to be 40x80 > in font ScreenBold. Have I committed a deadly sin? Here's the appropriate PostScript from my user.ps % % Customize console % /RunConsole { (/etc/gl/startconsole -r1000 -s24x68 -m60x80 -fScreen.8) forkunix } store (console) 10 12 preforigin Now I don't have to worry if init.ps changes from release to release. My window configuration still comes up the way I"m used to. There are 2 issues with modifying init.ps: you are not protected against mistakes; you could disable 4Sight. you have to keep making your changes with each new release. > > (The default window size/placement is very annoying, as the pointer is > initially outside the window, so the window isn't active & you can't type). This is a bug. It is fixed in Release 3.2. -- -Mark