[Info-vax] Intel proposal to simplify x86-64

[Johnny Billquist]

On 2023-06-10 15:44, Scott Dorsey wrote:
> gah4  <gah4 at u.washington.edu> wrote:
>> On Wednesday, June 7, 2023 at 5:06:09=E2=80=AFAM UTC-7, Simon Clubley wrote=
>> (snip)
>>
>>> The last time I really used it was decades ago, back when I started in=20
>>> the DEC world on RSTS/E at the very start of my career. When I moved to=
>> =20
>>> VMS and saw TPU, that's when I stopped using TECO.
>>
>> I am surprised that there isn't a port to C for Unix and Windows.
>>
>> Then that one could be ported to VMS.
> 
> There is.  The problem, though, with porting Unix and Windows editors to
> VMS, and this goes both for TECO and vi, is that in the Unix and Windows
> world all files are stream files and you wind up with editors that can
> only operate on stream files.  Or even worse (as was the case of a vim
> port I used), will convert other files into stream_lf files without warning.

I guess this is the moment in time to mention that teco always view any 
file as a stream of bytes, always. When it's written back to disk, it 
might do that in whatever format, but while it's in memory, it's a 
stream of bytes with both CR and LF in there.

teco is *not* a line editor.

   Johnny