-
-
Notifications
You must be signed in to change notification settings - Fork 27
Rmk103 font and related code updates #2216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Convention that files in full should be in library not lispusers
to control font coercion heuristics.
I checked out this PR on Linux Mint 22.1 Cinnamon and the apps sysout fails with the error
![]() I'm attaching the The Medley head:
The Maiko head on master:
|
Did you try loadup-full.sh ?
… On Jul 17, 2025, at 1:27 AM, Paolo Amoroso ***@***.***> wrote:
pamoroso
left a comment
(Interlisp/medley#2216)
<#2216 (comment)>
I checked out this PR on Linux Mint 22.1 Cinnamon and the apps sysout fails with the error File not found: MCCS error during GREET...:
***@***.***:~/medley/medley$ ./scripts/loadup-all.sh -apps
>>>>> START loadup-init
"/home/paolo/bin/lde" "/home/paolo/medley/medley/internal/loadups/starter.sysout" -id "loadup_init_1" -title "Medley::loadup_init_1" -g 1024x768 -sc 1024x768 -noscroll
MEDLEYDIR: "/home/paolo/medley/medley"
LOGINDIR: "/home/paolo/medley/medley/loadups/build/logindir"
GREET FILE: "/home/paolo/medley/medley/loadups/build/loadup-init.init"
REM.CM FILE: ""
VMEM FILE: "/home/paolo/medley/medley/loadups/build/logindir/vmem/lisp_loadup_init_1.virtualmem"
apps-sysout-error.png (view on web) <https://github.com/user-attachments/assets/81ce6676-b899-4083-b91b-3106571aadcf>
I'm attaching the loadups directory: loadups.zip <https://github.com/user-attachments/files/21288219/loadups.zip>
The Medley head:
commit b8b2108 (HEAD -> rmk103--Font-and-related-code-updates, origin/rmk103--Font-and-related-code-updates)
The Maiko head on master:
commit fc90838ad84a152bfc70ce1d091b13166d0bf0d5
—
Reply to this email directly, view it on GitHub <#2216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJNF2KYC5TTDB6LJORT3I5M7PAVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOBTGEZDOMZXGU>.
You are receiving this because you authored the thread.
|
With
![]() The |
(These were for the next phase)
I fetch and try it now.
MCCS is for the next phase, not for this PR. git wasn't removing it from my directory when I switched branches, so my loadups were OK.
… On Jul 17, 2025, at 9:28 AM, Paolo Amoroso ***@***.***> wrote:
pamoroso
left a comment
(Interlisp/medley#2216)
<#2216 (comment)>
With loadup-full.sh I get the same error File not found: MCCS error during GREET...:
***@***.***:~/medley/medley$ ./scripts/loadup-full.sh
>>>>> START loadup-init
"/home/paolo/bin/lde" "/home/paolo/medley/medley/internal/loadups/starter.sysout" -id "loadup_init_1" -title "Medley::loadup_init_1" -g 1024x768 -sc 1024x768 -noscroll
MEDLEYDIR: "/home/paolo/medley/medley"
LOGINDIR: "/home/paolo/medley/medley/loadups/build/logindir"
GREET FILE: "/home/paolo/medley/medley/loadups/build/loadup-init.init"
REM.CM FILE: ""
VMEM FILE: "/home/paolo/medley/medley/loadups/build/logindir/vmem/lisp_loadup_init_1.virtualmem"
loadup-full-error.png (view on web) <https://github.com/user-attachments/assets/63cbb89e-7f5d-4c20-916b-0a3aef3629b6>
The loadups directory: loadups.zip <https://github.com/user-attachments/files/21301093/loadups.zip>
—
Reply to this email directly, view it on GitHub <#2216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJOH5FBHKDGVPPMBD3T3I7FJHAVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOBUGY4DQNRUGQ>.
You are receiving this because you authored the thread.
|
I updated to commit f93cc9e and the apps sysout failed with the error
![]() The |
Thanks for pushing on this.
I just made a separate commit for MEDLEYFONTFORMAT, although according to GITFNS it was already there (locally).
I think there is a glitch in the way GITFNS and git interact when branches are changed. Old Medley version may be left around in the git directory, and GITFNS doesn't understand that they are not part of the new branch.
Would we get better behavior if GITFNS treated the git directory as {UNIX} instead of {DSK}, when it compares files with the working directory, or moves files around?
… On Jul 17, 2025, at 10:31 AM, Paolo Amoroso ***@***.***> wrote:
pamoroso
left a comment
(Interlisp/medley#2216)
<#2216 (comment)>
I updated to commit f93cc9e <f93cc9e> and the apps sysout failed with the error File not found: MEDLEYFONTFORMATerror during GREET...
***@***.***:~/medley/medley$ ./scripts/loadup-all.sh -apps
>>>>> START loadup-init
"/home/paolo/bin/lde" "/home/paolo/medley/medley/internal/loadups/starter.sysout" -id "loadup_init_1" -title "Medley::loadup_init_1" -g 1024x768 -sc 1024x768 -noscroll
MEDLEYDIR: "/home/paolo/medley/medley"
LOGINDIR: "/home/paolo/medley/medley/loadups/build/logindir"
GREET FILE: "/home/paolo/medley/medley/loadups/build/loadup-init.init"
REM.CM FILE: ""
VMEM FILE: "/home/paolo/medley/medley/loadups/build/logindir/vmem/lisp_loadup_init_1.virtualmem"
loadup-all-error.png (view on web) <https://github.com/user-attachments/assets/092b6c95-f4f8-4d0f-aa52-1d09f4d7ebe9>
The loadups directory: loadups.zip <https://github.com/user-attachments/files/21301852/loadups.zip>
—
Reply to this email directly, view it on GitHub <#2216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJPLJBAUST5CQ6QCAI33I7MVVAVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOBUHA3TSOJZGE>.
You are receiving this because you authored the thread.
|
OK, loadups work with the MEDLEYFONTFORMAT now present. Untracked files don't get deleted by git when you switch between branches, so if there's a new file that you forgot to commit then changing branches will leave it there and presumably GITFNS will think it's also in the branch it switched to. If a file was committed in one branch and then you switch to a branch where it doesn't exist then it will get deleted. I don't know that treating things as |
I updated to commit 51d2cc6 and the apps loadup failed with the error (the Medley window was closed):
The dribble files: loadups-dribble.zip |
Hmm, I see the same failure. It appears that it builds all the sysouts OK, including apps, but then fails when it is trying to do the aux.
And that phase fails even with loadup-all.sh, which only does the full before it does the aux.
It typescript shows a reference to loadups/build/logindir/vmem/lisp_loadup-aux_1.virtualmem, which doesn't exist. Could that be because the error happens before that should have been created, or is the error that it should have been created and it isn't there?
… On Jul 17, 2025, at 11:08 AM, Paolo Amoroso ***@***.***> wrote:
pamoroso
left a comment
(Interlisp/medley#2216)
<#2216 (comment)>
I updated to commit 51d2cc6 <51d2cc6> and the apps loadup failed with the error (the Medley window was closed):
***@***.***:~/medley/medley$ ./scripts/loadup-all.sh -apps
>>>>> START loadup-init
"/home/paolo/bin/lde" "/home/paolo/medley/medley/internal/loadups/starter.sysout" -id "loadup_init_1" -title "Medley::loadup_init_1" -g 1024x768 -sc 1024x768 -noscroll
MEDLEYDIR: "/home/paolo/medley/medley"
LOGINDIR: "/home/paolo/medley/medley/loadups/build/logindir"
GREET FILE: "/home/paolo/medley/medley/loadups/build/loadup-init.init"
REM.CM FILE: ""
VMEM FILE: "/home/paolo/medley/medley/loadups/build/logindir/vmem/lisp_loadup_init_1.virtualmem"
+++++ SUCCESS +++++
[...]
>>>>> START loadup-apps-from-full
"/home/paolo/bin/lde" "/home/paolo/medley/medley/loadups/build/full.sysout" -id "loadup_apps_from_full_1" -title "Medley::loadup_apps_from_full_1" -g 1024x768 -sc 1024x768 -noscroll
MEDLEYDIR: "/home/paolo/medley/medley"
LOGINDIR: "/home/paolo/medley/medley/loadups/build/logindir"
GREET FILE: "/home/paolo/medley/medley/greetfiles/NOGREET"
REM.CM FILE: "/home/paolo/medley/medley/loadups/build/loadup-apps-from-full.cm"
VMEM FILE: "/home/paolo/medley/medley/loadups/build/logindir/vmem/lisp_loadup_apps_from_full_1.virtualmem"
+++++ SUCCESS +++++
..... files created .....
-rw-rw-r-- 1 paolo paolo 12692 Jul 17 19:59 /home/paolo/medley/medley/loadups/build/apps.dribble
-rw-rw-r-- 1 paolo paolo 13494272 Jul 17 19:59 /home/paolo/medley/medley/loadups/build/apps.sysout
<<<<< END loadup-apps-from-full
Added RDSYS.~40~ to library
Linked RDSYS to RDSYS.~40~ in library
Added RDSYS.LCOM.~40~ to library
Linked RDSYS.LCOM to RDSYS.LCOM.~40~ in library
Added lisp.sysout to loadups
Added lisp.dribble to loadups
Added full.sysout to loadups
Added full.dribble to loadups
Added apps.sysout to loadups
Added apps.dribble to loadups
>>>>> START loadup-aux
"/home/paolo/bin/lde" "/home/paolo/medley/medley/loadups/full.sysout" -id "loadup_aux_1" -title "Medley::loadup_aux_1" -g 1024x768 -sc 1024x768 -noscroll
MEDLEYDIR: "/home/paolo/medley/medley"
LOGINDIR: "/home/paolo/medley/medley/loadups/build/logindir"
GREET FILE: "/home/paolo/medley/medley/greetfiles/NOGREET"
REM.CM FILE: "/home/paolo/medley/medley/loadups/build/loadup-aux.cm"
VMEM FILE: "/home/paolo/medley/medley/loadups/build/logindir/vmem/lisp_loadup_aux_1.virtualmem"
----- FAILURE loadup-aux-----
..... files created .....
<<<<< END loadup-aux
----- loadup-all: FAILURE -----
The dribble files: loadups-dribble.zip <https://github.com/user-attachments/files/21302489/loadups-dribble.zip>
—
Reply to this email directly, view it on GitHub <#2216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJO2PSC3XRYV5FQI3DL3I7RABAVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOBUHE3TMNRYGA>.
You are receiving this because you authored the thread.
|
It's failing the
|
Except for the relatively small additional code, the difference related to fonts is that it instantiates the medleyfontformats gacha 10 (after the makeinit) and helvetica 10 (in the lisp phase).
But those shouldn't really take any more time and shouldn't be noticeably bigger. Although those files now include all known glyphs in all character sets, only charset 0 is instantiated and it only has the additional bitmaps for characters that were not in the original displayfont/c0/ files and were therefore filled in from terminal/modern/classic (probably in the 8-bit part of the charset). But spacewise, that should be in the noise.
And there shouldn't be a noticeable difference in time, since getting charset 0 basically just validates the file headers, jumps to the charset dispatch vector, jumps to the charset, and reads the charset (mostly using BINS). It has to search for the file, but that should be a little bit faster, since DISPLAYFONTDIRECTORIES is smaller, and it should hit the medleyfont file on the first probe.
In the full-from-lisp phase, there is currently a little more going on, since there is old code there to precache a bunch of fonts and character sets. And it seems to hang up for a second or two a little later (maybe when it gets to grapher) where it may be trying to precalculate a bunch of font sizes.
The fonts in the full phase should take a bit longer now, because it is still going to the displayfont files from which it now does online the glyph-completion coercions that it never did before. Those will be precomputed when all the fonts are switched over.
But 1.5% bigger and 10% longer, I wouldn't have expected anything even close to that.
… On Jul 17, 2025, at 11:03 AM, Nick Briggs ***@***.***> wrote:
nbriggs
left a comment
(Interlisp/medley#2216)
<#2216 (comment)>
OK, loadups work with the MEDLEYFONTFORMAT now present.
lisp.sysout is now about 1.5% bigger and a full loadup takes about 10% longer than it used to. Not sure why.
Untracked files don't get deleted by git when you switch between branches, so if there's a new file that you forgot to commit then changing branches will leave it there and presumably GITFNS will think it's also in the branch it switched to. If a file was committed in one branch and then you switch to a branch where it doesn't exist then it will get deleted. I don't know that treating things as {unix} would help -- at least not that problem.
—
Reply to this email directly, view it on GitHub <#2216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJO3IW4UPYH2FSIXS4D3I7QQRAVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOBUHE3DENZTGU>.
You are receiving this because you authored the thread.
|
The space increase is reproducible, the time for a |
I pushed FILESETS again, give it another try.
I had to back out another reference to MCCS in EXPORTFILES, which is part of aux but not part of the loadup.
… On Jul 17, 2025, at 11:58 AM, Nick Briggs ***@***.***> wrote:
nbriggs
left a comment
(Interlisp/medley#2216)
<#2216 (comment)>
It's failing the -aux part because:
{DSK}<Users>briggs>Projects>medley>sources>FILESETS.;1
File created 17-Jul-2025 09:32:58
FILESETSCOMS
File not found: MCCS
4>
(IL:LOGOUT T 1)
—
Reply to this email directly, view it on GitHub <#2216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJL3OJ7RV4NSAYDJUBD3I7W5ZAVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOBVGEYDSMRYG4>.
You are receiving this because you authored the thread.
|
I'm testing the commits up to 28cf61a on Linux Mint 22.1 Cinnamon, nothing unusual so far. |
After updating to commit fa62d05 I still don't have anything unusual to report. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see notes
@masinter , I don't see any notes. Where are they? |
sorry they disappeared. I can reconstruct but mainly; the file PDFSTREAM was deleted from library (PDFSTREAM.LCOM remains). The ASSOC multilevel function changes were handled by another PR. |
My local builds were working, but my directory had the ~nn~ version without the Unix file.
wrt PDFSTREAM, my loadups were working but I saw that my local directory at only the I think something went wrong when I merged the PDFSTREAM PR into this. Anyway, try it now. |
wrt MULTI-ALIST, this PR moved it to the library. The GETMULTI PR #2245 is an updated version, simplified and with a new capability--out of step because this one was hanging out for so long. I could add the new version to this PR and delete the other one. But I'm expecting to be able just merge the new one into this after this is approved/merged. Will git prevent that? |
I updated to commit 455d714 and it's still looking good. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we establish the convention that TEdit files use .TEDIT consistently?
Does it make sense to document "changes" in the medley repository? In the future, will the 'changes' be relevant and useful? Or just detritus left over from one of several changes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does it make sense to update files that belong in 'obsolete'? The FX-80 is not something anyone will have.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I read somewhere in the documentation that the FX-80 driver, given its simplicity, is a good example to study for writing new types of IMAGESTREAM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remember Nick said something about 'subrs' (not compiled into current maiko) that implemented reading and writing binary bitmaps. I don't remember why these bitmap reading and writing are moved from here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it impossible to extract the MULTI-ALIST file changes into a separate PR?
Do the other changes depend on it? There are lots of commits, and it will be hard to sort out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the changes to MULTI-ALIST (now in library/MULTI-ALIST and related files) in PR #2216 can be separated from the other changes in that PR—but this would require creating a new pull request that contains only the MULTI-ALIST changes.
Currently, PR #2216 includes 52 changed files, covering a wide range of areas: font system architecture, font formats, compatibility updates, loadup sequence adjustments, and more. The MULTI-ALIST changes are just a subset among these many modifications.
To separate them:
- You (or the PR author) would need to create a new branch based on master (or the appropriate base), and cherry-pick or re-apply only the changes relevant to MULTI-ALIST (and its .LCOM/.TEDIT companions, if changed).
- You would then open a new PR just for those changes.
- The original PR (Rmk103 font and related code updates #2216) would need to drop those changes to avoid duplication/conflicts.
For a complete and up-to-date list of all files and changes in PR #2216, see: https://github.com/Interlisp/medley/pull/2216/files
Note: My API access is limited to 30 files at a time, so there may be more files changed than I can see directly. For the full set, use the GitHub link above.
The binary bitmaps were moved forward so that the medleyfont reader can call them (for the guaranteed display font (gacha 10)).
… On Aug 10, 2025, at 10:47 AM, Larry Masinter ***@***.***> wrote:
@masinter commented on this pull request.
On library/IMAGEOBJ <#2216 (comment)>:
I remember Nick said something about 'subrs' (not compiled into current maiko) that implemented reading and writing binary bitmaps. I don't remember why these bitmap reading and writing are moved from here.
—
Reply to this email directly, view it on GitHub <#2216 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJMGG6M54XTY4OQGKIL3M6ASPAVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTCMBTGY4TSNZTG4>.
You are receiving this because you authored the thread.
|
On FX-80DRIVER, it may well not be useful and may not have worked at all before these changes. But here I'm just trying to make sure that the failure isn't becaues of the font changes.
By the same token, what about PRESS and PRESSFROMNS? I assume that there is no future for PRESS, so should it be obsoleted?
… On Aug 10, 2025, at 10:43 AM, Larry Masinter ***@***.***> wrote:
@masinter commented on this pull request.
On library/FX-80DRIVER <#2216 (comment)>:
does it make sense to update files that belong in 'obsolete'? The FX-80 is not something anyone will have.
—
Reply to this email directly, view it on GitHub <#2216 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJJDJYLU6YESDNKJUZD3M6AEZAVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTCMBTGY4TQOBVGE>.
You are receiving this because you authored the thread.
|
The PRESS code is used to read PRESS format files containing bitmaps, it should not be obsoleted. |
Does it have code for reading information out of a press file, or just creating one?
… On Aug 10, 2025, at 9:05 PM, Nick Briggs ***@***.***> wrote:
nbriggs
left a comment
(Interlisp/medley#2216)
<#2216 (comment)>
The PRESS code is used to read PRESS format files containing bitmaps, it should not be obsoleted.
—
Reply to this email directly, view it on GitHub <#2216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJOAM3EMMDX4A5Z3LAD3NAI73AVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZTGIYTAMBZGA>.
You are receiving this because you authored the thread.
|
Looks as though the press file reader is in BITMAPFNS not PRESS. I still think keeping the PRESS functions around as useful.
… On Aug 10, 2025, at 10:56 PM, rmkaplan ***@***.***> wrote:
rmkaplan
left a comment
(Interlisp/medley#2216)
<#2216 (comment)>Does it have code for reading information out of a press file, or just creating one?
> On Aug 10, 2025, at 9:05 PM, Nick Briggs ***@***.***> wrote:
>
>
> nbriggs
> left a comment
> (Interlisp/medley#2216)
> <#2216 (comment)>
> The PRESS code is used to read PRESS format files containing bitmaps, it should not be obsoleted.
>
> —
> Reply to this email directly, view it on GitHub <#2216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJOAM3EMMDX4A5Z3LAD3NAI73AVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZTGIYTAMBZGA>.
> You are receiving this because you authored the thread.
>
—
Reply to this email directly, view it on GitHub <#2216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB6DAWLQHE6LZQJKPH5Y5N33NAWCBAVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZTGM2TIOBVGY>.
You are receiving this because you commented.
|
Commit 56cf738 doesn't fix the
![]() The backtrace:
|
Minor dependency on the new public interface for default paragraph looks
An unfortunate consequence of the TEDIT-LOOKS update to deal with the PLOOKS compile problem. These 2 files had a minor dependency on that, the new public interface for the default (empty-file opening) paragraph looks (TEDIT.DEFAULT.PARALOOKS).
… On Aug 11, 2025, at 12:24 PM, Paolo Amoroso ***@***.***> wrote:
pamoroso
left a comment
(Interlisp/medley#2216)
<#2216 (comment)>
Commit 56cf738 <56cf738> doesn't fix the PLOOKS issue for me on Linux Mint 22.1 Cinnamon. When I open DInfo from the background menu I get a break window with the error:
TYPE-MISMATCH
In CL::%%NOT-NONCOMPLEX-NUMBER-ERROR:
NIL is not a number
dinfo-error.png (view on web) <https://github.com/user-attachments/assets/96068868-8cd5-4a02-8e05-f4e6f2c61d72>
The backtrace:
OLDMOUSE/5(debug)BTV
CL::%%NOT-NONCOMPLEX-NUMBER-ERROR
IPLUS
TEXTOBJ {TEXTOBJ}#122,600
CH#1 1
LINE {L81/61864: NIL-NIL}
THISLINE {THISLINE}#121,177764
FONT {GACHA10-MRR/173,176734}
CLOOKS {CL100/17880:Gacha10}
TRUEASCENT 10
TRUEDESCENT 3
LM NIL
PLOOKS {PL81/64968:NI-NIL-NIL}
\TEDIT.FORMATLINE.EMPTY
TSTREAM #<IO Text Stream/127,114700>
CH#1 1
LINE {L81/61864: NIL-NIL}
REGION NIL
IMAGESTREAM #<Output Display Stream/146,41300>
FORMATTINGSTATE NIL
TEXTOBJ {TEXTOBJ}#122,600
OFFSET 0
TRUEASCENT -1
TRUEDESCENT -1
ASCENTB 0
DESCENTB 0
ASCENTC 0
DESCENTC 0
OVERHANG 0
SPACELEFT 0
TX 0
BOXSTREAM #<Output Display Stream/146,41300>
CHARLOOKS NIL
THISLINE {THISLINE}#121,177764
LINETYPE NIL
WIDTH NIL
WMARGIN NIL
SCALE NIL
PARALOOKS NIL
RIGHTMARGIN NIL
HASKERN NIL
PC NIL
CHARSLOT NIL
PREVSP NIL
1STLN NIL
CHNOB NIL
FORCED-END NIL
CHNO NIL
LX1 NIL
TX NIL
TXB NIL
FONT NIL
CHARSLOTB NIL
TABPENDING NIL
PREVHYPH NIL
PREVDHYPH NIL
START-OF-PIECE 1
UNBREAKABLE NIL
OLDPIECE {PIECE}#121,174744
OLDPCCHARSLEFT 0
OLDCARETLOOKS {CL100/17880:Gacha10}
FIRSTSEPR NIL
\TEDIT.FORMATLINE
PANE {WINDOW}#122,6664
TSTREAM #<IO Text Stream/127,114700>
PREVLINE {L81/61906: 0-0 FED}
\TEDIT.SUFFIXLINE.CREATE
TSTREAM #<IO Text Stream/127,114700>
PANE {WINDOW}#122,6664
LCHARLAST NIL
YBOT NIL
PREFIX {L81/61906: 0-0 FED}
\TEDIT.PANE.CREATELINES
PANE {WINDOW}#122,6664
TSTREAM #<IO Text Stream/127,114700>
PROPS (READONLY QUIET NOTITLE T TITLEMENUFN
DINFO.TITLEMENUFN)
AFTERPANE NIL
LCHAR1 NIL
TEXTOBJ {TEXTOBJ}#122,600
MENUPROP NIL
SEL {SEL: unset 101/30514}
LASTVISIBLE NIL
\TEDIT.WINDOW.SETUP
WINDOW {WINDOW}#122,6664
TSTREAM #<IO Text Stream/127,114700>
PROPS (READONLY QUIET NOTITLE T TITLEMENUFN
DINFO.TITLEMENUFN)
TEXTOBJ {TEXTOBJ}#122,600
FILEPTR 0
\TEDIT.OPENTEXTSTREAM.WINDOW
SI::*CLEANUP-FORMS* SI::RESETUNWIND
TSTREAM #<IO Text Stream/127,114700>
TEXTOBJ {TEXTOBJ}#122,600
TEDIT.GET.FINISHEDFORMS NIL
PRIMPANE NIL
START NIL
SI::*UNWIND-PROTECT*
TEXT NIL
WINDOW {WINDOW}#122,6664
START/PROPS NIL
END NIL
PROPS (READONLY QUIET NOTITLE T TITLEMENUFN
DINFO.TITLEMENUFN)
LISPXHIST NIL
SI::*RESETFORMS* NIL
RESETSTATE NIL
OPENTEXTSTREAM
GRAPH {DINFOGRAPH}#137,153640
NODE NIL
SEL NIL
OFF? T
WINDOW {WINDOW}#122,6664
FILENAME NIL
FROM NIL
TO NIL
PROPS (READONLY QUIET NOTITLE T TITLEMENUFN
DINFO.TITLEMENUFN)
OLD.TEXTSTREAM NIL
TEXTSTREAM NIL
FULLFILENAME NIL
DINFO.UPDATE.TEXT.DISPLAY
GRAPH {DINFOGRAPH}#137,153640
WINDOW {WINDOW}#122,6664
NO.FREEMENU? NIL
DINFO.SETUP.WINDOW
SI::*CLEANUP-FORMS* SI::RESETUNWIND
W {WINDOW}#122,6664
GRAPH {DINFOGRAPH}#137,153640
MONITORLOCK #<Lock DInfo/174,6570>
SI::*UNWIND-PROTECT*
GRAPH.OR.FILE {DINFOGRAPH}#137,153640
WINDOW.OR.REGION {WINDOW}#122,6664
SETUP.ONLY? T
NO.FREEMENU? NIL
LISPXHIST NIL
SI::*RESETFORMS* ((& NIL))
RESETSTATE NIL
DINFO
FROM.BACKGROUND? T
IRM.GET.DINFOGRAPH
*FORM* (IRM.GET.DINFOGRAPH T)
*ARGVAL* NIL
*TAIL* NIL
*FN* IRM.GET.DINFOGRAPH
\EVALFORM
\INTERNAL NIL
EVAL
SI::*CLEANUP-FORMS* SI::RESETUNWIND
SI::*UNWIND-PROTECT*
SI::*RESETFORMS* ((&))
DINFO.SELECT.GRAPH
*FORM* (DINFO.SELECT.GRAPH)
*ARGVAL* NIL
*TAIL* NIL
*FN* DINFO.SELECT.GRAPH
\EVALFORM
STKEVAL
ITEM (DInfo (DINFO.SELECT.GRAPH)
"Open a DInfo window for browsing documentation.")
FROMMENU {MENU}#131,70130
BUTTON RIGHT
DEFAULTWHENSELECTEDFN
MENU {MENU}#131,70130
ITEM (DInfo (DINFO.SELECT.GRAPH)
"Open a DInfo window for browsing documentation.")
BUTTON RIGHT
DOSELECTEDITEM
MENU {MENU}#131,70130
RELEASECONTROLFLG NIL
NESTEDFLG NIL
IMAGE {WINDOW}#122,15000
DSP #<Output Display Stream/146,41200>
MENU
FORM NIL
DOBACKGROUNDCOM
ARGS 1
WINDOW NIL
DOWINDOWCOM
\MHCOM NIL
\MHPROCESS NIL
\MHWINDOW NIL
\MOUSEBUSY T
WINDOW.MOUSE.HANDLER
\OLDTTY NIL
\MOUSEBUSY NIL
\MOUSE.PROCESS
*FORM* (\MOUSE.PROCESS)
*ARGVAL* NIL
*TAIL* NIL
*FN* \MOUSE.PROCESS
\EVALFORM
%#FORM# (\MOUSE.PROCESS)
*CURRENT-PROCESS* #<Process OLDMOUSE/174,11410>
HELPFLAG BREAK!
\CURRENTDISPLAYLINE 0
\#DISPLAYLINES 40
\LINEBUF.OFD #<IO Stream on T/174,55500>
*READTABLE* #<ReadTable INTERLISP/174,54714>
\PRIMTERMTABLE {TERMTABLEP}#174,47740
\PRIMTERMSA {CHARTABLE}#174,50000
TtyDisplayStream
#<Output Display Stream/127,125100>
SI::*RESETFORMS* NIL
\INTERRUPTABLE T
\TTYWINDOW NIL
READBUF NIL
\TERM.OFD #<Output Stream on T/167,134000>
*STANDARD-OUTPUT* #<Output Stream on T/167,134000>
*STANDARD-INPUT* #<IO Stream on T/174,55500>
\MAKE.PROCESS0
T
—
Reply to this email directly, view it on GitHub <#2216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJMGBFFIY2EM3BLIOTD3NDUVPAVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZWGU2TEMBTHA>.
You are receiving this because you authored the thread.
|
It fixed "MAN RSTRING" and "(RSTRING ?", but yes I also see the "NIL IS NOT A NUMBER" error if I try to start DInfo from the background menu. |
I pushed another commit, try that. LOAD(TEDIT-STREAM.LCOM).
… On Aug 11, 2025, at 2:32 PM, Nick Briggs ***@***.***> wrote:
nbriggs
left a comment
(Interlisp/medley#2216)
<#2216 (comment)>
It fixed "MAN RSTRING" and "(RSTRING ?", but yes I also see the "NIL IS NOT A NUMBER" error if I try to start DInfo from the background menu.
—
Reply to this email directly, view it on GitHub <#2216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQSTUJOURXR7HK6O6YIILP33NEDVTAVCNFSM6AAAAACBT3AQUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZWHE3DEMBQGI>.
You are receiving this because you authored the thread.
|
@masinter wondered about the extension for Tedit files. The put tries to suggest .TEDIT for formatted files, but it had a heuristic that said to lower-case if the file itself had any lower-case. That test was incorrect--it tested the whole file, including directory, and not just the name part. So if the concern was about seeing it suggest .tedit instead of .TEDIT, that will be fixed in the next Tedit PR. |
Commit 8e8d9a4 fixes all the issue for me: |
This includes changes to cleanup and simplify (somewhat) the interface and some of the internals of the FONT architecture. It also includes MEDLEYFONTFORMAT, the implementation of the new read/writable format for display and other device fonts. The changes to FONT are documented in docs/internal/FONTCODECHANGES.TEDIT, the document for MEDLEYFONTFORMAT is in docs/internal/MEDLEYFONTFORMAT.TEDIT.
Around this central core there are a bunch of files with small changes for compatibility with some of the font changes. E.g. the recursion surrounding the validation of font attributes has been flattened out, and almost all calls to \COERCEFONTDESC have been eliminated (addressing #2100).
And the loadup sequences and have been adjusted and a few functions have been moved so that medley-format fonts can be included in the MAKEINIT.
This PR includes only 2 medley-format fonts, for GACHA10 and HELVETICA10. GACHA10 is created in the MAKEINIT. HEVETICA10 a little later, when MENU is loaded. I've included them here to test that everything hangs together.
(Separately, I have created medley-format fonts for all the display fonts, but I want to release those in a separate PR after this code has settled down. The new NS fonts will be MCCS-encoded, and that will require some other adjustments.)