Re: Alternative workaround to macOS SIGABRT on exit?
Pavel Sanda <[email protected]>
| Newsgroups | gmane.editors.lyx.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Mar 19, 2026 at 11:11:26PM +0900, Koji Yokota wrote: > > 2026/03/19 20:31???Jean-Marc Lasgouttes <[email protected]>????????????: > > > > Le 19/03/2026 ?? 11:35, Scott Kostyshak a écrit : > >> On Thu, Mar 19, 2026 at 09:52:41AM +0900, Koji Yokota wrote: > >>> > >>>> 2026/03/18 16:54???Scott Kostyshak <[email protected]>????????????: > >>>> > >>>> On lyx-users Anders reports that the following does not trigger the > >>>> issue: > >>>> > >>>> command-sequence buffer-close-all; lyx-quit > >>>> > >>>> This suggests the idea that we can just call buffer-close-all inside of > >>>> lyx-quit, as done in the attached patch. > >>> > >>> Scott???s patch works well on macOS 26.3.1 (Apple M1 Pro) so seems right diagnosis. > >> Thanks for testing Koji! > > > > What happens if a file is modified? Is there a confirmation dialog? > > Yes, it works in that case too. As far as I tested around, I couldn???t find any problems. As I wrote in the earlier email - even in case you hit Cancel when asked about saving the data? I would expect that with menu>quit + cancel you are back in the app while in command-sequence you don't care for the return value of buffer-close-all and call lyx-quit again. Pavel -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel