Number: 141

Date: 17-Mar-84  0':26':17

Submitter: Sannella.PA

Source: JONL.PA

Subject: PRINTLEVEL UNDO-able from top level

Assigned To: JONL.PA

Attn: 

Status: Closed

In/By: Harmony

Problem Type: Documentation

Impact: Minor

Difficulty: 

Frequency: 

Priority: Perhaps

System: Language Support

Subsystem: Read and Print

Machine: 

Disk: 

Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: '
["Sannella" "20-Aug-84 18':51':54" Attn': Status':(Fixed->Closed) In/By':]

Description: '
Date':  1 JAN 84 03':42 PST'
From': JONL.PA'
Subject': two little addenda'
To':   LispCore^'
...'
Uh, also, I patched PRINTLEVEL to notice when it is being called "from'
top level", and it becomes "UNDO-able" in that case.  This is a minor'
kludge, but I don''t think every call wants to update the history list,'
and it''s sure a pain if you''re hacking around at LISPX and can''t undo'
some PRINTLEVEL call.'
'
-----'
'
Date':  1 Jan 84 16':52 PST'
From': vanMelle.pa'
Subject': Re': two little addenda'
In-reply-to': JONL.PA''s message of 1 JAN 84 03':42 PST'
To': JONL.PA'
cc': LispCore^.PA'
'
There is a much easier, less grody, and of course, official, way to make an arbitrary function FOO undoable on typein': define a function /FOO that is an undoable version of FOO, and then add (FOO . /FOO) to the variable LISPXFNS.  Thus define'
'
(/PRINTLEVEL (CARVAL CDRVAL)'
   ((LAMBDA (RESULT)'
	(UNDOSAVE (LIST (FUNCTION /PRINTLEVEL) RESULT))'
	RESULT)'
    (PRINTLEVEL CARVAL CDRVAL].'
'
I put this definition on UNDO and restored the old APRINT.'
'
	Bill'


Workaround: 

Test Case: 

Edit-By: Sannella

Edit-Date: 20-Aug-84 18':51':55