Codeberg and Interlisp sources

[Paolo Amoroso]

The Codeberg Git hosting platform, which is based on the Forgejo code forge, has a major limitation that makes it unusable for Interlisp projects: it doesn't detect Interlisp sources as text and treats them as binary files, allowing only to download but not display them. So I submitted a Forgejo feature request for supporting Interlisp sources.

However, adding such a feature may pose a classification problem as there's apparently no efficient way to classify Interlisp source code as text without increasing false positives. A viable workaround would be to detect a mandatory preamble in the first few bytes of a file that identifies it as an Interlisp source. Can it be assumed that all managed Interlisp files start with (DEFINE-FILE-INFO...?

--

Paolo Amoroso | Blog | Mastodon

[Nick Briggs]

There's no requirement that they start exactly (DEFINE-FILE-INFO -- there could be spaces before that, though it's unlikely.  The real problem is the .LCOM (compiled files) *also* start with (DEFINE-FILE-INFO.  The .DFASL files do NOT start with (DEFINE-FILE-INFO.  You'd want to exclude .LCOM and .DFASL files before applying a (DEFINE-FILE-INFO test.

A more useful solution would be for the system to let you assert that a particular file is a source file when you check it in.  The user *knows* what a new file is, it's helpful if the system can guess, but it shouldn't be required -- that's just bad tool design.

-- Nick

--
You received this message because you are subscribed to the Google Groups "Medley Interlisp core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lispcore+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/lispcore/CAGi1hzvFHSAcbMhZ4sDNXWbWe_L51PKGsiv9Uv_6YxTrTdpRCg%40mail.gmail.com.

[Paolo Amoroso]

The Forgejo developers are working to add support for detecting Interlisp sources.

[Larry Masinter]

Another approach is to fix the Interlisp "file package" to support a file extension (.interlisp, .medley, .ilisp, ...) as a "modernization" to fit in with other current systems.   To make this work requires a few tweaks but nothing drastic (IMHO).

I'll make an issue if there isn't already one.

https://LarryMasinter.net  https://interlisp.org

--

You received this message because you are subscribed to the Google Groups "Medley Interlisp core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lispcore+u...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/lispcore/115075a9-2649-4037-9356-add9d29ede10n%40googlegroups.com.