Number: 1211

Date: 23-May-84 17':08':37

Submitter: Sannella.PA


Subject: DWIM tries to interpret type-in as edit commands

Assigned To: MASINTER.PA


Status: Closed

In/By: Harmony

Problem Type: Design - UI

Impact: Annoying

Difficulty: Moderate

Frequency: Everytime

Priority: Hopefully

System: Programming Environment

Subsystem: DWIM



Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: '
["Sannella.PA" "21-Aug-84 18':06':52" Assigned% To': Status':(Fixed->Closed) In/By':]

Description: '
Date': 19 May 84 04':08 PDT'
Subject': Lisp': Why is %↑ not unbound?'
cc': Masinter'
Lisp System Date': 14-May-84 21':12':25'
Machine': Dorado (PASTEUR)'
Microcode version': 24,4'
Memory size': 10000'
Frequency': Always'
Impact': Annoying'
Should an AR be submitted on this?  Does any one understand what''s going on here?'
Type just ↑<CR> or %↑<CR> at LISPX.  It responds with some random associations, which vary from time to time; on particular instance gave'
and then dumped into DEdit on the proplist of "if". ???  '
Date': 19 MAY 84 21':35 PDT'
Subject': Re': Lisp': Why is %↑ not unbound?'
To':   JonL, LispSupport'
cc':   Masinter'
 In response to the message sent 19 MAY 1984 0408-PDT by'
 This is a longstanding problem. There is some arcane and obsolete code in DWIM which attempts to detect when you type in ''edit'' commands at the executive when you meant to be in the editor. It was dubious when the TTY editor was the only editor in town, but just downright wrong for DEDIT.'
I suspect that removing this growth will reqire a bit of delicate surgery. I would be happy to see an AR on the subject, Attn': Masinter, Priority': Hopefully.'
Date': 19 MAY 84 22':47 PDT'
Subject': minor surgery performed...'
To':   JonL, LispSupport'
I made two changes to DWIM':'
a) typing TTY editor commands to the top level will *NOT* send you into the editor. I think few users will miss this. DWIM is of necessity ''heuristic'', attempting to second guess what the user meant. However, this is one that, over time, has become wrong far mor often than right. Its one of the problems of DWIM that it has to grow and change as the rest of the system changes in order to do a good job of guessingwhat the user means.'
Now': I think I''ve completed the surgery, but I haven''t sewn the patient back together yet': I''m working on Maxc and have tested the new DWIM and macro expansion interpreted, but I have not compiled the new versions. They are DWIMIFY and MACROS on <LispCore>Sources>. '


Test Case: 

Edit-By: Sannella.PA

Edit-Date: 21-Aug-84 18':06':53