Want Lisp git/Github client

[masinter]

I think our problems with Git and GitHub are mainly terrible UI.

I'd like a git implementation that integrates with the file package, masterscope, loadups, etc.

This isn't unusual. There are lots of "git desktop" packages. Let's make one that works for us.

[orcmid]

I suppose there is the matter of on-boarding new developers or people who toy with forks/clones, and any friction related to unfamiliar tooling,

On my PC I get good git integration not only with the GitHub desktop client but with Git4Windows and Tortoise Git (for all the nice tagging of files in the File Explorer as well as actions in the context menu).

I suspect you are looking for even higher level things and automation around them. Of course wanting a kind of Interlisp-centered tool regime is up to you and the itches you are scratching. Maybe it resonates with what you are after as well. Just curious here.

[masinter]

one of the reasons why Interlisp is interesting is that it embodies a different style of software development. As with Smalltalk, but also different, is that there's not only a REPL Read-Eval-Print-Loop but you're editing in the live environment.
Users don't edit the text of their programs ("A program is not its listing") and the structure with definers. The Lisp system (fiflepkg, masterscope etc) are aware of files and dates and versions.

We don't want to lose that. Versioning systems without 'git' model worked. Git-based development don't.
The problems aren't unworkable -- raw 'git' has useful properties -- but the Git desktop clients think they own the file system inside the repo and make changes that are mysterious and unhelpful.

For a small example, files have "filemaps" that allow you to use LOADFNS and GETDEF and COMPAREDEFS between different versions, so I can ask

COMPAREDEFS(FOO FNS (NIL FILE))

or

COMPAREDEFS(FOO FNS (FILE;3 FILE;4)

I did write a shall-based medley/scripts/restore-versions.sh which turns git history (git log) into version numbers.
But this doesn't deal with branching or comparing across named branches which aren't in the history.

[orcmid]

@masinter

one of the reasons why Interlisp is interesting is that it embodies a different style of software development. As with Smalltalk, but also different, is that there's not only a REPL Read-Eval-Print-Loop but you're editing in the live environment. Users don't edit the text of their programs ("A program is not its listing") and the structure with definers.

I recall Smalltalkers raving about this sort of thing. I lean more to the Literate Programming school, although in spirit, not literal form.

I'm uncertain how software-engineering practices and open-source collaboration projects work in the Interlisp case, where (Inter/C)Lisp are the currency of expression. Are Docker images seen as the interchange medium? Can one not export a (pretty-printed) expression of definitions and is there no coupling with some form of narrative about what it is for as opposed to what it is?

[masinter]

The discussion in #533 is the reason I made this a separate issue.

[masinter]

The Lispusers "package" GITFNS has the start. Closing this issue; if medley/lispusers/GITFNS has problems, raise separate issues.