problems noted trying to write a BDF font reader

[masinter]

I'm just noting problems here rather than getting distracted.

• [ ] if I remove version files rmver = find . -name "*~" -exec rm {} \; then xcl::*where-is-cash-files* points to the wrong version.
• [ ] ed(load) offers me the TEMPLATES definition but not FUNCTIONS. ed(load functions) offers to set a dummy definition. Need to call (MEDLEY-INIT-VARS) to fix
• [ ] after accidentally creating an SEDIT window for the TEMPLATES definition (a dummy xcl:defdefiner) then ED(CL:LOAD) in the interlisp window asks me Edit which (FUNCTIONS TEMPLATES) definition of CL:LOAD I want but then proceeds to wake up the DEFDEFINER window.
• [ ] WHEREIS(LOAD FNS T) looking for Interlisp shows DATABASEFNS and BOOTSTRAP. What is DATABASEFNS? Relation to MANAGER?
• [ ] in \CML-LOAD change "USER" to "XCL-USER" to pick up DEFPACKAGE etc
• [ ] cd reports back symbol instead of string or pathname
• [ ] pathnames print out as #.(PATHNAME "blahblah") instead of #p"blah blah"\
• [ ] Lots of times I see odd things in the PROMPTWINDOW for asking the user to drag out a region. Someties it's just "Exec" or some other string in quotes, where I imagine it was intended to ask "Please drag out a region ..."
• [ ] change \CML-LOAD to use (FIND-READTABLE "XCL") to see if that helps
• [ ] IL:DO-DISPATCH-MACRO uses the read-table, but we're missing at least #P for pathnames and #: for uninterned symbols.
• [ ] Masterscope kind of assumes that everything in its database is 'of interest', because you wouldn't do a 'FULLER.DATABASE' then. We need some way to restrict the database to things that came from a file of interest or a set of files? There is the 'AMONG' modifier but using it is awkward.
• [ ] Select region for SEdit window -- could mention what you're editing
• [ ] check print-array in hprint
• [ ] there' a function HASH-COLON but not called. I added it in SET-DEFAULT-HASHMACRO-SETTINGS
• [ ] I've now managed to read in the defpackage that uses #: to note uninterned symbols
• [ ] it skips over #+ #- resolving them about Xerox features -- is there a way to save those to files, like Interlisp comments?

stopping here to save these since GitHub doesn't keep backups

• [ ]