Dynamic Lisp Listener in Symbolics Genera

Evidence and rights boundary

The implementation and extracted Help files below came from licensed Open Genera media and remain untracked. This page publishes only artifact identities, small interface names, behavioral facts, and original analysis.

Installed Document Examiner records cp1, cp1a, cp2, and cp3 were used to cross-check intended Command Processor operation:

No decoded proprietary prose is tracked or reproduced here.

The public manuals are labeled Genera 8, while the local world identifies as 8.5. Manual statements are treated as product documentation and are cross-checked against the local 8.5 source or the running world before being stated as exact behavior.

Three cooperating layers

The visible facility is easiest to understand as three cooperating systems.

The internal Listener mixin combines process behavior with the standard-value environment and defaults to SI:LISP-TOP-LEVEL1. A public Listener mixin adds an interactor and selection through Select L; the Dynamic Windows combination supplies the pane and presentation framework seen in the running system. The initial Listener is created during warm start, while additional Lisp windows can be created as separate processes from the System Menu.

At the top level, the command loop directs standard input, standard output, error output, query I/O, and debug I/O through the Listener's terminal stream. The trace output stream is deliberately not rebound in this setup. This matters when interpreting output that does not appear where ordinary evaluation results do.

The read-evaluate-print cycle

The Listener reads one object or command, evaluates it, collects all returned values, updates history variables, and prints each returned value on a fresh line. An error offers a top-level restart rather than requiring the process to be discarded.

The standard-value environment maintains these Lisp histories:

There is an important timing detail that a static list of variable names does not show. While a new form is being evaluated, - already denotes that new form, but // still contains the previous evaluation's multiple-value list. Only after the new evaluation returns can the loop replace //. The runtime probe below visibly confirmed that ordering.

The loop dynamically binds its history variables only when an enclosing command loop has not already established them. Nested loops can therefore share an existing history environment, while independent Listener streams normally retain independent histories.

Command Processor modes and dispatch

The running Listener used Command Preferred mode and displayed Command: as its prompt. The implementation supports four input-preference modes:

In Command Preferred mode, alphabetic input first attempts command recognition. If it does not name a command but does name a bound symbol, its Lisp value can be used. A leading comma explicitly forces Lisp input; a leading colon explicitly forces a command. Thus the comma in ,(values 17 23) is dispatch syntax, not part of the Lisp form.

Blank input has a separately configured policy. The source supports reprompting, beeping, ignoring the input, returning NIL, and ending with NIL; this policy is orthogonal to the four command/form modes. Set Command Processor changes the configuration, Show Command Processor Status reports it, and the Command Processor can be turned on or off.

Presentations and mouse-oriented interaction

Command Processor output can retain a semantic link between a printed region and the object it represents. Commands, arguments, Lisp objects, and evaluation results can therefore become presentations with context-dependent mouse operations. The interactor is not simply a terminal emulator layered over a REPL: it participates in Genera's typed presentation system.

This design connects several behaviors that otherwise look unrelated:

• a displayed pathname, system, symbol, command, or object can supply input to a later command without being retyped;
• completion operates over typed populations;
• pointer documentation can describe operations appropriate to the object beneath the mouse; and
• command arguments can constrain which presentation types are acceptable at that point in an interaction.

The running world's Help Commands display reported 40 command areas. They are command-table categories, not 40 standalone applications:

Complete configured base Input Editor bindings

The following tables enumerate every configured base entry found by the source audit, including hardware-key names and modifier variants. A gesture can be shadowed by a more specific active input context. “Configured” is deliberate: the Input Editor's command alist is localizable and globally modifiable, and some useful implementation commands are defined without being assigned a base gesture.

Notation uses C-, M-, and S- for Control, Meta, and Super. Shift is written out where it is part of the key identity. Names such as Line, Page, Scroll, Back-Scroll, Clear Input, Complete, and Overstrike refer to Symbolics keyboard characters, not generic PC-key labels.

Additional Lisp-structure bindings supplied by Zwei support

The Input Editor is not Zmacs, but it deliberately reuses a small part of Zwei. The inspected ie-commands module installs these additional Lisp-oriented operations:

The same module defines, but does not assign base gestures to, backward-up-list killing, generic symbol description, disassembly, and completion-internal helpers.

Findings that are easy to miss in manuals

• The Input Editor constructs a small temporary Zwei node and selects a Common Lisp or Zetalisp syntax table for structural operations. The Listener therefore gets syntax-aware movement without becoming a Zmacs buffer.
• Symbol completion considers both the package recorded for the input entry and the current package. Its implementation tries not to intern a new symbol merely as a side effect of asking for completion.
• Lisp-oriented yanking is whitespace-aware. It can insert separation appropriate to the surrounding input rather than treating every yank as a blind byte splice.
• Input Editor Help enumerates the active command alist. Because contexts can localize that alist, Help can be more authoritative for the current prompt than a printed global reference card.
• A command for displaying internal Input Editor state exists but is deliberately unbound in the base table. Static function-name inventories overstate the ordinary user interface if they ignore installation.
• The multiple-value history is updated after evaluation. During evaluation of the next form, // still denotes the preceding value list even though - already denotes the current form.
• The Listener rebinds ordinary and debugging streams to the window but intentionally leaves the trace stream alone. “All output goes to the Listener” is therefore too broad.

Runtime observations in Genera 8.5

A fresh isolated session named core-dossiers-20260718, generation 1, exercised the Listener, System Menu, Inspector, and Peek in one boot. Its Listener observations were made before opening the other applications.

The VLM ran in separate user, mount, network, PID, IPC, and hostname namespaces. The session had no external route or guest-visible host file service, and Xvfb did not advertise MIT-SHM. Bubblewrap exposed a read-only Guix store, the exact read-only helpers and X socket, and the writable private runtime. The two byte-exact X request substitutions and one local RFC 868 request/reply were observed and validated; the time responder exited zero. These controls reduce the native process's reach but do not claim a complete kernel security boundary.

,(values 17 23)

,(list * // - + ++ +++)

(17 NIL (LIST * // - + ++ +++) (VALUES 17 23) NIL NIL)

Scope limits and open questions

• The binding census covers the configured base source entries and the inspected Zwei integration. It does not dump every application-local Input Editor context in the world.
• The runtime probe exercised Command Preferred mode. The other three modes are established by source and documentation but were not separately demonstrated in this session.
• Presentation-sensitive mouse operations were not exhaustively enumerated because they depend on the displayed object type and current input context.
• The session was deliberately isolated and unconfigured. Network-, namespace-, printer-, mail-, and site-dependent commands being named in Help does not establish that those services were operational.

Sources

• Symbolics, Genera User's Guide, Genera 8, Dynamic Lisp Listener, Command Processor, and interactive input sections; verified 2026-07-18.
• Symbolics, Genera Workbook, Genera 8, Listener and command-interaction exercises; verified 2026-07-18.
• Symbolics, Programming the User Interface, Genera 8, presentations and interactive-stream context; verified 2026-07-18.
• Licensed local Genera 8.5 source and extracted Document Examiner help, identities recorded above; inspected 2026-07-18.
• Fresh core-dossiers-20260718 Genera Xvfb session, generation 1, input, image, and shutdown evidence recorded above; observed 2026-07-18.