blanks in file:open recent:

[markklein]

I am running https://github.com/Clozure/ccl/releases/tag/v1.13 on Mac OS Sonoma 14.2

When I selected "open recent" from the file menu, it gives a list of blank lines:

Similarly, when I selected "open" from the file menu, some of the files (recently opened ones) are greyed out and can't be opened. They become available, however, if I just try a second time.

This is not an existential problem obviously, but it would be nice to fix.

[bperryman]

I've just tried this with 1.12.2 and the recent items are also blank. I haven't been able to reproduce the greyed out issue but that could just be dumb luck

[bperryman]

I'm not in any way an expert on mac os x development but googling a bit turned up the following:

https://forums.developer.apple.com/forums/thread/749684

This seems to indicate that the app would need to be code signed for the recent items to turn up.

[xrme]

It does look like code signing is the issue.

I built an app via (require 'cocoa-application), and then signed it via

% codesign -s "Developer ID Application: Matt Emerson (E2U65G9LFN)" Clozure\ CL64.app

I launched the app, and I observed that the Open Recent menu worked as expected.

If you have a Developer ID certificate, you can sign the app yourself by using your own Developer ID Application identity in this way. There's apparently a complicated way to generate and use a self-signed identity, too: https://developer.apple.com/library/archive/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG10

[markklein]

Matthew,

If you simply somehow send me the CL64 app you created and signed, would it work for me as it does for you? Or does it need to have my developer certificate (which I don't currently have).

I have an Intel Mac laptop running Sonoma 14.2.

Thanks,

Mark

On Aug 17, 2024, at 8:49 PM, R. Matthew Emerson @.***> wrote:

It does look like code signing is the issue. I built an app via (require 'cocoa-application), and then signed it via % codesign -s "Developer ID Application: Matt Emerson (E2U65G9LFN)" Clozure\ CL64.app

I launched the app, and I observed that the Open Recent menu worked as expected. If you have a Developer ID certificate, you can sign the app yourself by using your own Developer ID Application identity in this way. There's apparently a complicated way to generate and use a self-signed identity, too: https://developer.apple.com/library/archive/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG10 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

---

Mark Klein, PhD Massachusetts Institute of Technology http://cci.mit.edu/klein/

[xrme]

I built an app following scripts/make-standalone-app (only I signed with my own Developer ID Application identity).

It's at https://github.com/Clozure/ccl/releases/download/v1.13/Clozure.CL64.zip if you would like to try it. It is signed, but not notarized, so you'll get the warning dialog "Apple cannot check this app for malicious software" or whatever the message is. Use the usual trick of control-clicking on the app icon and choosing Open to get past that.

I made it on my macOS Sonoma 14.6.1 (23G93) system. It probably won't run on anything prior to Sonoma.

Maybe that'll help you.

[markklein]

Thanks!

I downloaded that app and indeed the open recent menu showed actual file names instead of blanks but whenever I close a window, it throws an error in the altconsole:

Unhandled exception 10 at 0x7ff813bfbc56, context->regs at #x70000a0f2fe0 Exception occurred while executing foreign code at objc_release + 22 received signal 10; faulting address: 0x4 ? for help [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: Current Thread Context Record (tcr) = 0x7fbd91331970 Control (C) stack area: low = 0x70000a074000, high = 0x70000a0f4000 Value (lisp) stack area: low = 0x2f8d9000, high = 0x2fb25000 Exception stack pointer = 0x70000a0f34b8 [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: [60258] Clozure CL kernel debugger: symbol name :

Unless there's a super-simple way to fix that, I'll stick with my previous version of CL64.

But thanks anyway for the pointer!

Mark

On Aug 19, 2024, at 12:50 PM, R. Matthew Emerson @.***> wrote:

I built an app following scripts/make-standalone-app (only I signed with my own Developer ID Application identity). It's at https://github.com/Clozure/ccl/releases/download/v1.13/Clozure.CL64.zip if you would like to try it. It is signed, but not notarized, so you'll get the warning dialog "Apple cannot check this app for malicious software" or whatever the message is. Use the usual trick of control-clicking on the app icon and choosing Open to get past that. I made it on my macOS Sonoma 14.6.1 (23G93) system. It probably won't run on anything prior to Sonoma. Maybe that'll help you. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

---

Mark Klein, PhD Massachusetts Institute of Technology http://cci.mit.edu/klein/

[xrme]

Sorry it didn't help. I'll delete that file from the release assets since it doesn't seem to work right.