How to increase the editor display length?

[karthikeyan mahalingam]

Whenever i open the editor (lsedit, edit/tpu, edit/eve), the width is 132/80,but the length is usually half the screen. Is there any way to increase the length of display in the editors. The terminal properties and the editor display is in the attachment.

[P Muralidhar Kini · Accepted solution]

Hi Karthikeyan,

I generally execute the command "SET TERM/INQ/ANSI/INS/WIDTH=132"
and then open the editor. It works for me and I get a full screen display. The "/INQ" and "/ANSI" qualifier is what will increase the screen length i guess.
You can have that command in your login script (LOGIN.COM) so that it happens automatically every time.

Regards,
Murali

[karthikeyan mahalingam]

Hi Murali

It worked. I googled it, but there was nothing about /ins.
Thanks much.

[P Muralidhar Kini]

Hi Karthikeyan,

>> It worked. I googled it, but there was nothing about /ins.
The "/INS" (i.e. /INSERT) would set the terminal to INSERT mode
rather than OVERSTRIKE mode.

please refer DCL HELP on "SET TERM" for more details.
i.e issue the following command from DCL prompt
$HELP SET TERM

Regards,
Murali

[Bart Zorn_1]

As you can see with HELP SET TERMINAL, /ANSI does not set the line width. Neither does /INQ. The latter issues a request to the terminal(-emulator) to report its characteristics back to the OS. IF the line width of the terminal is 132, the line width in the OS will also be set to 132.

You seem to be using a magic incantation which does what you want, but you have no idea why it does so!

HTH,

Bart

[Steven Schweda]

> Whenever i open the editor [...]

Using _what_ as a terminal (or terminal
emulator)?

> [...] half the screen. [...]

What is "the screen"?

> [...] the attachment.

".doc"? A Microsoft Word document? Who is
your target audience? Windows users?


> I generally execute the command "SET
> TERM/INQ/ANSI/INS/WIDTH=132" and then open
> the editor.

I usually use an editor (EDIT /TPU) command
like "[Do] SET WIDTH 200". Doing this
_after_ I'm in the editor means that the
terminal (normally a DECterm on my Alpha
workstation "New Desktop") gets restored to
its original size when I exit the editor.
(Its position is normally messed up some, but
at least some things get restored.)

I normally don't care about height, but with
EDIT /TPU, it's possible to enlarge a DECterm
window before running the editor. (If I want
more height, I often use Vim: "gvim -geom
80x48".)

EDT (EDIT /EDT) has a [Gold KP7] SET SCREEN
command, but I think that EDT can't do a
width bigger than 132 (or a height bigger
than 24).

I don't use LSE enough to care, but you might
try HELP and/or the manual.

[karthikeyan mahalingam]

Steven,

I use the putty session from a windows PC to logon to the OpenVMS system.
The attachment is .doc

Bart,
I guess the /INQ works solves the purpose, because of the following description.

/INQUIRE

Sets the device type when the /INQUIRE qualifier is specified
and the DEC_CRT characteristic is set. The SET TERMINAL command
reads the current screen size from the terminal and sets the
corresponding page length and page width values appropriately.

After the terminal/screen is maximized and do set term/inq/ansi_crt/ins/width=132, the current size is picked from the terminal and it set for the editor.

Please, correct me, if I am wrong.

[P Muralidhar Kini]

Hi Karthikeyan,

Yes. thats correct.
You can put that command in the LOGIN.COM command procedure in your login directory so that it gets executed automatically every time you login (if thats what you want).

Regards,
Murali

[H.Becker]

As VMS user you very likely have in your login.com a section starting with two lines like

$ if f$mode() .eqs "INTERACTIVE"
$ then

You want to put the set terminal command in that section.

[P Muralidhar Kini]

Hi Becker,

>> if f$mode() .eqs "INTERACTIVE"
Thats a good suggestion.

I guess doing this would make the commands get executed only in interactive
mode. So a batch job for example running from this user account would not
execute those commands. Is that correct.

Regards,
Murali

[Hein van den Heuvel]

Right You want the $ SET TERM/INQ only to happen for interactive sessions with terminal to talk to.

If this is a batch job, then the command targets SYS$INPUT which is the file.
That results in errors like:

%SET-W-NOTSET, error modifying Dxxxx:
-SET-E-INVDEV, device is invalid for requested operation

Nothing will 'break' or be damaged, but it is needless and ugly.

Hein

[P Muralidhar Kini]

Hi Hein,

>> %SET-W-NOTSET, error modifying Dxxxx:
>> -SET-E-INVDEV, device is invalid for requested operation

Thats great. I had this question in mind.
I run some of my test scripts as batch jobs and used to get this message
lot of times and as you said the message will get logged but the batch
job would continue to run and do its job.
But its a needless & ugly message indeed.

I would be chaning my login procedure very soon.

Thanks Becker & Hein.

Regards,
Murali

[John Gillings]

I've attached a zipped saveset of a Alpha and IA64 versions of a program called SET_TERM_INQUIRE the source of which is lost in the mysts of time. I think the IA64 version is translated.

Execute the program from LOGIN.COM - it will set the terminal page and width to match your your terminal, or emulator, and also the terminal type (somewhat more accurately than SET TERMINAL/INQUIRE).

It's a silent NOOP if executed from BATCH, NETWORK or anywhere else that SYS$COMMAND is a non-terminal device, so you don't need to perform any tests.

One of my "must haves" on any OpenVMS system.

[Hoff]

Two sources for the SET_TERM_INQUIRE source code:

http://www.mpp.mpg.de/~huber/vmssig/src/C/

http://www.decuslib.com/decus/vax92a/munic_s92/set_term_inq/

If you want to read some about the tool:

http://www.mpp.mpg.de/~huber/vmssig/src/C/SET_TERM_INQUIRE.TXT