Issues with macOS 14 Sonoma
When using Jedit Ω on macOS 14 Sonoma, the program may crash when performing the following operations:
Operation while Alphanumeric indicator is displayed
Pressing the alphanumeric key displays a blue "A" mark near the cursor. Performing actions such as typing or pasting while this "A" mark is displayed and a region is selected may cause the program to crash. Please try entering keys after the "A" mark disappears. Note that crashes do not occur when no region is selected or when the blue "あ" mark indicating Japanese input mode is displayed.
Operation while Uppercase indicator is displayed
Pressing the caps lock key displays a blue "bold upward arrow" mark near the cursor, indicating uppercase input mode. Performing actions such as typing or pasting while this "bold upward arrow" mark is displayed and a region is selected may cause the program to crash. Please try entering keys after the "bold upward arrow" mark disappears. Crashes do not occur when no region is selected.
Workaround for the Issue
This issue seems to be related to the split view feature implemented in JeditΩ. Editing in the latter half of the split view window does not seem to cause this issue. Splitting the editing window can be done via the menu "View > Split View" or by using the split button at the top right of the editing window.
As of April 18, 2024, this bug appears to have been resolved in macOS Sonoma 14.5 Beta (23F5059e)!!! Please look forward to the official release of macOS Sonoma 14.5.
Our response to this issue
Our investigation has confirmed that this issue occurs not only with Jedit Ω but also with a simple editor (test program) that implement split view. We have consulted with Apple DTS (Developer Technical Support) and confirmed that it is a system bug. A bug report (FB13668983) has also been submitted regarding this split view system-related bug.
Unfortunately, as it is a system bug, there is nothing JeditΩ can do on its end, and we must wait for an OS update to resolve the bug.
As of April 18, 2024, this bug appears to have been resolved in macOS Sonoma 14.5 Beta (23F5059e)!!! Please look forward to the official release of macOS Sonoma 14.5.