Many medley source files are difficult to read using inconsistent styles

[masinter]

Lisp can print out source code with lots of options with respect to case, package, encoding, readable, in ways that don't affect what will be read. Over the years after common lisp and "living inside" the Lisp world, the idea of a "listing" being something that you cared about got left behind.

This might be OK if you are working in Medley, but it isn't so good for newcomers just trying to get a sense of what is what, or someone wanting to take SEdit and port it to another Common Lisp.

I think the solution is going to involve redoing MAKEFILE NEW on sources after we've fixed some of the problems with current listings. |changes| |to:|

[Anzus]

There’s a LispUsers package called Migration that does a lot of this. I don’t see it on Github, so I’ll add to the repo. Here’s what the description documentation says: "Contains a tool for translating File Manger format Interlisp source files from Medley into Common Lisp text files. The software runs in the Medley system.” Unfortunately that’s the only documentation for it.

…

On Nov 28, 2021, at 5:11 PM, Larry Masinter ***@***.***> wrote: Lisp can print out source code with lots of options with respect to case, package, encoding, readable, in ways that don't affect what will be read. Over the years after common lisp and "living inside" the Lisp world, the idea of a "listing" being something that you cared about got left behind. This might be OK if you are working in Medley, but it isn't so good for newcomers just trying to get a sense of what is what, or someone wanting to take SEdit and port it to another Common Lisp. I think the solution is going to involve redoing MAKEFILE NEW on sources after we've fixed some of the problems with current listings. |changes| |to:| — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#590>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACBP2DH7YXZVETZDOPB4KR3UOLAMNANCNFSM5I54GFXQ>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[masinter]

There's a thing in XCL:PROFILE defined in the file PROFILE which combines all of the various Common Lisp control variables like PRINT-CASE etc. And a definer GETDEF("INTERLISP" PROFILE) SHOWDEF("LISP" PROFILE).
PROFILE.TXT
still looking for documentation grep -ri with-profile . gives some clues.

we need to remake source files with a consistent profile-per-file.

[masinter]

assigned to "outreach" because it would be better for newcomers if the "source" files were legible.
assigned to "Common Lisp" because the problem is incomplete integration with Common Lisp