From: tillman@swdev.si.com ("Brian Tillman, Smiths Industries, VAX Support, x8425")
Newsgroups: comp.os.vms
Subject: RE: Q: LSEdit with DECwindows configuration
Date: 28 Aug 92 13:03:35 GMT
Organization: The Internet

I assume you are using LSE V3.1 (I don't know if V4.0 is shipping yet or not, 
although it's close).  In either case, you can position the window using the 
following two resources:

Tpu.Tpu$MainWindow.X: x-value
Tpu.Tpu$MainWindow.Y: y-value

If you are using V3.1, you can also establish the screen height with the 
following resource:

Tpu.Tpu$MainWindow.Rows: n

There is also a Tpu.Tpu$MainWindow.IconName and Tpu.Tpu$MainWindow.Title 
resource.  Put these resources in a file and define the logical name 
LSE$DEFAULTS to point to it.  The default file type is .DAT, as you'd expect.

If you are using V4.0, there seems to be a problem with the .Rows resource.  You 
might be successful if you spell it .rows (keeping everything else in the 
previously demonstrated case) - DEC was able to make this work, but I haven't.  
Instead, I found that I also needed to SET SCREEN HEIGHT=nn (where "nn" is my 
preferred height), save the options to a command file, define LSE$COMMAND to 
point to that file, and have my .Rows resource be five less than the screen 
height.  The .Rows seems to control the size of the edit region, whereas the 
screen height is the number of rows in the entire window.  The edit region is 
always five less than the screen height, anyway. (one line for the horizontal 
scroll bar, one line for the status line, and three lines for the command 
window).

One feature of V4.0 is that it can run on VMS or Ultrix (different kits, of 
course) and have the exact same command syntax.  This is called Portable LSE.  
DEC has changed the name, too, to DEC LSE.  You can choose the VMS-style 
commands so it is compatible with V3.1 or you can select the Portable command 
language (on an individual basis).  I use the Portable language, so my *real* 
command for changing the height is SET HEIGHT nn (instead of the example above, 
which is the VMS-style command).  Other examples of command differences are:

	set left_margin nn	is now		set buffer left margin nn
	set right_margin nn			set buffer right margin nn
	align/comment_column=n			align n
	call procedure params			tpu procedure params
	capitalize word				capitalize
	cut/append				cut append
	cut/noerase				copy
	dcl command				cli command
	define key keyname lse-command		new key keyname lse-command

and so on.  There are quite a few changes.  The main reason for these changes 
seems to have been to eliminate similarity to DCL, turning qualifiers into 
parameters.  Some of the changes (like the SET LEFT and SET RIGHT) seem to be 
just to make things more verbose, but the designers obviously thought that a 
more mnemonic grouping of commands would help.  Sometimes they succeeded, and 
sometimes not, but on the whole, someone jumping between VMS and Unix will have 
an easier time.

For those that don't have V4.0 yet, I'll be glad to answer questions.

-----------------------------+--------------------------------
 Brian Tillman               | Internet: tillman@swdev.si.com
 Smiths Industries, Inc.     |
 4141 Eastern Ave., MS129    | Hey, I said this stuff myself.
 Grand Rapids, MI 49518-8727 | My company has no part in it.
-----------------------------+--------------------------------