@zyd @falken @oantolin @jesus

> We're hardly ever typing function definitions into it so I rather think of it as your workbench.

This is because Common #Lisp is designed around text editing files in file store rather than structure editing actual Lisp structures in memory -- to the extent that it's pretty hard to retrofit a structure editor into Common Lisp.

I feel, having grown up in the days of structure editors, that this is an enormous own goal.

@simon_brooke @zyd @falken @jesus I think I missed that era of structure editors! All the editors I know use text and all of the attempts at structure editors I've read about seem to have failed to gain any traction. Which structure editors did you use?

@oantolin You can still try the structure editor of the Medley Interlisp environment, SEdit. It eventually replaced DEdit and supports Interlisp and Common Lisp.

https://interlisp.org

@simon_brooke @zyd @falken @jesus

Medley Interlisp Project

The Medley Interlisp Project a retrofuturistic software system What did we leave behind on the path to developing today's computer systems? Could there be lessons for the future of computing hidden in the past? Enter the Medley software environment to explore these questions.

The Medley Interlisp Project

@amoroso It's not a structure editor, it's a text editor, surely?

I mean, it's getting on for forty years since I used it, but I thought it was a huge step backwards.

@simon_brooke Although it works differently internally, to the user it appears as SEdit manipulates structures. Which is most of the experience modern developers aren't familiar with.
@amoroso I must clearly try it again. I remember disliking it extremely!
Medley Interlisp structure editing: first impressions

Although I used several Lisp systems over a couple of decades, I never tried structure editing. The chance finally came when I encounter...

Paolo Amoroso's Journal