gil@daffy.gatech.edu (Gil Neiger) (10/05/89)
I would like to have a Terminal window launch itself at startup and for it to be in the same place every time I log in. Using dwrite I find that I can only control where the next Terminal window will start; after that, the default locations are both incremented by 24. The dock doesn't allow me to specify options or flags to a command, so I'm not sure what I can do. - Gil Neiger gil@gatech.edu
ags@seaman.cc.purdue.edu (Dave Seaman) (10/05/89)
In article <2276@hydra.gatech.EDU> gil@gatech.edu (Gil Neiger) writes: >I would like to have a Terminal window launch itself at startup and for it >to be in the same place every time I log in. Using dwrite I find that I >can only control where the next Terminal window will start; after that, >the default locations are both incremented by 24. The dock doesn't allow >me to specify options or flags to a command, so I'm not sure what I can do. That is indeed an irritating problem. The default locations are also changed when you move a window. My workaround is to put the appropriate dwrite commands into my .login (to handle the change that takes effect whenever a new terminal window is opened) and also into my .logout (to handle the case when a window is moved). Ouch! Why doesn't somebody work on adding scrolling capability, instead of putting in such howling misfeatures as this? -- Dave Seaman ags@seaman.cc.purdue.edu
mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) (10/05/89)
In article <2276@hydra.gatech.EDU> gil@gatech.edu (Gil Neiger) writes: >I would like to have a Terminal window launch itself at startup and for it >to be in the same place every time I log in. Using dwrite I find that I >can only control where the next Terminal window will start; after that, >the default locations are both incremented by 24. The dock doesn't allow >me to specify options or flags to a command, so I'm not sure what I can do. I have the same problem; although the incrementing by [24.24] for subsequent Terminal windows is nice in principle, it keeps me from having my Terminal windows positioned where I really want them when I first log in. I worked around the problem by adding dwrite Terminal WinLocX 563 dwrite Terminal WinLocY -4 to my .login file. So, as long as I'm careful not to move the Terminal window (which seems to have the effect of setting the dock variables to new location + [24.24]) I'm alright. I agree with another poster that Terminal is highly unsatisfactory. It is not a VT100 emulator; it emulates something that is similar to a VT100. It works poorly with other Unix systems (a quick comparison of the NeXT "VT100" termcap with a real VT100 termcap will show you why!) and even worse with non-Unix systems. It should also allow PostScript previewing through the terminal emulator (e.g. make it an "ANSI terminal with PostScript support"). My guess is that most internal users at NeXT use Shell. If Shell let me run EMACS I would use it too. The right way to fix this would be to put true ANSI support in the Text object (or a subclass of the Text object), and allow a user to direct standard input and output to/from this object. This would be a big step towards resolving many Unix users' complaints about poor Unix/NeXTStep integration. I'd do something like this myself except that nobody's paying me to do it... Mark Crispin / 6158 Lariat Loop NE / Bainbridge Island, WA 98110-2020 mrc@CAC.Washington.EDU / MRC@WSMR-SIMTEL20.Army.Mil / (206) 842-2385 Atheist & Proud / 450cc Rebel pilot -- a step up from 250cc's!!! tabesaserarenakerebanaranakattarashii...kisha no kisha ga kisha de kisha-shita sumomo mo momo, momo mo momo, momo ni mo iroiro aru uraniwa ni wa niwa, niwa ni wa niwa niwatori ga iru
abe@mace.cc.purdue.edu (Vic Abell) (10/05/89)
In article <2276@hydra.gatech.EDU> gil@gatech.edu (Gil Neiger) writes: >I would like to have a Terminal window launch itself at startup and for it >to be in the same place every time I log in. Have you tried using the Pseudo and window-position programs that Greg Couch posted to this news group in July, 1989? Pseudo allows you to specify arguments to auto-launched applications. Window-position generates a random window position. Although the programs were done for the 0.9 release, updating them to 1.0 only requires changing the Terminal location option names in window-position from WinLocH/WinLocV to WinLocX/WinLocY and adding the NXFixedPitch prefix to the examples for the Terminal application font arguments in Pseudo(1). I want to express my public thanks to Greg for a very useful contribution to NeXTing.
klamb@csm9a.UUCP (Kathleen Lamb) (10/05/89)
If you use the menu command quit, or command-q to leave the Terminal window, then it will come up in the same position the next time. So if you can break yourself of typing "logout" or control-d, your problem is fixed. Unless, of course, your account is on a NeXT client/server cluster, and you're sometimes running Terminal on more than one cube at a time - then you will still have Terminal windows coming up offset from where you may want them.
ags@seaman.cc.purdue.edu (Dave Seaman) (10/07/89)
In article <1928@csm9a.UUCP> klamb@csm9a.UUCP (Kathleen Lamb) writes: >If you use the menu command quit, or command-q to leave the Terminal window, >then it will come up in the same position the next time. That might work if you can remember to quit only the original terminal window (the one that was autolaunched by the window manager) and to avoid doing this with any other terminal windows (or at least to quit the autolaunched terminal last). -- Dave Seaman ags@seaman.cc.purdue.edu