Re: Hex File Snooper

[Thomas Passin]

 It was remarkable how much faster a 2 MHz Z80 was than an early PC with 
the 8088 at nearly 5 MHz.  I was able to make a direct comparison because I 
had a FORTH program I used all the time on a 64k Z80 machine.  When I got a 
PC I was able to find a 8088 FORTH system.  FORTH was written with a small 
core of assembler and then all the other FORTH instructions were written 
using that fast core.  So FORTH for the two machines was as nearly 
comparable as you were going to get.

The PC version running our FORTH code on a 8088 machine was wretchedly slow 
compared to the Z80 version.  The PC version only caught up when the AT 
came out with an 8MHz processor.

On Thursday, June 13, 2024 at 5:08:29 PM UTC-4 jkn wrote:

> I never used TECO on a PDP (PDP/11 in my case), but I did use PMATE 
> ('Michael Aaronson's Text Editor, IIRC) on an early S-100 Z80 computer, and 
> that was heavily 'inspired' by TECO, I believe. working with the 'command 
> syntax' was great fun, as was customising the editor to work with your 
> graphics card driver.
>
>
> On Thursday, June 13, 2024 at 8:45:01 PM UTC+1 tbp1...@gmail.com wrote:
>
>> After reading the link, I see I never got near anything like TECO.
>>
>> On Thursday, June 13, 2024 at 3:17:49 PM UTC-4 David Szent-Györgyi wrote:
>>
>>> TECO for the PDP/8 was available under OS/8. The Wikipedia article on 
>>> TECO  is a nice 
>>> summary. There you can find links to Web pages on TECO, including one by 
>>> the originatoer of TECO and the GitHub repository for TECOC, a 
>>> reimplementation in C for Windows, macOS, and LInux. 
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/c1549548-50f2-4a4f-b9c2-b02fe37c7979n%40googlegroups.com.

Re: Hex File Snooper

[David Szent-Györgyi]

TECO for the PDP/8 was available under OS/8. The Wikipedia article on TECO 
 is a nice summary. There 
you can find links to Web pages on TECO, including one by the originatoer 
of TECO and the GitHub repository for TECOC, a reimplementation in C for 
Windows, macOS, and LInux. 

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/8b7fbdde-6e13-4f65-8de9-cded0a576a44n%40googlegroups.com.

Re: Hex File Snooper

[jkn]

I never used TECO on a PDP (PDP/11 in my case), but I did use PMATE 
('Michael Aaronson's Text Editor, IIRC) on an early S-100 Z80 computer, and 
that was heavily 'inspired' by TECO, I believe. working with the 'command 
syntax' was great fun, as was customising the editor to work with your 
graphics card driver.


On Thursday, June 13, 2024 at 8:45:01 PM UTC+1 tbp1...@gmail.com wrote:

> After reading the link, I see I never got near anything like TECO.
>
> On Thursday, June 13, 2024 at 3:17:49 PM UTC-4 David Szent-Györgyi wrote:
>
>> TECO for the PDP/8 was available under OS/8. The Wikipedia article on 
>> TECO  is a nice 
>> summary. There you can find links to Web pages on TECO, including one by 
>> the originatoer of TECO and the GitHub repository for TECOC, a 
>> reimplementation in C for Windows, macOS, and LInux. 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/f157a178-7e72-4840-ac0f-691b3546d4a5n%40googlegroups.com.

Re: Script To Swap Log Frame Between Secondary And Primary Splitter

[Edward K. Ream]

On Wed, Jun 12, 2024 at 12:21 PM Thomas Passin  wrote:

> When Leo comes to life, the Log frame normally shares the panel that has
> the tree.  I often like to have the Log frame next to the body editor
> instead.  This lets me see more of the tree at once and also gives the Log
> panel more vertical height.  This is often important for me.


Thanks, Thomas. Scripts like this were a motivation for Leo 6.8.0. And such
scripts were why I was willing to have 6.8.0 be a breaking change from
Leo's previous codebase.

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS3yqV2hH6dBZ9h4aS-D7Pnnof_ySF4iZBMZNs_cxeyKkg%40mail.gmail.com.

Re: Hex File Snooper

[Thomas Passin]

After reading the link, I see I never got near anything like TECO.

On Thursday, June 13, 2024 at 3:17:49 PM UTC-4 David Szent-Györgyi wrote:

> TECO for the PDP/8 was available under OS/8. The Wikipedia article on TECO 
>  is a nice summary. 
> There you can find links to Web pages on TECO, including one by the 
> originatoer of TECO and the GitHub repository for TECOC, a reimplementation 
> in C for Windows, macOS, and LInux. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/419ec002-2de9-498d-b172-05617d8071c9n%40googlegroups.com.

Re: Hex File Snooper

[Thomas Passin]

I was using a PDP8/i back around 1973.  I don't remember TECO.  Maybe it 
came in with the /e?  Or maybe it's just the passage of time ...

On Thursday, June 13, 2024 at 9:57:45 AM UTC-4 David Szent-Györgyi wrote:

> The TECO text editor was designed to edit files that were too large to fit 
> in memory. I used TECO on a PDP8/e minicomputer; the 8/e used 12-bit words; 
> memory was addressed in 128-word pages and 4096-word fields. 
>
> The original implementation of Emacs was a set of "editor macros" written 
> in TECO. Maybe this means that the old joke that every program accrues 
> features to become more like Emacs has it wrong; every program grows to 
> become more like TECO. *grin*
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/e2a5876e-fcbc-4cc1-9d3a-2e8467fb7f8fn%40googlegroups.com.

Re: Hex File Snooper

[David Szent-Györgyi]

The TECO text editor was designed to edit files that were too large to fit 
in memory. I used TECO on a PDP8/e minicomputer; the 8/e used 12-bit words; 
memory was addressed in 128-word pages and 4096-word fields. 

The original implementation of Emacs was a set of "editor macros" written 
in TECO. Maybe this means that the old joke that every program accrues 
features to become more like Emacs has it wrong; every program grows to 
become more like TECO. *grin*

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/3e6211f8-b0ee-4539-af3f-a5f5ea3e0c1bn%40googlegroups.com.

Re: Hex File Snooper

[jkn]

I hadn't heard of ArchWSL before, thanks for that. I run Kubuntu rather 
than Arch Linux, but I like the latter's documentation a lot.

J^n


On Tuesday, June 11, 2024 at 8:25:02 PM UTC+1 gates...@gmail.com wrote:

> As with all things, YMMV.  But I run a Windows 10 installation, with 
> ArchWSL as my WSL distro.  It's on WSL2 (as opposed to WSL1, which did 
> things differently).  WSL2 effectively runs the Linux kernel as a program, 
> which other linux programs can use to get their system calls answered, so 
> it's fairly lightweight in that aspect.
>
> On my system, the memory impact is minimal (maybe 10-100MB when idle). 
> Disk space is going to be entirely up to what you install inside your 
> distro -- on my box it's hovering at around 50GB, but that's after using 
> this same installation for many years, installing packages, etc.  The 
> default install depending on distro could be 10GB or so.
>
> Once in a WSL shell, your Windows drives and files are available in 
> /mnt/.  For example, /mnt/c is my C: drive.  It's really slick 
> how well they pulled it off.
>
> Jake
>
> On Tue, Jun 11, 2024 at 1:58 PM Thomas Passin  wrote:
>
>>
>> On Tuesday, June 11, 2024 at 12:35:26 PM UTC-4 gates...@gmail.com wrote:
>>
>> On Windows, I use my Linux tools :)
>>
>> WSL is fantastic for this — ‘xxd’ works just as well in a WSL shell as it 
>> does on my Arch laptop.
>>
>>
>> I haven't tried WSL yet.  Does it take up a lot of memory or disk space? 
>> I'm not a Linux whiz, and I usually spin up a Linux VM when I need to try 
>> something.
>>
>> -- 
>>
> You received this message because you are subscribed to the Google Groups 
>> "leo-editor" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to leo-editor+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/leo-editor/2b9962d0-fb02-4a30-9f94-f9e40589e7c1n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/0bf6c28a-6975-4a15-b315-3e7528455bcfn%40googlegroups.com.