Lisp code text formatting broken when SEEing source files in TEdit

[Paolo Amoroso]

Describe the bug
When viewing Interlisp source files with TEDIT-SEE text formatting in the TEdit window is broken. Control characters look like black boxes and code is not styled with the usual attributes such as bold.

To Reproduce
Steps to reproduce the behavior:

1. sign into your Interlisp Online account
2. under Initial Exec, select Interlisp
3. click Run Medley
4. evaluate (TEDIT-SEE 'INIT)

Expected behavior
Lisp code appears formatted as usual such as with function names in bold.

Screenshots
The TEDIT-SEE window:

The full desktop with the TEdit window (to the bottom right of the browser) created by the File Browser command See > Scrollable & Pretty:

Context (please complete the following information):

• OS: chromeOS Stable
• OS Version: 124.0.6367.95
• Host arch: x86_64 (ASUS Chromebox 3)
• Maiko version: N/A
• IL:MAKESYSDATE: 22-Apr-2024 02:03:43

Additional context
Text formatting is similarly broken when viewing files with the File Browser command See > Scrollable & Pretty.

[rmkaplan]

I see the problem online, but not on my mac. On my mac the font changes are properly interpreted. I think the problem is that the variable TEDIT.INPUT.FORMATS is NIL online, instead of what it should be: ((TEDIT.BRAVOFILE? TEDITFROMBRAVO) (LISPSOURCEFILEP TEDITFROMLISPSOURCE)) This is how it determines what to do with non-Tedit files (in particular, Bravo and Lisp source). If LISPSOURCEFILEP is true, it applies TEDITFROMLISPSOURCE, which interprets the font changes. Otherwise, it sees them as ordinary (black-box) characters. So why isn’t that variable set? What about the other platforms?

…

On May 7, 2024, at 12:36 PM, Paolo Amoroso ***@***.***> wrote: Describe the bug When viewing Interlisp source files with TEDIT-SEE text formatting in the TEdit window is broken. Control characters look like black boxes and code is not styled with the usual attributes such as bold. To Reproduce Steps to reproduce the behavior: sign into your Interlisp Online account under Initial Exec, select Interlisp click Run Medley evaluate (TEDIT-SEE 'INIT) Expected behavior Lisp code appears formatted as usual such as with function names in bold. Screenshots The TEDIT-SEE window: tedit-see1.png (view on web) <https://github.com/Interlisp/medley/assets/10342479/b3d0b149-58b3-4de5-a6ab-3ab992598d3e> The full desktop with the TEdit window (to the bottom right of the browser) created by the File Browser command See > Scrollable & Pretty: tedit-see2.png (view on web) <https://github.com/Interlisp/medley/assets/10342479/71a75e69-828f-4ffa-b903-3ed600ab2c49> Context (please complete the following information): OS: chromeOS Stable OS Version: 124.0.6367.95 Host arch: x86_64 (ASUS Chromebox 3) Maiko version: N/A IL:MAKESYSDATE: 22-Apr-2024 02:03:43 Additional context Text formatting is similarly broken when viewing files with the File Browser command See > Scrollable & Pretty. — Reply to this email directly, view it on GitHub <#1700>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJPRU2PAISB3L6QPI3DZBEUNFAVCNFSM6AAAAABHLTXIZKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4DIMBYGU2TKMQ>. You are receiving this because you are subscribed to this thread.

[Nick Briggs]

Odd. If you reload TEDIT-FILE.LCOM it will reset TEDIT.INPUT.FORMATS.

[rmkaplan]

The value is correct in the release full sysout even without my INIT (on my mac).

…

On May 7, 2024, at 2:30 PM, Nick Briggs ***@***.***> wrote: Odd. If you reload TEDIT-FILE.LCOM it will reset TEDIT.INPUT.FORMATS. — Reply to this email directly, view it on GitHub <#1700 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJKSESQZHTW76IHPBODZBFBYRAVCNFSM6AAAAABHLTXIZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJZGM2DGMJUGQ>. You are receiving this because you commented.

[Paolo Amoroso]

I confirm TEDIT.INPUT.FORMATS is NIL online. But setting TEDIT.INPUT.FORMATS to ((TEDIT.BRAVOFILE? TEDITFROMBRAVO) (LISPSOURCEFILEP TEDITFROMLISPSOURCE)) or loading TEDIT-FILE.LCOM restores formatting only in part:

[Nick Briggs]

The black-boxes in the DEFINE-FILE-INFO are not totally unexpected - they're the package delimiter in the INTERLISP file readtable which I think is 0x1E, the ASCII RS (record separator) character - so there really is no meaningful printable form.

[Paolo Amoroso]

I copied the same INIT file to my local Linux, which runs an old Medley build, and it looks like this with no black boxes: