On 9/22/2022 10:36 AM, Johnny Billquist wrote:
> On 2022-09-22 15:14, Single Stage to Orbit wrote:
>> On Thu, 2022-09-22 at 12:41 +0000, Simon Clubley wrote:
>>> On 2022-09-21, gah4 <gah4@u.washington.edu> wrote:
>>>> On Tuesday, September 20, 2022 at 6:31:17 AM UTC-7,
>>>> alanfe...@gmail.com wrote:
>>>>
>>>> Does VMS know about xterm-256color?
>>>
>>> I doubt it. :-)
>>>
>>> Try setting TERM to vt220 and see if that makes a difference.
>>>
>>> BTW, it would be nice if VMS did support colour. The z/OS style
>>> command output would make the VMS command output much more readable
>>> instead of the monochrome output you get with VMS.
>>
>> VT100 supports ANSI color codes. In theory you should be able to do
>> this in VMS provided the terminal can parse these color codes.
>
> Uh? A VT100 don't support ANSI color codes. A VT100 is very monochrome.
> But technically, any application that want to play with color can always
> send the escape sequences required to make them happen. VMS isn't really
> involved here.
>
> xterm do support colors, as do the VT525, using ANSI color codes.

VT241 and VT340 was also color - I don't know if they supported
ANSI color escape sequences.

Arne

On 2022-09-23 00:44, Arne Vajhøj wrote:
> On 9/22/2022 10:36 AM, Johnny Billquist wrote:
>> On 2022-09-22 15:14, Single Stage to Orbit wrote:
>>> On Thu, 2022-09-22 at 12:41 +0000, Simon Clubley wrote:
>>>> On 2022-09-21, gah4 <gah4@u.washington.edu> wrote:
>>>>> On Tuesday, September 20, 2022 at 6:31:17 AM UTC-7,
>>>>> alanfe...@gmail.com wrote:
>>>>>
>>>>> Does VMS know about xterm-256color?
>>>>
>>>> I doubt it. :-)
>>>>
>>>> Try setting TERM to vt220 and see if that makes a difference.
>>>>
>>>> BTW, it would be nice if VMS did support colour. The z/OS style
>>>> command output would make the VMS command output much more readable
>>>> instead of the monochrome output you get with VMS.
>>>
>>> VT100 supports ANSI color codes. In theory you should be able to do
>>> this in VMS provided the terminal can parse these color codes.
>>
>> Uh? A VT100 don't support ANSI color codes. A VT100 is very monochrome.
>> But technically, any application that want to play with color can
>> always send the escape sequences required to make them happen. VMS
>> isn't really involved here.
>>
>> xterm do support colors, as do the VT525, using ANSI color codes.
>
> VT241 and VT340 was also color - I don't know if they supported
> ANSI color escape sequences.

They don't. They can only switch colors if you go into ReGIS mode. No
ANSI escape sequences for playing with colors.

Johnny

On 9/22/2022 5:06 PM, alanfe...@gmail.com wrote:
> On Thursday, September 22, 2022 at 4:11:02 AM UTC-4, Johnny Billquist wrote:
>> On 2022-09-21 11:54, alanfe...@gmail.com wrote:
>>> On Wednesday, September 21, 2022 at 4:51:41 AM UTC-4, Johnny Billquist wrote:
>>>> On 2022-09-20 21:57, Steven Schweda wrote:
>>>>>> Am I the only one in the newsgroup that uses a Mac to access an
>>>>>> OpenVMS box?

Many do. I use iterm2 which was a pain to configure correctly, but it
works correctly for me other than the fact the fn and PF2 keys don't
work, but I don't use them.

> The only problem I have with Terminal is that using EDT in full-screen mode wipes out part of the history buffer (not the commands, but screen output).

I noticed something like that with iterm2, not elsewhere, I'll look at
EDT to see what's up.

On 2022-09-23 21:16, Michael Moroney wrote:
> On 9/22/2022 5:06 PM, alanfe...@gmail.com wrote:
>> The only problem I have with Terminal is that using EDT in full-screen
>> mode wipes out part of the history buffer (not the commands, but
>> screen output).
>
> I noticed something like that with iterm2, not elsewhere, I'll look at
> EDT to see what's up.

Not sure what you are referring to. EDT clears the screen in order to
draw whatever it wants to show there. So of course, whatever else was
there before is gone.

Or are you referring to something else?

Johnny

On Friday, September 23, 2022 at 4:34:55 PM UTC-4, Johnny Billquist wrote:
> On 2022-09-23 21:16, Michael Moroney wrote:
> > On 9/22/2022 5:06 PM, alanfe...@gmail.com wrote:
> >> The only problem I have with Terminal is that using EDT in full-screen
> >> mode wipes out part of the history buffer (not the commands, but
> >> screen output).
> >
> > I noticed something like that with iterm2, not elsewhere, I'll look at
> > EDT to see what's up.
> Not sure what you are referring to. EDT clears the screen in order to
> draw whatever it wants to show there. So of course, whatever else was
> there before is gone.
>
> Or are you referring to something else?
>
> Johnny

Say I run SHOW SYSTEM on EISNER. It's like a hundred-something lines. Say it's 160 lines. I run EDT. It clears the screen, brings up the file, I do my edits, and exit. Now I page-up to review the SHOW SYSTEM output, and the l last 30 or 40 or whatever lines are gone. If I had instead run, say, SH DEV DS, I get what,10 lines of output? Then I do a full-screen editing session. Then I page-up to see the SH DEV DS output again, and it's gone. Older stuff is still there, but the last n lines of what was there before I edited something is gone for good. Maybe you never do the page-up bit to see previous commands and their outputs.

Alan.

On 9/23/2022 11:13 PM, alanfe...@gmail.com wrote:

> Say I run SHOW SYSTEM on EISNER. It's like a hundred-something lines. Say
> it's 160 lines. I run EDT. It clears the screen, brings up the file, I do my
> edits, and exit. Now I page-up to review the SHOW SYSTEM output, and the l
> last 30 or 40 or whatever lines are gone. If I had instead run, say, SH DEV
> DS, I get what,10 lines of output? Then I do a full-screen editing session.
> Then I page-up to see the SH DEV DS output again, and it's gone. Older stuff
> is still there, but the last n lines of what was there before I edited
> something is gone for good. Maybe you never do the page-up bit to see
> previous commands and their outputs.

It's your emulator.

I use EDT regularly and frequently scroll back to see previous output (whilst
in the editor and after exiting it). I always see the output that had been
displayed prior to the editing session.

I use PowerTerm for an emulator.

--

--- Rob

On Friday, September 23, 2022 at 11:24:48 PM UTC-4, Robert A. Brooks wrote:
> On 9/23/2022 11:13 PM, alanfe...@gmail.com wrote:
>
> > Say I run SHOW SYSTEM on EISNER. It's like a hundred-something lines. Say
> > it's 160 lines. I run EDT. It clears the screen, brings up the file, I do my
> > edits, and exit. Now I page-up to review the SHOW SYSTEM output, and the l
> > last 30 or 40 or whatever lines are gone. If I had instead run, say, SH DEV
> > DS, I get what,10 lines of output? Then I do a full-screen editing session.
> > Then I page-up to see the SH DEV DS output again, and it's gone. Older stuff
> > is still there, but the last n lines of what was there before I edited
> > something is gone for good. Maybe you never do the page-up bit to see
> > previous commands and their outputs.
> It's your emulator.
>
> I use EDT regularly and frequently scroll back to see previous output (whilst
> in the editor and after exiting it). I always see the output that had been
> displayed prior to the editing session.

Fascinating. I just tried it using EDIT/TPU, and it works fine. It just fails with EDT. I guess the problem only happens running EDT in Terminal!

>
> I use PowerTerm for an emulator.

I don't.

Thanks for checking!
>
> --
>
> --- Rob

Alan

Den 2022-09-24 kl. 06:06, skrev alanfe...@gmail.com:
> On Friday, September 23, 2022 at 11:24:48 PM UTC-4, Robert A. Brooks wrote:
>> On 9/23/2022 11:13 PM, alanfe...@gmail.com wrote:
>>
>>> Say I run SHOW SYSTEM on EISNER. It's like a hundred-something lines. Say
>>> it's 160 lines. I run EDT. It clears the screen, brings up the file, I do my
>>> edits, and exit. Now I page-up to review the SHOW SYSTEM output, and the l
>>> last 30 or 40 or whatever lines are gone. If I had instead run, say, SH DEV
>>> DS, I get what,10 lines of output? Then I do a full-screen editing session.
>>> Then I page-up to see the SH DEV DS output again, and it's gone. Older stuff
>>> is still there, but the last n lines of what was there before I edited
>>> something is gone for good. Maybe you never do the page-up bit to see
>>> previous commands and their outputs.
>> It's your emulator.
>>
>> I use EDT regularly and frequently scroll back to see previous output (whilst
>> in the editor and after exiting it). I always see the output that had been
>> displayed prior to the editing session.
>
> Fascinating. I just tried it using EDIT/TPU, and it works fine. It just fails with EDT. I guess the problem only happens running EDT in Terminal!
>
>
>>
>> I use PowerTerm for an emulator.
>
> I don't.
>
> Thanks for checking!
>>
>> --
>>
>> --- Rob
>
> Alan

Works just fine with EDT and Putty.

Here I did SHO SYS, picked up my LOGIN.COM file in EDT,
switched to full screen, did quit from EDT and finaly
just scrolled back my screen session in Putty.

The PACK11_PLC process was the last line from SHO SYS before
EDT was started. It is still there in the scroll-back buffer
after exiting EDT.

00009206 PACK_11 LEF 11 2957 0 00:00:00.44 1752 1458
00009A07 PACK_11PLC LEF 11 2357 0 00:00:00.40 1946 1648
$ edit/edt login.com
1 $!-----------------------------------------!
*c
$!-----------------------------------------!
$! LOGIN FILE FOR USER: EDED
$!-----------------------------------------!
...
...
<ctrl-Z>
*quit

$

On Saturday, September 24, 2022 at 9:03:22 AM UTC-4, Jan-Erik Söderholm wrote:
> Den 2022-09-24 kl. 06:06, skrev alanfe...@gmail.com:
> > On Friday, September 23, 2022 at 11:24:48 PM UTC-4, Robert A. Brooks wrote:
> >> On 9/23/2022 11:13 PM, alanfe...@gmail.com wrote:
> >>
> >>> Say I run SHOW SYSTEM on EISNER. It's like a hundred-something lines. Say
> >>> it's 160 lines. I run EDT. It clears the screen, brings up the file, I do my
> >>> edits, and exit. Now I page-up to review the SHOW SYSTEM output, and the l
> >>> last 30 or 40 or whatever lines are gone. If I had instead run, say, SH DEV
> >>> DS, I get what,10 lines of output? Then I do a full-screen editing session.
> >>> Then I page-up to see the SH DEV DS output again, and it's gone. Older stuff
> >>> is still there, but the last n lines of what was there before I edited
> >>> something is gone for good. Maybe you never do the page-up bit to see
> >>> previous commands and their outputs.
> >> It's your emulator.
> >>
> >> I use EDT regularly and frequently scroll back to see previous output (whilst
> >> in the editor and after exiting it). I always see the output that had been
> >> displayed prior to the editing session.
> >
> > Fascinating. I just tried it using EDIT/TPU, and it works fine. It just fails with EDT. I guess the problem only happens running EDT in Terminal!
> >
> >
> >>
> >> I use PowerTerm for an emulator.
> >
> > I don't.
> >
> > Thanks for checking!
> >>
> >> --
> >>
> >> --- Rob
> >
> > Alan
> Works just fine with EDT and Putty.
>
> Here I did SHO SYS, picked up my LOGIN.COM file in EDT,
> switched to full screen, did quit from EDT and finaly
> just scrolled back my screen session in Putty.
>
> The PACK11_PLC process was the last line from SHO SYS before
> EDT was started. It is still there in the scroll-back buffer
> after exiting EDT.
>
>
> 00009206 PACK_11 LEF 11 2957 0 00:00:00.44 1752 1458
> 00009A07 PACK_11PLC LEF 11 2357 0 00:00:00.40 1946 1648
> $ edit/edt login.com
> 1 $!-----------------------------------------!
> *c
> $!-----------------------------------------!
> $! LOGIN FILE FOR USER: EDED
> $!-----------------------------------------!
> ..
> ..
> <ctrl-Z>
> *quit
>
> $

Thank you, gentlemen!

On Saturday, September 24, 2022 at 9:03:22 AM UTC-4, Jan-Erik Söderholm wrote:
> Den 2022-09-24 kl. 06:06, skrev alanfe...@gmail.com:
> > On Friday, September 23, 2022 at 11:24:48 PM UTC-4, Robert A. Brooks wrote:
> >> On 9/23/2022 11:13 PM, alanfe...@gmail.com wrote:
> >>
[...]
> >
> > Alan
> Works just fine with EDT and Putty.
>
> Here I did SHO SYS, picked up my LOGIN.COM file in EDT,
> switched to full screen, did quit from EDT and finaly
> just scrolled back my screen session in Putty.
>
> The PACK11_PLC process was the last line from SHO SYS before
> EDT was started. It is still there in the scroll-back buffer
> after exiting EDT.
>
>
> 00009206 PACK_11 LEF 11 2957 0 00:00:00.44 1752 1458
> 00009A07 PACK_11PLC LEF 11 2357 0 00:00:00.40 1946 1648
> $ edit/edt login.com
> 1 $!-----------------------------------------!
> *c
> $!-----------------------------------------!
> $! LOGIN FILE FOR USER: EDED
> $!-----------------------------------------!
> ..
> ..
> <ctrl-Z>
> *quit
>
> $

Did you scroll up and down during your EDT session?

On 2022-09-24 05:13, alanfe...@gmail.com wrote:
> On Friday, September 23, 2022 at 4:34:55 PM UTC-4, Johnny Billquist wrote:
>> On 2022-09-23 21:16, Michael Moroney wrote:
>>> On 9/22/2022 5:06 PM, alanfe...@gmail.com wrote:
>>>> The only problem I have with Terminal is that using EDT in full-screen
>>>> mode wipes out part of the history buffer (not the commands, but
>>>> screen output).
>>>
>>> I noticed something like that with iterm2, not elsewhere, I'll look at
>>> EDT to see what's up.
>> Not sure what you are referring to. EDT clears the screen in order to
>> draw whatever it wants to show there. So of course, whatever else was
>> there before is gone.
>>
>> Or are you referring to something else?
>>
>> Johnny
>
> Say I run SHOW SYSTEM on EISNER. It's like a hundred-something lines. Say it's 160 lines. I run EDT. It clears the screen, brings up the file, I do my edits, and exit. Now I page-up to review the SHOW SYSTEM output, and the l last 30 or 40 or whatever lines are gone. If I had instead run, say, SH DEV DS, I get what,10 lines of output? Then I do a full-screen editing session. Then I page-up to see the SH DEV DS output again, and it's gone. Older stuff is still there, but the last n lines of what was there before I edited something is gone for good. Maybe you never do the page-up bit to see previous commands and their outputs.

The last 30-40 lines (the screen size I would guess) would be gone,
since those lines were reused by EDT. Anything that was off the top of
the screen are no longer active, and can't be overwritten, so they stay
around.

On newer terminal emulators, there exists an escape sequence to switch
to an alternative window, which some applications use, so that all
current screen content remains. I highly doubt EDT knows about, or uses
that escape sequence. But I have a feeling that is what you are thinking
of/hoping for. Some other, newer editors, would be using that when possible.

A real VT terminal do not have that alternative window, so it's
something that DEC never played with.

Johnny

On Saturday, September 24, 2022 at 11:38:53 AM UTC-4, Johnny Billquist wrote:
> On 2022-09-24 05:13, alanfe...@gmail.com wrote:
> > On Friday, September 23, 2022 at 4:34:55 PM UTC-4, Johnny Billquist wrote:
> >> On 2022-09-23 21:16, Michael Moroney wrote:
> >>> On 9/22/2022 5:06 PM, alanfe...@gmail.com wrote:
> >>>> The only problem I have with Terminal is that using EDT in full-screen
> >>>> mode wipes out part of the history buffer (not the commands, but
> >>>> screen output).
> >>>
> >>> I noticed something like that with iterm2, not elsewhere, I'll look at
> >>> EDT to see what's up.
> >> Not sure what you are referring to. EDT clears the screen in order to
> >> draw whatever it wants to show there. So of course, whatever else was
> >> there before is gone.
> >>
> >> Or are you referring to something else?
> >>
> >> Johnny
> >
> > Say I run SHOW SYSTEM on EISNER. It's like a hundred-something lines. Say it's 160 lines. I run EDT. It clears the screen, brings up the file, I do my edits, and exit. Now I page-up to review the SHOW SYSTEM output, and the l last 30 or 40 or whatever lines are gone. If I had instead run, say, SH DEV DS, I get what,10 lines of output? Then I do a full-screen editing session. Then I page-up to see the SH DEV DS output again, and it's gone. Older stuff is still there, but the last n lines of what was there before I edited something is gone for good. Maybe you never do the page-up bit to see previous commands and their outputs.
> The last 30-40 lines (the screen size I would guess) would be gone,
> since those lines were reused by EDT. Anything that was off the top of
> the screen are no longer active, and can't be overwritten, so they stay
> around.
>
> On newer terminal emulators, there exists an escape sequence to switch
> to an alternative window, which some applications use, so that all
> current screen content remains. I highly doubt EDT knows about, or uses
> that escape sequence. But I have a feeling that is what you are thinking
> of/hoping for. Some other, newer editors, would be using that when possible.
>
> A real VT terminal do not have that alternative window, so it's
> something that DEC never played with.
>
> Johnny

Yep, it works fine with TPU. One then needs to put it in a DCL jacket with the right secret escape sequence, or get one of these newfangled terminal emulators.

On 2022-09-24 21:36, alanfe...@gmail.com wrote:
> On Saturday, September 24, 2022 at 11:38:53 AM UTC-4, Johnny Billquist wrote:
>> On 2022-09-24 05:13, alanfe...@gmail.com wrote:
>>> On Friday, September 23, 2022 at 4:34:55 PM UTC-4, Johnny Billquist wrote:
>>>> On 2022-09-23 21:16, Michael Moroney wrote:
>>>>> On 9/22/2022 5:06 PM, alanfe...@gmail.com wrote:
>>>>>> The only problem I have with Terminal is that using EDT in full-screen
>>>>>> mode wipes out part of the history buffer (not the commands, but
>>>>>> screen output).
>>>>>
>>>>> I noticed something like that with iterm2, not elsewhere, I'll look at
>>>>> EDT to see what's up.
>>>> Not sure what you are referring to. EDT clears the screen in order to
>>>> draw whatever it wants to show there. So of course, whatever else was
>>>> there before is gone.
>>>>
>>>> Or are you referring to something else?
>>>>
>>>> Johnny
>>>
>>> Say I run SHOW SYSTEM on EISNER. It's like a hundred-something lines. Say it's 160 lines. I run EDT. It clears the screen, brings up the file, I do my edits, and exit. Now I page-up to review the SHOW SYSTEM output, and the l last 30 or 40 or whatever lines are gone. If I had instead run, say, SH DEV DS, I get what,10 lines of output? Then I do a full-screen editing session. Then I page-up to see the SH DEV DS output again, and it's gone. Older stuff is still there, but the last n lines of what was there before I edited something is gone for good. Maybe you never do the page-up bit to see previous commands and their outputs.
>> The last 30-40 lines (the screen size I would guess) would be gone,
>> since those lines were reused by EDT. Anything that was off the top of
>> the screen are no longer active, and can't be overwritten, so they stay
>> around.
>>
>> On newer terminal emulators, there exists an escape sequence to switch
>> to an alternative window, which some applications use, so that all
>> current screen content remains. I highly doubt EDT knows about, or uses
>> that escape sequence. But I have a feeling that is what you are thinking
>> of/hoping for. Some other, newer editors, would be using that when possible.
>>
>> A real VT terminal do not have that alternative window, so it's
>> something that DEC never played with.
>>
>> Johnny
>
> Yep, it works fine with TPU. One then needs to put it in a DCL jacket with the right secret escape sequence, or get one of these newfangled terminal emulators.

You need both a new fangled termina emulator, *and* an editor which
switches to this alternative screen.

A little surprised TPU knows about it, but I guess maybe because of
xterm and the VXT terminals, it already was around in the later days of
DEC software?

Johnny

Den 2022-09-24 kl. 17:26, skrev alanfe...@gmail.com:
> On Saturday, September 24, 2022 at 9:03:22 AM UTC-4, Jan-Erik Söderholm wrote:
>> Den 2022-09-24 kl. 06:06, skrev alanfe...@gmail.com:
>>> On Friday, September 23, 2022 at 11:24:48 PM UTC-4, Robert A. Brooks wrote:
>>>> On 9/23/2022 11:13 PM, alanfe...@gmail.com wrote:
>>>>
> [...]
>>>
>>> Alan
>> Works just fine with EDT and Putty.
>>
>> Here I did SHO SYS, picked up my LOGIN.COM file in EDT,
>> switched to full screen, did quit from EDT and finaly
>> just scrolled back my screen session in Putty.
>>
>> The PACK11_PLC process was the last line from SHO SYS before
>> EDT was started. It is still there in the scroll-back buffer
>> after exiting EDT.
>>
>>
>> 00009206 PACK_11 LEF 11 2957 0 00:00:00.44 1752 1458
>> 00009A07 PACK_11PLC LEF 11 2357 0 00:00:00.40 1946 1648
>> $ edit/edt login.com
>> 1 $!-----------------------------------------!
>> *c
>> $!-----------------------------------------!
>> $! LOGIN FILE FOR USER: EDED
>> $!-----------------------------------------!
>> ..
>> ..
>> <ctrl-Z>
>> *quit
>>
>> $
>
> Did you scroll up and down during your EDT session?

Just tried with a larger file (than my LOGIN.COM) and jumped
up and down in it within EDT. I could still scroll back to my
previous screen content before I entered EDT.

EDT is my prefered editor and I would definitely had seen this
if it had been a problem. So, no, I have never seen this problem.
And I have used Reflection, Extra! and Putty over the years.

On Saturday, September 24, 2022 at 5:16:33 PM UTC-4, Jan-Erik Söderholm wrote:
> Den 2022-09-24 kl. 17:26, skrev alanfe...@gmail.com:
> > On Saturday, September 24, 2022 at 9:03:22 AM UTC-4, Jan-Erik Söderholm wrote:
> >> Den 2022-09-24 kl. 06:06, skrev alanfe...@gmail.com:
> >>> On Friday, September 23, 2022 at 11:24:48 PM UTC-4, Robert A. Brooks wrote:
> >>>> On 9/23/2022 11:13 PM, alanfe...@gmail.com wrote:
> >>>>
> > [...]
> >>>
> >>> Alan
> >> Works just fine with EDT and Putty.
> >>
> >> Here I did SHO SYS, picked up my LOGIN.COM file in EDT,
> >> switched to full screen, did quit from EDT and finaly
> >> just scrolled back my screen session in Putty.
> >>
> >> The PACK11_PLC process was the last line from SHO SYS before
> >> EDT was started. It is still there in the scroll-back buffer
> >> after exiting EDT.
> >>
> >>
> >> 00009206 PACK_11 LEF 11 2957 0 00:00:00.44 1752 1458
> >> 00009A07 PACK_11PLC LEF 11 2357 0 00:00:00.40 1946 1648
> >> $ edit/edt login.com
> >> 1 $!-----------------------------------------!
> >> *c
> >> $!-----------------------------------------!
> >> $! LOGIN FILE FOR USER: EDED
> >> $!-----------------------------------------!
> >> ..
> >> ..
> >> <ctrl-Z>
> >> *quit
> >>
> >> $
> >
> > Did you scroll up and down during your EDT session?
> Just tried with a larger file (than my LOGIN.COM) and jumped
> up and down in it within EDT. I could still scroll back to my
> previous screen content before I entered EDT.
>
> EDT is my prefered editor and I would definitely had seen this
> if it had been a problem. So, no, I have never seen this problem.
> And I have used Reflection, Extra! and Putty over the years.

Thanks! OK, the problem is with Terminal.

Alan

On 9/24/2022 10:18 PM, alanfe...@gmail.com wrote:
> On Saturday, September 24, 2022 at 5:16:33 PM UTC-4, Jan-Erik Söderholm wrote:
>> Den 2022-09-24 kl. 17:26, skrev alanfe...@gmail.com:
>>> On Saturday, September 24, 2022 at 9:03:22 AM UTC-4, Jan-Erik Söderholm wrote:
>>>> Den 2022-09-24 kl. 06:06, skrev alanfe...@gmail.com:
>>>>> On Friday, September 23, 2022 at 11:24:48 PM UTC-4, Robert A. Brooks wrote:
>>>>>> On 9/23/2022 11:13 PM, alanfe...@gmail.com wrote:
>>>>>>
>>> [...]
>>>>>
>>>>> Alan
>>>> Works just fine with EDT and Putty.
>>>>
>>>> Here I did SHO SYS, picked up my LOGIN.COM file in EDT,
>>>> switched to full screen, did quit from EDT and finaly
>>>> just scrolled back my screen session in Putty.
>>>>
>>>> The PACK11_PLC process was the last line from SHO SYS before
>>>> EDT was started. It is still there in the scroll-back buffer
>>>> after exiting EDT.
>>>>
>>>>
>>>> 00009206 PACK_11 LEF 11 2957 0 00:00:00.44 1752 1458
>>>> 00009A07 PACK_11PLC LEF 11 2357 0 00:00:00.40 1946 1648
>>>> $ edit/edt login.com
>>>> 1 $!-----------------------------------------!
>>>> *c
>>>> $!-----------------------------------------!
>>>> $! LOGIN FILE FOR USER: EDED
>>>> $!-----------------------------------------!
>>>> ..
>>>> ..
>>>> <ctrl-Z>
>>>> *quit
>>>>
>>>> $
>>>
>>> Did you scroll up and down during your EDT session?
>> Just tried with a larger file (than my LOGIN.COM) and jumped
>> up and down in it within EDT. I could still scroll back to my
>> previous screen content before I entered EDT.
>>
>> EDT is my prefered editor and I would definitely had seen this
>> if it had been a problem. So, no, I have never seen this problem.
>> And I have used Reflection, Extra! and Putty over the years.
>
> Thanks! OK, the problem is with Terminal.
>
> Alan

It may be EDT doing something goofy that was previously ignored by most
emulators, but Terminal/iTerm2 respond to, and may be responding correctly.

I took (literal) screenshots of what EDT and TPU do on a VT320 in
"Display Control Characters" mode, with a mini editing session. I will
figure out what the various escape sequences are trying to do.

On Sunday, September 25, 2022 at 1:05:22 AM UTC-4, Michael Moroney wrote:
> On 9/24/2022 10:18 PM, alanfe...@gmail.com wrote:
> > On Saturday, September 24, 2022 at 5:16:33 PM UTC-4, Jan-Erik Söderholm wrote:
> >> Den 2022-09-24 kl. 17:26, skrev alanfe...@gmail.com:
> >>> On Saturday, September 24, 2022 at 9:03:22 AM UTC-4, Jan-Erik Söderholm wrote:
> >>>> Den 2022-09-24 kl. 06:06, skrev alanfe...@gmail.com:
> >>>>> On Friday, September 23, 2022 at 11:24:48 PM UTC-4, Robert A. Brooks wrote:
> >>>>>> On 9/23/2022 11:13 PM, alanfe...@gmail.com wrote:
> >>>>>>
> >>> [...]
> >>>>>
> >>>>> Alan
> >>>> Works just fine with EDT and Putty.
> >>>>
> >>>> Here I did SHO SYS, picked up my LOGIN.COM file in EDT,
> >>>> switched to full screen, did quit from EDT and finaly
> >>>> just scrolled back my screen session in Putty.
> >>>>
> >>>> The PACK11_PLC process was the last line from SHO SYS before
> >>>> EDT was started. It is still there in the scroll-back buffer
> >>>> after exiting EDT.
> >>>>
> >>>>
> >>>> 00009206 PACK_11 LEF 11 2957 0 00:00:00.44 1752 1458
> >>>> 00009A07 PACK_11PLC LEF 11 2357 0 00:00:00.40 1946 1648
> >>>> $ edit/edt login.com
> >>>> 1 $!-----------------------------------------!
> >>>> *c
> >>>> $!-----------------------------------------!
> >>>> $! LOGIN FILE FOR USER: EDED
> >>>> $!-----------------------------------------!
> >>>> ..
> >>>> ..
> >>>> <ctrl-Z>
> >>>> *quit
> >>>>
> >>>> $
> >>>
> >>> Did you scroll up and down during your EDT session?
> >> Just tried with a larger file (than my LOGIN.COM) and jumped
> >> up and down in it within EDT. I could still scroll back to my
> >> previous screen content before I entered EDT.
> >>
> >> EDT is my prefered editor and I would definitely had seen this
> >> if it had been a problem. So, no, I have never seen this problem.
> >> And I have used Reflection, Extra! and Putty over the years.
> >
> > Thanks! OK, the problem is with Terminal.
> >
> > Alan
> It may be EDT doing something goofy that was previously ignored by most
> emulators, but Terminal/iTerm2 respond to, and may be responding correctly.
>
> I took (literal) screenshots of what EDT and TPU do on a VT320 in
> "Display Control Characters" mode, with a mini editing session. I will
> figure out what the various escape sequences are trying to do.

Looking forward to it. EDT full screen mode always seemed to reset the screen properly no matter how badly is was screwed up!