Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucsd!ogccse!blake!Tomobiki-Cho!mrc
From: mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin)
Newsgroups: comp.sys.next
Subject: Re: Terminal Window Location
Message-ID: <3913@blake.acs.washington.edu>
Date: 4 Oct 89 20:59:35 GMT
References: <2276@hydra.gatech.EDU>
Sender: news@blake.acs.washington.edu
Organization: Mendou Zaibatsu, Tomobiki-Cho, Butsumetsu-Shi
Lines: 43

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