415a698df5
* Make medley.sh and its associated scripts POSIX compliant - i.e., debashify them * Added config file for medley script, medley now reads from config file and prepends arguemnts from file to the copmmand line arguments * WIP. Updates to medley.sh scripts. * WIP. More on medley.sh and friends update. * WIP. Medley redo * WIP. Debugging new medley scripts * Renamed medley.sh/medley.command to be medley_main.sh. Added code to compile single medley.sh/medley.command script by inlining all of the source'd medley_*.sh files. * Add temp fix for cygwin Issue #1685 * Minor fixup to medley_utils.sh; take debug code out out of run_medley * Add README to medley directory to explain how to compile medley.sh (medley.command). * Ooops. This time really adding the README file to the medley directory explaining how to compile medley.sh (medley.command) * Update loadup- scripts to use updated medley scripts rather than run-medley * Fix default setting of $config_file in medley_configfile.sh * Redo medley compile to pick up last commikt * Fixing how maiko exe is found and sysout argument error processing - both issues discovered testing on MAcOS * In medley_configfile, replace echo with printf %s because echo - does not work in zsh * Supress config file on loadups calls to Medley * Add oldschool support (use original run-medley) to loadup scripts; improve FAILURE detection so loadup-all won't proceed once one of the components fails * Add in medley_args.sh add -prog as synonym to --maikoprog to aid in loadup scripts; in medley_run.sh script try to get a good exit code for call to maiko, especially useful for loadup scripts * Run loadup scripts thru shellcheck and update as necessary to make Posix compliant * Get rid of -nt comparisons in loadup-setup.sh because they are not posix-complaint. They were not really needed anyway. * Removing (for now) use of lde exit codes to decide FAILURE case in loadup-setup.sh since exit codes from lde apperar to be inverted on MacOS. * Update medley man page. Add - functionality to more args is medley_args.sh * Compile medley.sh with changes from last commit * Ooops. Left medley_args.sh changes out of last commit. Rectifying here. * Added support for LDEKEYBOARDTYPE to medley_run to match run-medley * Add to medley.sh: auto numbered id's and titles with id's inserted * Cleanup some shellcheck issues in medley_main.sh * fix maiko args -nh-xxx. were -nethub-xxxx. In medley_run.sh * Overhaul handling of pass-on args to manage the quoting issues prevelant in the previous implementation * Cleanup minor shellcheck issues in medley_*.sh scripts * Add underscore as character allowed in ids - makes things clearer when id used with + * Add a self-numbering id to medley calls in loadup scripts * Put workaround in medley_run.sh for Issue #1702 - issues with sysout arg processing in Maiko * Oops. messed up LDESRCSYSOUT in last commit. should be LDESOURCESYSOUT * compile medley.sh
Medley
This repository is for the Lisp environment of Medley.
Install and Run covers ways to install and start up Medley on Linux systems, MacOS, and Windows (with or without WSL).
Using Medley has an overview and pointers to documentation.
Interlisp/maiko, is the repo for the implementation (in C) of the Medley virtual machine.
Releases
While there are installers for popular platforms, this section may be useful in some circumstances.
Getting releases
Get the Maiko release here. You'll need the .tgz file corresponding to your operating system and processor. For Windows with WSL or Intel Linux, use linux.x86_64; for Macs use darwin.x86_64 for Intel and darwin.aarch64 for Mac silicon. Windows without WSL uses cygwin instead.
Or, build your own maiko (the binaries lde, ldex OR ldesdl, and ldeinit).
You can also build for other architectures
The medley release image and sources come in two parts, found here
- The "loadups" (download
medley-YYMMDD-XXXXX-loadups.tgz) - The "runtime" (download
medley-YYMMDD-XXXXX-runtime.tgz)
where YYMMDD is the date and XXXXX is the GitHub commit ID.
The "runtime" isn't needed if you've cloned the (medley) repo--you have all the files. The "runtime" has extra fonts, unicode tables, and source code that aren't part of the loadups but may be called on.
Unpacking releases
From a shell/terminal window:
- Choose a directory parent where you want to install medley and maiko.
- Unpack the medley loadups file
cdparenttar xvzf medley-YYMMDD-XXXXX-loadups.tgz
- Unpack the medley runtime OR clone the Medley repo (the "medley runtime" is just a subset of the whole repo)
-
tar xvzf medley-YYMMDD-runtime.tgzOR
git clone https://github.com/Interlisp/medley
-
Unpack the maiko file for your operating system and CPU type, e.g.,
tar xvzf maiko-210823.linux.x86_64.tgz -
This should leave you with two directories,
medleyandmaiko.
Setting up X
In many configurations, Medley uses an X-Server to manage its display. Most Linux desktops have one. Windows 11 with WSL includes an X-Server. For Windows 10 with WSL2, there are a number of open-source X servers; for example vcxsrv.
Mac users should get XQuartz from XQuartz.org.
Medley manages the display entirely, doesn't use X fonts and manages it's own window system.
If you have a high-resolution display, note that much of the graphics was designed for a low-resolution display, so an X-server that does "pixel doubling" is best. (E.g., Raspberry Pi does pixel doubling on 4K displays.)
Medley presumes you have a 3-button mouse; the scroll-wheel on some mice acts as one, with some difficulty. Go into XQuartz Preferences/Input and check "Emulate three button mouse" option.
Running Medley Interlisp (obsolete)
The run-medley script in this repo sets up some convenient defaults. Running Medley can be done by typing:
$ cd medley
$ ./run-medley
Or, if you wish to start Medley up with a different SYSOUT:
$ cd medley
$ ./run-medley <SYSOUT-file-name>
The first time the system is run it loads the system image that comes
with the system. When you exit the system (or "do a SaveVM" menu
option) the state of your machine is saved in a file named
~/lisp.virtualmem. Subsequent system startups load the
~/lisp.virtualmem image by default.
Exiting The System
The system may be exited from the Interlisp prompt by typing:
(LOGOUT)
Or from the Common Lisp prompt with:
(IL:LOGOUT)
When you log out of the system, Medley automatically creates a binary
dump of your system located in your home directory named
lisp.virtualmem. The next time you run the system, if you don't
specify a specific image to run, Medley restores that image so that
you can continue right where you left off.
Naming conventions and directory structure
File Names and Extensions: Most Interlisp source file names are UPPERCASE and Interlisp didn't use file extensions for its source files. A .TEDIT or .TXT file is probably documentation for the package of the same name, at least in the library and lispusers directories.
The current repo has both Lisp sources and compiled .LCOM and .DFASL files.
Each directory should have a README.md, but briefly
- BUILDING.md -- instructions on how to make your own loadups
- clos -- early implementation of Common Lisp Object System
- CLTL2 -- files submitted to bring Medley up to the conformance to "Common Lisp, the Language" 2nd edition. Not enough to conform to the ANSI standard lisp.
- docs -- Documentation files (in TEdit format, PDFs, or online help; look here)
- fonts -- raster fonts (or font widths) in various resolutions for display, postscript, interpress, press formats
- greetfiles -- various configuration setups
- internal -- These were internal to Venue
- library -- packages that were supported (30 years ago)
- lispusers -- User contributed packages that were only half supported (ditto)
- loadups -- has sysouts and other builds plus a few remnants
- obsolete -- files we should remove from the repo
- rooms -- implementation of ROOMS window/desktop manager
- run-medley -- script to enhance the options of running medley
- scripts -- some scripts for fixing up things, building and running medley
- sources -- sources for Interlisp and Common Lisp implementations
- unicode -- data files for support of XCCS to and from Unicode mappings