DFV gets FNS and/or FUNCTIONS, depending on what definitions exist (#2530)

If both exist, it brings up 2 Sedit windows.

The relative version numbers are currently mapped to Medley absolute
version numbers. It would be nice to extend VERSIONDEFS with a function
(say GEDV) that maps the relative version numbers into the definitions
on git-file versions, by looking at the history. So (GEDV 'FOO 'RECORD
-3) would find the file for FOO's record declaration from WHEREIS, and
get the definition from the version 3 commits back. But GITFNS doesn't
currently have a primitive for fetching and interpreting history.

.github/ISSUE_TEMPLATE/primer.yml

@@ -0,0 +1,68 @@
+name: Report an issue with the "Medley Interlisp for the Newcomer" primer
+description: Use this template to report issues or make suggestions.
+title: "[Primer] <short title here>"
+labels: 
+  - primer
+  - documentation
+body:
+  - type: dropdown
+    id: problemType
+    attributes:
+      label: "What type of issue are you reporting?"
+      options:
+        - Suggested improvement
+        - Incorrect explanation / code sample
+        - Confusing explanation
+        - Outdated information
+        - Broken link
+        - Typo / Grammar
+    validations:
+      required: true
+  - type: dropdown
+    id: location
+    attributes:
+      label: "Section of the primer where the issue occurs"
+      options:
+        - Introduction
+        - Medley online and Medley Local
+        - Understanding and Navigating the Interface
+        - Understanding Lisp Syntax
+        - Atoms, Functions and Lists
+        - Variable Bindings and Scope
+        - Iterators and Conditionals
+        - The File Browser
+        - Debugging
+        - Editing functions with SEdit
+        - Build Your First Interactive Program
+        - Saving Your Work
+        - TEdit, The WYSIWYG Editor
+        - Drawing and Displaystreams
+        - Making a Graph with Grapher
+        - Additional Resources
+        - General Feedback (not specific to a section)
+    validations:
+      required: true
+  - type: textarea
+    id: issueLocationDetails
+    attributes:
+      label: "Please provide more details about the location of the issue"
+      description: "For example, the specific page title, section heading, or url."
+    validations:
+      required: false
+  - type: textarea
+    id: issueDescription
+    attributes:
+      label: "Description of the issue"
+      description: "Please provide a detailed description of the issue you encountered."
+    validations:
+      required: true
+  - type: textarea
+    id: suggestedFix
+    attributes:
+      label: "Suggested fix or improvement"
+      description: "If you have a suggestion for how to fix or improve the issue, please provide it here."
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: "## Thank you for helping us improve the **Medley Interlisp for the Newcomer** primer!"

.github/ISSUE_TEMPLATE/what_people_are_saying.yml

@@ -1,6 +1,6 @@
-name: "New entry for **What People Are Saying**"
-description: "Suggest a new entry for the **What People are Saying** page"
-title: "What People are Saying suggestion"
+name: New "What People Are Saying" entry
+description: 'Suggest a new entry for the "What People Are Saying" page'
+title: "What People Are Saying suggestion"
 body:
   - type: dropdown
     id: contentType
@@ -24,7 +24,7 @@ body:
     id: additionalInformation
     attributes:
       label:  Additional information
-      description: "Use this space to supply any addiitonal information on the suggested item."
+      description: "Use this space to supply any additional information on the suggested item."
     validations:
       required: false
   - type: markdown

.gitignore

@@ -31,6 +31,9 @@ loadups/whereis.hash
 loadups/apps.sysout
 loadups/fuller.database
 loadups/build/
+loadups/tagged
+loadups/gitinfo
+
 
 # manual cross-reference files
 

CONTRIBUTING.md

@@ -3,7 +3,7 @@
 First, we want to thank you for helping reach the goal of restoring Medley Interlisp
 to the point where it is as useful today as it was 30 years ago.
 
-This guide is meant to help you make useful contributions, whether to the [Maiko](https://github.com/Interlisp/maiko) C-based virtual machine implementation, the [Medley](https://github.com/Interlisp/medley) Lisp code (in Interlisp and Common Lisp), or [documentation](https://github.com/Interlisp/medley/wiki). There are a number of [GitHub](https://github.com/Interlisp/medley/discussions/categories/github-use) problems that could use some attention.
+This guide is meant to help you make useful contributions, whether to the [Maiko](https://github.com/Interlisp/maiko) C-based virtual machine implementation, the [Medley](https://github.com/Interlisp/medley) Lisp code (in Interlisp and Common Lisp), or [documentation](https://interlisp.org/software/using-medley). There are a number of [GitHub](https://github.com/Interlisp/medley/discussions/categories/github-use) problems that could use some attention.
 
 ## Working with Maiko
 
@@ -17,6 +17,8 @@ The current arrangement of files and extentions is awkward for working on the im
 * The most useful contributions are reproducible errors -- things that don't work as documented.
 * Second most useful are reports of unexpected behavior -- things that aren't documented but behave unexpectedly.
 
+To report these errors and behaviors [open an issue](https://github.com/Interlisp/medley/issues).
+
 ## Reporting a bug or feature request
 * Ensure the bug was not already reported by searching on GitHub under [Issues](https://github.com/Interlisp/medley/issues) or [Discussions](https://github.com/Interlisp/medley/discussions). Note that all issues and Discussions are found in the Medley repository, using labels to distinguish. Discussions are for questions or topics where there is some disagreement or uncertainty about the "right" direction.
 * If you're unable to find a discussion or open issue addressing the problem, open a new one. Be sure to include a title 
@@ -24,7 +26,7 @@ and clear description, as much relevant information as possible. Use the issue t
 
 ## Did you write a patch that fixes a bug?  
 * Some bug fixes and "improvements" have unintended consequences, well beyond what you might expect for well-written modern code. We don't have testing new builds automated or integrated. Be sure you've tested your patch.
-* Open a new [GitHub pull request](https://github.com/Interlisp/maiko/pulls) with the patch.
+* Open a new GitHub pull request with the patch.
 * Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
 * Keep Pull Requests small and easily reviewable.  https://www.thedroidsonroids.com/blog/splitting-pull-request for
 a writeup of good practices.

README.md

@@ -1,12 +1,14 @@
 # Medley 
 
-This repository is for the Lisp environment of [Medley](https://interlisp.org).
+The [Medley Interlisp Project](https://interlisp.org) aims to preserve, revive, and modernize the [Interlisp](https://interlisp.org) software development environment for rapid prototyping, research and Artificial Intelligence created at Xerox PARC since the 1970s.
 
-[Install and Run](https://interlisp.org/software/install-and-run) covers ways to install and start up Medley on Linux systems, MacOS, and Windows (with or without WSL).
+This repository is for the Lisp environment of the [Medley](https://interlisp.org) release of Interlisp. Other repositories hold additional subsystems and applications such as [Maiko](https://github.com/Interlisp/maiko), the implementation (in C) of the Medley virtual machine, the [LOOPS](https://github.com/Interlisp/loops) object-oriented extension of Interlisp, and the [NoteCards](https://github.com/Interlisp/notecards) hypermedia system.
+
+[Install and Run](https://interlisp.org/software/install-and-run) covers ways to install and start up Medley on Linux systems, MacOS, Windows (with or without WSL), and in a web browser.
 
 [Using Medley](https://interlisp.org/software/using-medley/) has an overview and pointers to documentation.
 
-[Interlisp/maiko](https://github.com/Interlisp/maiko), is the repo for the implementation (in C) of the Medley virtual machine. 
+The [Glossary](https://interlisp.org/history/glossary) defines system-specific terms such as "loadup" and "sysout".
 
 ## Releases
 
@@ -67,25 +69,9 @@ If you have a high-resolution display, note that much of the graphics was design
 
 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)
+### Running Medley Interlisp
 
-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.
+The primer [Medley Interlisp for the Newcomer](https://primer.interlisp.org) eases new users into the Interlisp environment. It assumes no prior knowledge of Lisp and covers the user interface, programming and debugging, windows and graphics, and more. We recommend consulting this document to learn how to run and use the system.
 
 ### Exiting The System
 
@@ -123,7 +109,7 @@ 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](https://github.com/Interlisp/medley/Documentation))
+* docs -- Documentation files (in TEdit format, PDFs, or online help
 * 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

docs/html-primer/Medley-Primer-OnePage.html

@@ -1,2 +0,0 @@
-<!DOCTYPE  html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/><title>Medley-Primer-OnePage</title></head><frameset cols="310pt,*" rows="94%"><frame src="Medley-Primer-OnePage_files/headings.htm" name="headings"/><frame src="Medley-Primer-OnePage_files/content.htm" name="content"/></frameset></html>