Re: LyX 2.5.0 on windows closes immediately after pressing right arrow in math box

[Jean-Marc Lasgouttes]

Le 24/03/2026 à 23:05, Peter Eliaš a écrit :

variations:
1. if instead of '\alpha' I wrote 'x' then LyX behaved as expected
2. when I did something more with the empty document (don't remember 
exactly) then crash dump was created, shall I send it?


Dear Peter,

Thank you very much for the precise report. I think that it is fixed in 
the development code now. The fix will be in LyX 2.5.1.


If you have any other ways to make LyX crash, please tell us about them.

JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 on windows closes immediately after pressing right arrow in math box

[Richard Kimberly Heck]

On 3/24/26 6:05 PM, Peter Eliaš wrote:

Dear LyX developers,
I found the following buggy behavior of LyX 2.5.0.
Peter

environment:
Windows 11 Home
texlive 2025 installed for a single user only
LyX 2.5.0 installed using Windows Installer 
(LyX-250-Installer-1-x64.exe), for a single user only


what I did:
opened a new document, pressed Ctrl+M for creating a math box, wrote 
'\alpha' into the box, pressed right arrow key


This only happens when using the arrow key. If you hit space, it is fine.

2  lyx::MathRow::draw                     MathRow.cpp        346 0x8694fa
3  lyx::MathData::draw                    MathData.cpp       431 0x8342a5
4  lyx::InsetMathGrid::draw               InsetMathGrid.cpp  606 0x7cdd0a
5  lyx::InsetMathHull::draw               InsetMathHull.cpp  725 0x7e3b4d
6  lyx::RowPainter::paintInset            RowPainter.cpp     118 0x698ead
7  lyx::RowPainter::paintText             RowPainter.cpp     581 0x69bb49
8  lyx::TextMetrics::drawParagraph        TextMetrics.cpp    2086 0x70e330
9  lyx::TextMetrics::draw                 TextMetrics.cpp    1925 0x70d479
10 lyx::BufferView::draw                  BufferView.cpp     3929 0x50c58c
11 lyx::frontend::GuiWorkArea::paintEvent GuiWorkArea.cpp    1341 0xaeb6b1

No time now to bisect, but I can try to do it tomorrow.

That said, 616c5307a6, which is 256 commits back in November, is bad.

Riki

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 on windows closes immediately after pressing right arrow in math box

[Richard Kimberly Heck]

On 3/24/26 6:05 PM, Peter Eliaš wrote:

Dear LyX developers,
I found the following buggy behavior of LyX 2.5.0.
Peter

environment:
Windows 11 Home
texlive 2025 installed for a single user only
LyX 2.5.0 installed using Windows Installer 
(LyX-250-Installer-1-x64.exe), for a single user only


what I did:
opened a new document, pressed Ctrl+M for creating a math box, wrote 
'\alpha' into the box, pressed right arrow key


what happened:
LyX closes immediately, without creating crash dump


I can reproduce this on Fedora Linux. I'll see if I can get a backtrace.

Riki


--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Released

[Bernt Lie via lyx-devel]

Thanks for great work! I have made the switch, and all my recent changes in 
work flow worked immediately.

I will relatively soon check out nomenclature, etc. (I have not used that 
before — and there seemed to be some limitations in RC2).

From: lyx-users  on behalf of Richard Kimberly 
Heck via lyx-users 
Sent: Saturday, February 21, 2026 5:17 PM
To: lyx-annou...@lists.lyx.org ; LyX Developers 
; lyx-users 
Subject: LyX 2.5.0 Released

We are proud to announce the release the new LyX 2.5.0. The 2.5 series has a
rich set of new features compared to the 2.4 series. An overview of the new
features can be found here:

   https://wiki.lyx.org/LyX/NewInLyX25

This release also celebrates LyX's 30th anniversary, just a bit late: The
first versions were released in 1995.

As this release ships with new features, we strongly recommend that
packagers
of LyX on various platforms and distributions read RELEASE-NOTES in order to
get the new dependencies right. That file contains additional
information about
some of the changes from 2.4.x.

If a file from an earlier version of LyX is opened *and saved* with any
version
of 2.5.x, then the original file will automatically be backed up. The backup
file will be found in the backup directory, if one is set under
Tools> Preferences> Paths
or else in the same folder as the original file, if no backup directory
is set.

The file RELEASE-NOTES also lists some known issues and problems compared
to the current stable releases (LyX 2.4.x).

As with any major release, this one comes with a lot of new features but
also
some bugs. If you think you have found a bug in LyX 2.5.0, either email the
LyX developers' mailing list (lyx-devel at lists.lyx.org), or open a bug
report
at
   https://www.lyx.org/trac/wiki/BugTrackerHome
Please specify if the behavior you are reporting is different from
behavior in
a previous LyX version. Please note that we have had to disable registration
for new accounts due to spam. If you would like an account, email the
developers' list.

If you have trouble using LyX or have a question, consult the documentation
that comes with LyX (under Help) and the LyX wiki, which you
will find at https://wiki.lyx.org/. You can also send email to the LyX
users'
list (lyx-users at lists.lyx.org).

The LyX team.
https://www.lyx.org

--
lyx-users mailing list
lyx-us...@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Tarballs

[Yu Jin]

Am So., 8. Feb. 2026 um 19:53 Uhr schrieb Richard Kimberly Heck <
rikih...@gmail.com>:

> Here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/
>
> Please have a look and let me know if these are OK. And thanks to Pavel,
> especially, for doing some work to get everything ready.
>
> Hold off a bit on building binaries until we are sure these are final.
>

Builds and runs well on Windows too.
-- 
  Eugene
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Tarballs

[Niranjana K M]

Great work. Builds smoothly and runs nicely on Gentoo Linux.
Thank you all..

with regards
Niranjana

On Wed, Feb 11, 2026 at 1:06 AM Marco Atzeri  wrote:

> On 08/02/2026 19:52, Richard Kimberly Heck wrote:
> > Here:
> >
> > http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/
> >
> > Please have a look and let me know if these are OK. And thanks to Pavel,
> > especially, for doing some work to get everything ready.
> >
> > Hold off a bit on building binaries until we are sure these are final.
> >
>
> it builds fine on Cygwin
> --
> lyx-devel mailing list
> lyx-devel@lists.lyx.org
> https://lists.lyx.org/mailman/listinfo/lyx-devel
>
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Tarballs

[Marco Atzeri]

On 08/02/2026 19:52, Richard Kimberly Heck wrote:

Here:

http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/

Please have a look and let me know if these are OK. And thanks to Pavel, 
especially, for doing some work to get everything ready.


Hold off a bit on building binaries until we are sure these are final.



it builds fine on Cygwin
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Tarballs

[Scott Kostyshak]

On Mon, Feb 09, 2026 at 10:09:51AM +0100, Jean-Pierre Chrétien via lyx-devel 
wrote:
> Le 09/02/2026 à 00:04, Pavel Sanda a écrit :
> > On Sun, Feb 08, 2026 at 01:52:58PM -0500, Richard Kimberly Heck wrote:
> > > Please have a look and let me know if these are OK. And thanks to Pavel,
> > > especially, for doing some work to get everything ready.
> > 
> > Seems to work fine on oldstable debian. P
> 
> Same here with Debian stable.

Tested the xz on Ubuntu 25.04 and compiled a few manuals. Everything smooth.

Thanks to those working on the release!

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Tarballs

[Jean-Pierre Chrétien via lyx-devel]

Le 09/02/2026 à 00:04, Pavel Sanda a écrit :

On Sun, Feb 08, 2026 at 01:52:58PM -0500, Richard Kimberly Heck wrote:

Please have a look and let me know if these are OK. And thanks to Pavel,
especially, for doing some work to get everything ready.


Seems to work fine on oldstable debian. P


Same here with Debian stable.

--
Jean-Pierre

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Tarballs

[Pavel Sanda]

On Sun, Feb 08, 2026 at 01:52:58PM -0500, Richard Kimberly Heck wrote:
> Please have a look and let me know if these are OK. And thanks to Pavel,
> especially, for doing some work to get everything ready.

Seems to work fine on oldstable debian. P
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Pavel Sanda]

On Tue, Jan 27, 2026 at 09:03:06PM +0100, Pavel Sanda wrote:
> On Tue, Jan 27, 2026 at 12:05:52PM -0500, Richard Kimberly Heck wrote:
> > Can someone please check the announcement and make any changes that seem
> > needed? Are there new features we want to highlight there? I'll copy that
> > over into the news file for the website.
> > 
> > Can someone also handle the NEWS file? I'm not good at that sort of thing.

I fixed the NEWS, announcement looks fine to my eyes.

> I also see that all our documentation/examples/templates are stored
> in 2.4 format and can't remember if we accepted all changed & turned off
> the change tracking altogether.

Quick check of few manuals shows that we did not turn off change-tracking
yet.

Jean-Pierre are you by chance any closer with producing pdfs of 2.5 manuals
for wiki https://wiki.lyx.org/LyX/Manuals ?
(by no means showstopper for 2.5.0)

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Scott Kostyshak]

On Wed, Jan 28, 2026 at 01:20:01PM +0100, Kornel Benko wrote:
> Am Wed, 28 Jan 2026 13:10:01 +0100
> schrieb Scott Kostyshak :
> 
> > On Wed, Jan 28, 2026 at 11:53:14AM +0100, Kornel Benko wrote:
> > > Am Tue, 27 Jan 2026 21:03:06 +0100
> > > schrieb Pavel Sanda :
> > >   
> > > > Do we have as part of our test-suite run by Scott/Kornel check that all
> > > > the official lyx files export as pdfs?  
> > 
> > I generally only run the tests on master since that's what I try to work
> > off of and it's hard enough just keeping that test output clean (e.g.,
> > with regression due to TeX Live updates).
> > 
> > But yes, please always feel free to ask and I/Kornel can run the tests
> > on 2.5.x. Kornel's results suggest that things look pretty good for our
> > official docs. There are some failures with ja/Modules/Linguistics and
> > also ja/UserGuide but I'm not sure if that is due to a TL update.
> > 
> > > > Pavel  
> > > 
> > > I got the attached errors.  
> > 
> > The ed62816e-knitr-comment-beamer tests pass for me on 2.5.x branch.
> > 
> > I'm guessing the ed62816e-knitr-comment-beamer tests fail for you on master 
> > also?
> > 
> > Note that I haven't upgraded my TL system for a couple of weeks.
> > 
> > Scott
> 
> I have TL updated. The only one of ed62816e-knitr-comment-beamer is
> INVERTED.DOCBOOK.BEAMER_export/export/latex/lyxbugs-resolved/ed62816e-knitr-comment-beamer_docbook5
> which passes.
> I was only testing on master.

OK, I will upgrade TL and check probably next week.

I first need to clear some harddrive space. Before I upgrade TL, I
always copy the directory (about 10GB) so that I can revert if
necessary. Often there are failures, and I go back and forth sometimes
to check if LyX regression and to post different logs if making a bug
report.

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Kornel Benko]

Am Wed, 28 Jan 2026 13:10:01 +0100
schrieb Scott Kostyshak :

> On Wed, Jan 28, 2026 at 11:53:14AM +0100, Kornel Benko wrote:
> > Am Tue, 27 Jan 2026 21:03:06 +0100
> > schrieb Pavel Sanda :
> >   
> > > Do we have as part of our test-suite run by Scott/Kornel check that all
> > > the official lyx files export as pdfs?  
> 
> I generally only run the tests on master since that's what I try to work
> off of and it's hard enough just keeping that test output clean (e.g.,
> with regression due to TeX Live updates).
> 
> But yes, please always feel free to ask and I/Kornel can run the tests
> on 2.5.x. Kornel's results suggest that things look pretty good for our
> official docs. There are some failures with ja/Modules/Linguistics and
> also ja/UserGuide but I'm not sure if that is due to a TL update.
> 
> > > Pavel  
> > 
> > I got the attached errors.  
> 
> The ed62816e-knitr-comment-beamer tests pass for me on 2.5.x branch.
> 
> I'm guessing the ed62816e-knitr-comment-beamer tests fail for you on master 
> also?
> 
> Note that I haven't upgraded my TL system for a couple of weeks.
> 
> Scott

I have TL updated. The only one of ed62816e-knitr-comment-beamer is
INVERTED.DOCBOOK.BEAMER_export/export/latex/lyxbugs-resolved/ed62816e-knitr-comment-beamer_docbook5
which passes.
I was only testing on master.

Kornel


pgpfWzhS8p_28.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Scott Kostyshak]

On Wed, Jan 28, 2026 at 11:53:14AM +0100, Kornel Benko wrote:
> Am Tue, 27 Jan 2026 21:03:06 +0100
> schrieb Pavel Sanda :
> 
> > Do we have as part of our test-suite run by Scott/Kornel check that all
> > the official lyx files export as pdfs?

I generally only run the tests on master since that's what I try to work
off of and it's hard enough just keeping that test output clean (e.g.,
with regression due to TeX Live updates).

But yes, please always feel free to ask and I/Kornel can run the tests
on 2.5.x. Kornel's results suggest that things look pretty good for our
official docs. There are some failures with ja/Modules/Linguistics and
also ja/UserGuide but I'm not sure if that is due to a TL update.

> > Pavel
> 
> I got the attached errors.

The ed62816e-knitr-comment-beamer tests pass for me on 2.5.x branch.

I'm guessing the ed62816e-knitr-comment-beamer tests fail for you on master 
also?

Note that I haven't upgraded my TL system for a couple of weeks.

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Kornel Benko]

Am Tue, 27 Jan 2026 21:03:06 +0100
schrieb Pavel Sanda :

> On Tue, Jan 27, 2026 at 12:05:52PM -0500, Richard Kimberly Heck wrote:
> > Can someone please check the announcement and make any changes that seem
> > needed? Are there new features we want to highlight there? I'll copy that
> > over into the news file for the website.
> > 
> > Can someone also handle the NEWS file? I'm not good at that sort of thing.  
> 
> Will try to look, but unf very busy atm.
> 
> I also see that all our documentation/examples/templates are stored
> in 2.4 format and can't remember if we accepted all changed & turned off
> the change tracking altogether.
> 
> Do we have as part of our test-suite run by Scott/Kornel check that all
> the official lyx files export as pdfs?
> 
> Pavel

I got the attached errors.

Kornel


testerrors
Description: Binary data


pgpZynPOQ9w0m.pgp
Description: Digitale Signatur von OpenPGP
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Pavel Sanda]

On Tue, Jan 27, 2026 at 12:05:52PM -0500, Richard Kimberly Heck wrote:
> Can someone please check the announcement and make any changes that seem
> needed? Are there new features we want to highlight there? I'll copy that
> over into the news file for the website.
> 
> Can someone also handle the NEWS file? I'm not good at that sort of thing.

Will try to look, but unf very busy atm.

I also see that all our documentation/examples/templates are stored
in 2.4 format and can't remember if we accepted all changed & turned off
the change tracking altogether.

Do we have as part of our test-suite run by Scott/Kornel check that all
the official lyx files export as pdfs?

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Pavel Sanda]

On Sun, Jan 18, 2026 at 10:05:29PM +0900, Yokota K. wrote:
> > 2026/01/18 11:03???Koji Yokota :
> > 
> > From this, I suspect this can be a problem between Qt 6 and Tahoe. I wonder 
> > placing a simple waiting timer only for macOS Tahoe before exiting can be a 
> > temporary workaround?
> 
> 
> The attached is a very dirty hack that simply waits for constant two seconds 
> before exiting. This removes a crash in *most* of the cases in normal 
> operations, but fails in very high load times, say right after the first 
> start after new installation.
> 
> Of course it would be ideal for waiting time to be conditioned on the 
> time-consuming process, but we may need to be reconciled to the optimized 
> fixed length.

As we do not have any better idea we should probably go with your 2s hack, but
commit it only to 2.5.x and leave master buggy, so we do not completely forget
about it.

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Pavel Sanda]

On Thu, Jan 08, 2026 at 11:20:41AM -0500, Richard Kimberly Heck wrote:
> > > > > What's the general view? We're ready?
> > > > > 
> > > > 
> > > > I think so.
> > > 
> > > OK, I will plan to package it in the next few days. Consider 2.5.x
> > > closed.
> > 
> > There is maybe the backport for https://www.lyx.org/trac/ticket/13272
> > 
> > That can wait for 2.5.1 I guess, but having it in 2.4.5 would be nice.
> 
> Go ahead. I won't get to this for a day or two.

BTW if you prepare the announcement first lyx releases were 1995, so with
this release we are passing 30y :)
P
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Richard Kimberly Heck]

On 1/18/26 8:05 AM, Yokota K. wrote:

2026/01/18 11:03、Koji Yokota のメール:

 From this, I suspect this can be a problem between Qt 6 and Tahoe. I wonder 
placing a simple waiting timer only for macOS Tahoe before exiting can be a 
temporary workaround?


The attached is a very dirty hack that simply waits for constant two seconds 
before exiting. This removes a crash in *most* of the cases in normal 
operations, but fails in very high load times, say right after the first start 
after new installation.

Of course it would be ideal for waiting time to be conditioned on the 
time-consuming process, but we may need to be reconciled to the optimized fixed 
length.


Once it's decided what to do about this, I'll do the release. It seems 
bad to have LyX constantly crashing on exit, even if it doesn't cause 
other problems. We'll get all kinds of complaints about it.


Riki


--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Yokota K.]

> 2026/01/18 11:03、Koji Yokota のメール:
> 
> From this, I suspect this can be a problem between Qt 6 and Tahoe. I wonder 
> placing a simple waiting timer only for macOS Tahoe before exiting can be a 
> temporary workaround?


The attached is a very dirty hack that simply waits for constant two seconds 
before exiting. This removes a crash in *most* of the cases in normal 
operations, but fails in very high load times, say right after the first start 
after new installation.

Of course it would be ideal for waiting time to be conditioned on the 
time-consuming process, but we may need to be reconciled to the optimized fixed 
length.

Koji



fix-exit.patch
Description: Binary data
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Koji Yokota]

> 2026/01/16 2:24、Jean-Marc Lasgouttes via lyx-devel 
> のメール:
> 
> I am lost now. I re-read the thread, but I missed how we went from "this is 
> signal-related" to "something is wrong with UndoGroupHelper".
> 
> Concerning signals, this is beyond my abilities. I guess the actions are held 
> somewhere in an object that is released to early.
> 
> Here is a hint though:
> https://github.com/jurplel/qView/issues/635
> together with a fix:
> https://github.com/jurplel/qView/commit/5044ead339ab4b90a3acededba2f57f582638bd4
> 
> Now the problem is to find out where we close the windows explicitly.
> 
> Does this ring a bell for someone?

I pulled out an old mac running macOS Ventura 13.7.8 and tested with LyX 
2.5-RC2 built on Qt 6.8.3. This case doesn’t seem to cause the exit problem.

Combination of macOS Tahoe and all Qt-6 variants I tested have the problem. 
Combination with Qt 5 cannot be tested since it requires old AGL framework.

From this, I suspect this can be a problem between Qt 6 and Tahoe. I wonder 
placing a simple waiting timer only for macOS Tahoe before exiting can be a 
temporary workaround?

Koji
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Jean-Marc Lasgouttes via lyx-devel]

Le 15/01/2026 à 17:03, Koji Yokota a écrit :

2026/01/15 16:31、Jean-Marc Lasgouttes のメール:

I think that I know what happens: the UndoGroupHelper is called after the 
destruction of the LyX singleton (which hold all global variables) and 
therefore it is the buffer list itself that does not exist anymore.

The attached patch tries to handle that. Can you give it a go?


Thanks, JMarc. I tested with the patch but unfortunately the problem still 
arises. I attach the log that macOS reports.

However, LyX correctly exits when I try to debug it step-by-step, so it seems 
something needs to be waited.


I am lost now. I re-read the thread, but I missed how we went from "this 
is signal-related" to "something is wrong with UndoGroupHelper".


Concerning signals, this is beyond my abilities. I guess the actions are 
held somewhere in an object that is released to early.


Here is a hint though:
https://github.com/jurplel/qView/issues/635
together with a fix:
https://github.com/jurplel/qView/commit/5044ead339ab4b90a3acededba2f57f582638bd4

Now the problem is to find out where we close the windows explicitly.

Does this ring a bell for someone?

JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Koji Yokota]

> 2026/01/15 16:31、Jean-Marc Lasgouttes のメール:
> 
> I think that I know what happens: the UndoGroupHelper is called after the 
> destruction of the LyX singleton (which hold all global variables) and 
> therefore it is the buffer list itself that does not exist anymore.
> 
> The attached patch tries to handle that. Can you give it a go?

Thanks, JMarc. I tested with the patch but unfortunately the problem still 
arises. I attach the log that macOS reports.

However, LyX correctly exits when I try to debug it step-by-step, so it seems 
something needs to be waited.

Koji
-
Translated Report (Full Report Below)
-
Process: lyx [63738]
Path:/Applications/LyX-2.5.0~RC2.app/Contents/MacOS/lyx
Identifier:  org.lyx.lyx
Version: 2.5.0~RC2 (???)
Code Type:   ARM-64 (Native)
Role:Foreground
Parent Process:  launchd [1]
Coalition:   org.lyx.lyx [226541]
User ID: 501

Date/Time:   2026-01-15 23:34:45.1356 +0900
Launch Time: 2026-01-15 23:26:55.4946 +0900
Hardware Model:  MacBookPro18,1
OS Version:  macOS 26.2 (25C56)
Release Type:User

Crash Reporter Key:  6D40D450-6C6C-22DB-C1DF-D9FF5BA4E28E
Incident Identifier: 551947E6-DB67-43B4-AE6A-E88F26A84A6D

Sleep/Wake UUID:   50CF7124-B23B-4EBD-87D9-E29AED08212A

Time Awake Since Boot: 160 seconds
Time Since Wake:   5125 seconds

System Integrity Protection: enabled

Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGABRT)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0029a21f
Exception Codes:   0x0001, 0x0029a21f

Termination Reason:  Namespace SIGNAL, Code 6, Abort trap: 6
Terminating Process: lyx [63738]


VM Region Info: 0x29a21f is not in any region.  Bytes before following region: 
4295925217
  REGION TYPESTART - END [ VSIZE] PRT/MAX 
SHRMOD  REGION DETAIL
  UNUSED SPACE AT START
--->  
  __TEXT  100384000-100be[ 8560K] r-x/r-x 
SM=COW  /Applications/LyX-2.5.0~RC2.app/Contents/MacOS/lyx

Application Specific Information:
abort() called


Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib 0x1986435b0 __pthread_kill + 8
1   libsystem_pthread.dylib0x19867d888 pthread_kill + 296
2   libsystem_c.dylib  0x198582850 abort + 124
3   lyx0x1004da48c 
lyx::error_handler(int) + 616
4   libsystem_platform.dylib   0x198687744 _sigtramp + 56
5   lyx0x1007e1b54 void 
QMetaObject::activate(QObject*, QMetaObject const*, int, void*, 
QAction* const&) + 28 (qobjectdefs.h:319) [inlined]
6   lyx0x1007e1b54 
lyx::frontend::Action::triggered(QAction*) + 28 (moc_Action.cpp:123) [inlined]
7   lyx0x1007e1b54 
lyx::frontend::Action::action() + 60 (Action.cpp:88) [inlined]
8   lyx0x1007e1b54 
lyx::frontend::Action::qt_static_metacall(QObject*, QMetaObject::Call, int, 
void**) + 188 (moc_Action.cpp:79)
9   lyx0x1007e1b54 void 
QMetaObject::activate(QObject*, QMetaObject const*, int, void*, 
QAction* const&) + 28 (qobjectdefs.h:319) [inlined]
10  lyx0x1007e1b54 
lyx::frontend::Action::triggered(QAction*) + 28 (moc_Action.cpp:123) [inlined]
11  lyx0x1007e1b54 
lyx::frontend::Action::action() + 60 (Action.cpp:88) [inlined]
12  lyx0x1007e1b54 
lyx::frontend::Action::qt_static_metacall(QObject*, QMetaObject::Call, int, 
void**) + 188 (moc_Action.cpp:79)
13  QtCore 0x10341b3e4 void 
doActivate(QObject*, int, void**) + 1468 (qobject.cpp:4269)
14  QtGui  0x101983544 void 
QMetaObject::activate(QObject*, QMetaObject const*, int, void*, 
bool const&) + 28 (qobjectdefs.h:319) [inlined]
15  QtGui  0x101983544 
QAction::triggered(bool) + 28 (moc_qaction.cpp:374) [inlined]
16  QtGui  0x101983544 
QAction::activate(QAction::ActionEvent) + 368
17  QtCore 0x103412d98 
QObject::event(QEvent*) + 672 (qobject.cpp:1413)
18  QtWidgets  0x1021b4014 
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 332 
(qapplication.cpp:3305)
19  QtWidgets  0x1021b506c 
QApplication::notify(QObject*, QEvent*) + 516 (qapplication.cpp:3255)
20  lyx0x100816bc8 
lyx::frontend::GuiApplication::notify(QObject*, QEvent*) + 28
21  QtCore  

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Jean-Marc Lasgouttes]

Le 20/12/2025 à 04:03, Koji Yokota a écrit :

2025/12/20 1:44、Jean-Marc Lasgouttes のメール:
It would be interesting to see what theBufferList().isLoaded(buf) and 
theBufferList().isInternal(buf) return in the helper destructor. The 
question is to know how it is possible to detect that the buffer has 
been destroyed.


Dear Koji,

I think that I know what happens: the UndoGroupHelper is called after 
the destruction of the LyX singleton (which hold all global variables) 
and therefore it is the buffer list itself that does not exist anymore.


The attached patch tries to handle that. Can you give it a go?

JMarc

diff --git a/src/BufferList.cpp b/src/BufferList.cpp
index 757bf46cf7..45485d59fc 100644
--- a/src/BufferList.cpp
+++ b/src/BufferList.cpp
@@ -42,13 +42,16 @@ namespace Alert = lyx::frontend::Alert;
 
 
 BufferList::BufferList()
-{}
+{
+	exists_ = true;
+}
 
 
 BufferList::~BufferList()
 {
 	for (Buffer * buf : binternal)
 		delete buf;
+	exists_ = false;
 }
 
 
diff --git a/src/BufferList.h b/src/BufferList.h
index 1384467c73..90725b37ba 100644
--- a/src/BufferList.h
+++ b/src/BufferList.h
@@ -131,6 +131,9 @@ public:
 	void invalidateConverterCache() const;
 	//@}
 
+	// Do we have a usable BufferList object?
+	static bool exists() { return exists_; }
+
 private:
 	/// create a new buffer
 	/// \return 0 if the Buffer creation is not possible for whatever reason.
@@ -146,6 +149,9 @@ private:
 	BufferStorage bstore;
 	/// storage of all internal buffers used for cut&paste, etc.
 	BufferStorage binternal;
+
+	/// has the (unique) BufferList instance been created?
+	static inline bool exists_ = false;
 };
 
 /// Implementation is in LyX.cpp
diff --git a/src/Undo.cpp b/src/Undo.cpp
index 69d85a7e5f..f2022c798e 100644
--- a/src/Undo.cpp
+++ b/src/Undo.cpp
@@ -713,9 +713,15 @@ UndoGroupHelper::UndoGroupHelper(CursorData & cur) : d(new UndoGroupHelper::Impl
 
 UndoGroupHelper::~UndoGroupHelper()
 {
-	for (Buffer * buf : d->buffers_)
-		if (theBufferList().isLoaded(buf) || theBufferList().isInternal(buf))
-			buf->undo().endUndoGroup();
+	/**
+	 * It may happen (in macOS, for instance) that the LyX singleton
+	 * is destroyed before this destructor is called. In this case,
+	 * one should not try, or need, to access the BufferList object.
+	 */
+	if (BufferList::exists())
+		for (Buffer * buf : d->buffers_)
+			if (theBufferList().isLoaded(buf) || theBufferList().isInternal(buf))
+buf->undo().endUndoGroup();
 	delete d;
 }
 
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Richard Kimberly Heck]

On 1/8/26 4:54 AM, Jean-Marc Lasgouttes wrote:

Le 07/01/2026 à 20:32, Richard Kimberly Heck a écrit :

On 1/7/26 10:30 AM, Jean-Marc Lasgouttes wrote:

Le 06/01/2026 à 17:51, Richard Kimberly Heck a écrit :

What's the general view? We're ready?



I think so.


OK, I will plan to package it in the next few days. Consider 2.5.x 
closed.


There is maybe the backport for https://www.lyx.org/trac/ticket/13272

That can wait for 2.5.1 I guess, but having it in 2.4.5 would be nice.


Go ahead. I won't get to this for a day or two.

Riki


--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jean-Marc Lasgouttes]

Le 07/01/2026 à 20:32, Richard Kimberly Heck a écrit :

On 1/7/26 10:30 AM, Jean-Marc Lasgouttes wrote:

Le 06/01/2026 à 17:51, Richard Kimberly Heck a écrit :

What's the general view? We're ready?



I think so.


OK, I will plan to package it in the next few days. Consider 2.5.x closed.


There is maybe the backport for https://www.lyx.org/trac/ticket/13272

That can wait for 2.5.1 I guess, but having it in 2.4.5 would be nice.

JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Richard Kimberly Heck]

On 1/7/26 10:30 AM, Jean-Marc Lasgouttes wrote:

Le 06/01/2026 à 17:51, Richard Kimberly Heck a écrit :

What's the general view? We're ready?



I think so.


OK, I will plan to package it in the next few days. Consider 2.5.x closed.

Riki


--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jean-Marc Lasgouttes]

Le 06/01/2026 à 17:51, Richard Kimberly Heck a écrit :

What's the general view? We're ready?



I think so.

JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jürgen Spitzmüller]

Am Dienstag, dem 06.01.2026 um 22:47 +0100 schrieb Scott Kostyshak:
> I've been doing my recent work on current master and I would say that
> is pretty stable, so I would assume 2.5.0 is.

Same here.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Scott Kostyshak]

On Tue, Jan 06, 2026 at 11:51:51AM -0500, Richard Kimberly Heck wrote:
> What's the general view? We're ready?

I haven't been following much. I've been doing my recent work on current
master and I would say that is pretty stable, so I would assume 2.5.0
is.

So no objection from me.

Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0-RC2

[Pavel Sanda]

On Fri, Dec 12, 2025 at 10:05:34AM +0100, Jean-Pierre Chrétien wrote:
> > We hope that this will be the last release candidate, and that LyX 2.5.0
> > itself will be released around the (western) New Year.
> 
> I'm afraid I was unable to update the French UserGuide before 2.5 is out. I
> will try to do it for 2.5.1.

There is still some time left :)
Jean-Pierre, would yo have time to update the wiki with 2.5 docs?
https://wiki.lyx.org/LyX/Manuals

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Koji Yokota]

2025/12/20 1:44、Jean-Marc Lasgouttes のメール:It would be interesting to see what theBufferList().isLoaded(buf) and theBufferList().isInternal(buf) return in the helper destructor. The question is to know how it is possible to detect that the buffer has been destroyed.After evaluation of the “for” sentence in ~UndoGroupHelper() (line 716), we have:d->buffers_ has 1 itembuf 			has an addresstheBufferList()	has an address	-> binternal	0items	-> bstore		0itemstheBufferList().isLoaded(buf)	theBufferList().isInternal(buf)	Do you see some backtrace leading to the destructors.I attach them to this mail.JMarcKoji1   lyx::UndoGroupHelper::~UndoGroupHelper()
 Undo.cpp   
718  0x1027077d4 
2   lyx::frontend::GuiApplication::dispatch(lyx::FuncRequest const&)
 GuiApplication.cpp 
1596 0x102945b6c 
3   lyx::frontend::Action::action() 
 Action.cpp 
87   0x102919d90 
4   lyx::frontend::Action::qt_static_metacall(QObject *, QMetaObject::Call, 
int, void * *)   moc_Action.cpp 
79   0x102919d78 
5   void doActivate(QObject *, int, void * *)
 qobject.cpp
4269 0x1055f33e4 
6   void QMetaObject::activate(QObject *, QMetaObject const *, int, 
void *, bool const&) qobjectdefs.h  
319  0x103b5b544 
7   QAction::triggered(bool)
 moc_qaction.cpp
374  0x103b5b528 
8   QAction::activate(QAction::ActionEvent) 
 qaction.cpp
 0x103b5b528 
9   QObject::event(QEvent *)
 qobject.cpp
1413 0x1055ead98 
10  QApplicationPrivate::notify_helper(QObject *, QEvent *) 
 qapplication.cpp   
3305 0x10438c014 
11  QApplication::notify(QObject *, QEvent *)   
 qapplication.cpp   
3255 0x10438d06c 
12  lyx::frontend::GuiApplication::notify(QObject *, QEvent *)  
 GuiApplication.cpp 
3046 0x10294ee28 
13  QCoreApplication::notifyInternal2(QObject *, QEvent *)  
 qcoreapplication.cpp   
1109 0x1055a0e78 
14  QCoreApplication::sendEvent(QObject *, QEvent *)
 qcoreapplication.cpp   
1549 0x1055a0dfc 
15  QCoreApplicationPrivate::sendPostedEvents(QObject *, int, QThreadData *)
 qcoreapplication.cpp   
1904 0x1055a1648 
16  QCocoaEventDispatcherPrivate::processPostedEvents() 
 qcocoaeventdispatcher.mm   
871  0x1053e31f8 
17  QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void *)
 qcocoaeventdispatcher.mm   
893  0x1053e4498 
18  __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__  
 (arm64e) 
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation   
   0x19871c9f8 
19  __CFRunLoopDoSource0
 (arm64e) 
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation   
   0x19871c98c 
20  __CFRunLoopDoSources0   
 (arm64e) 
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation   
   0x19871c6f8 
... 1   lyx::Buffer::~Buffer()
Buffer.cpp   517  0x10440172c 
2   lyx::BufferList::release(lyx::Buffer *)   
BufferList.cpp   97   0x10442f3b0 
3   lyx

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Jean-Marc Lasgouttes]

Le 19/12/2025 à 17:23, Koji Yokota a écrit :

I checked with the order of destructor calls. The destructor of Buffer class is 
called before that of UndoGroupHelper class, whereas UndoGroupHelper is 
dependent on Buffer class.

It seems the destructor of Buffer class should make it sure that all 
UndoGroupHelper classes have finished.


It would be interesting to see what theBufferList().isLoaded(buf) and 
theBufferList().isInternal(buf) return in the helper destructor. The 
question is to know how it is possible to detect that the buffer has 
been destroyed.


Do you see some backtrace leading to the destructors.

JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Koji Yokota]

>>> 2025/12/12 21:15、Koji Yokota のメール:
>>> 
>>> The crash seems to be caused by the sender of a signal that has disappeared 
>>> when doActivate() tries to do
>>> QObjectPrivate::get(sender)->blockSig
>>> (object.cpp:4139)

I checked with the order of destructor calls. The destructor of Buffer class is 
called before that of UndoGroupHelper class, whereas UndoGroupHelper is 
dependent on Buffer class.

It seems the destructor of Buffer class should make it sure that all 
UndoGroupHelper classes have finished.

Koji
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Yokota K.]

> 2025/12/16 22:31、Koji Yokota のメール:
> 
> When quitting LyX with an opened file, buffer disappears unexpectedly while 
> GuiApplication::dispatch(LFUN_LYX_QUIT) goes from
>   UndoGroupHelper ugh(buffer);(GuiApplication.cpp:1586)
> to
>   dispatch(cmd, dr);  
> (GuiApplication.cpp:1587).
> Therefore, when this function tries to return d->dispatch_result_, it doesn’t 
> exist.
> 
> The constructor of UndoGroupHelper calls UndoGroupHelper::resetBuffer(Buffer 
> * buf). When
>   d->buffers_.insert(buf);
> is executed, d->buffers_ does not exist (I think it was alive in the “if” 
> sentence one line before). After this line, this UndoGroupHelper class itself 
> and buf disappears.
> 
> In a normal quit case, d->buffers_.insert() normally finishes.
> 
> I wonder what causes this problem. Is there any other processes that touches 
> the buffer? Or simply buffer crashes?


In UndoGroupHelper::resetBuffer(Buffer * buf) (Undo.cpp:726),
d->buffers_.count(buf)
causes buf to become a null pointer. Before its execution, d->buffers_ exists 
and contains zero entries.

Adding a call of some buf's member functions before this line works fine, so 
this problem seems to relate to use of set::count().

Koji
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Koji Yokota]

> 2025/12/13 18:18、Koji Yokota のメール:
>> 2025/12/12 21:15、Koji Yokota のメール:
>> The crash seems to be caused by the sender of a signal that has disappeared 
>> when doActivate() tries to do
>>  QObjectPrivate::get(sender)->blockSig
>> (object.cpp:4139)
> 
> I see, lyx binary itself dies too early, but what can be done for this?

When quitting LyX with an opened file, buffer disappears unexpectedly while 
GuiApplication::dispatch(LFUN_LYX_QUIT) goes from
UndoGroupHelper ugh(buffer);(GuiApplication.cpp:1586)
to
dispatch(cmd, dr);  
(GuiApplication.cpp:1587).
Therefore, when this function tries to return d->dispatch_result_, it doesn’t 
exist.

The constructor of UndoGroupHelper calls UndoGroupHelper::resetBuffer(Buffer * 
buf). When
d->buffers_.insert(buf);
is executed, d->buffers_ does not exist (I think it was alive in the “if” 
sentence one line before). After this line, this UndoGroupHelper class itself 
and buf disappears.

In a normal quit case, d->buffers_.insert() normally finishes.

I wonder what causes this problem. Is there any other processes that touches 
the buffer? Or simply buffer crashes?

Koji
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0-RC2 -- remaining bug

[Jürgen Spitzmüller]

Am Freitag, dem 12.12.2025 um 11:39 +0100 schrieb Jürgen Spitzmüller:
> > If I mark a text, say "vena contracta", as Latin and try to PDF-
> > preview the document, I get the following error message:
> 
> As already answered on your previous report: this is not a LyX bug.
> Obiously your LaTeX installation is not up to date in all packages
> (particularly l3).

To be a bit more concrete: The check \sys_if_engine_opentype:TF was
introduced with version 2024-12-09 of l3kernel:
https://mailman.ctan.org/hyperkitty/list/ctan-...@ctan.org/message/5ZZKLFRBDWQVNJTNUFGPBEZDGNAUOSFK/

So make sure you have this version at least.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0-RC2 -- remaining bug

[Jürgen Spitzmüller]

Am Freitag, dem 12.12.2025 um 10:24 + schrieb Bernt Lie via lyx-
users:
> I previously reported a bug in LyX v2.5.0 RC1, and the bug is still
> there in RC2:
> 
> 
> If I mark a text, say "vena contracta", as Latin and try to PDF-
> preview the document, I get the following error message:

As already answered on your previous report: this is not a LyX bug.
Obiously your LaTeX installation is not up to date in all packages
(particularly l3).

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0-RC2 -- remaining bug

[Bernt Lie]

I previously reported a bug in LyX v2.5.0 RC1, and the bug is still there in 
RC2:

If I mark a text, say "vena contracta", as Latin and try to PDF-preview the 
document, I get the following error message:

[cid:0c1ccb9e-16cf-4c36-a137-2bc49909720d]

If I change the language to any other language (?), say Italian, the error 
message disappears.

-B

From: lyx-users  on behalf of Richard Kimberly 
Heck 
Sent: Thursday, December 11, 2025 4:57 PM
To: LyX Developers ; lyx-users 

Subject: LyX 2.5.0-RC2

Tarballs and binaries for LyX 2.5.0 RC2 are available here:

http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/

We hope that this will be the last release candidate, and that LyX 2.5.0
itself will be released around the (western) New Year.

What we really need testing of is the new work on Input Methods, which
are "used to input letters in languages whose number of characters
exceeds the number of keyboard keys", such as Japanese and Chinese. See

https://wiki.lyx.org/LyX/NewInLyX25#toc7

for some further information. Please let us know if you are able to test
this, and how it compares to LyX 2.4.x.

Riki


--
lyx-users mailing list
lyx-us...@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0-RC2

[Jean-Marc Lasgouttes]

Le 12/12/2025 à 10:05, Jean-Pierre Chrétien a écrit :
What we really need testing of is the new work on Input Methods, which 
are "used to input letters in languages whose number of characters 
exceeds the number of keyboard keys", such as Japanese and Chinese. See


https://wiki.lyx.org/LyX/NewInLyX25#toc7

for some further information. Please let us know if you are able to 
test this, and how it compares to LyX 2.4.x.


I think I can't test, it needs an appropriate keyboard, right ?


Well, dead keys like ^ are handled by input methods and are typical of 
what Koji did not test. I found a couple of issues that got fixed (like 
using ^^ to have a superscript in math).


JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0-RC2

[Jean-Pierre Chrétien]

Le 11/12/2025 à 16:57, Richard Kimberly Heck a écrit :

Tarballs and binaries for LyX 2.5.0 RC2 are available here:

http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/


Works fine on Debian Trixie, I'm able to compile an run the UserGuide.



We hope that this will be the last release candidate, and that LyX 2.5.0 itself 
will be released around the (western) New Year.


I'm afraid I was unable to update the French UserGuide before 2.5 is out. I will 
try to do it for 2.5.1.




What we really need testing of is the new work on Input Methods, which are "used 
to input letters in languages whose number of characters exceeds the number of 
keyboard keys", such as Japanese and Chinese. See


https://wiki.lyx.org/LyX/NewInLyX25#toc7

for some further information. Please let us know if you are able to test this, 
and how it compares to LyX 2.4.x.


I think I can't test, it needs an appropriate keyboard, right ?

--
Jean-Pierre

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Richard Kimberly Heck]

Unfortunately, I don't see any useful information there.

On 12/11/25 12:55 PM, Stephan Witt wrote:

For your convenience :)

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib 0x1918f35b0 __pthread_kill + 8
1   libsystem_pthread.dylib0x19192d888 pthread_kill + 296
2   libsystem_c.dylib  0x191832850 abort + 124
3   lyx0x102b468bc 
lyx::error_handler(int) + 364
4   libsystem_platform.dylib   0x191937744 _sigtramp + 56
5   lyx0x102dd6d98 
lyx::frontend::Action::action() + 80
6   lyx0x102dd6d98 
lyx::frontend::Action::action() + 80
7   QtCore 0x105c70cc4 void 
doActivate(QObject*, int, void**) + 1472
8   QtGui  0x103c59078 
QAction::activate(QAction::ActionEvent) + 368
9   QtCore 0x105c6915c 
QObject::event(QEvent*) + 644
10  QtWidgets  0x104705590 
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 336
11  QtWidgets  0x10470654c 
QApplication::notify(QObject*, QEvent*) + 504
12  lyx0x102dff590 
lyx::frontend::GuiApplication::notify(QObject*, QEvent*) + 28
13  QtCore 0x105c21ccc 
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 200
14  QtCore 0x105c22db4 
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 500
15  libqcocoa.dylib0x10546604c 
QCocoaEventDispatcherPrivate::processPostedEvents() + 360
16  libqcocoa.dylib0x10546729c 
QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 476
17  CoreFoundation 0x1919cc9e8 
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
18  CoreFoundation 0x1919cc97c __CFRunLoopDoSource0 
+ 172
19  CoreFoundation 0x1919cc6e8 
__CFRunLoopDoSources0 + 232
20  CoreFoundation 0x1919cb378 __CFRunLoopRun + 820
21  CoreFoundation 0x191a8535c 
_CFRunLoopRunSpecificWithOptions + 532
22  HIToolbox  0x19e488768 
RunCurrentEventLoopInMode + 316
23  HIToolbox  0x19e48b9b8 
ReceiveNextEventCommon + 272
24  HIToolbox  0x19e615308 
_BlockUntilNextEventMatchingListInMode + 48
25  AppKit 0x1962dc3c0 
_DPSBlockUntilNextEventMatchingListInMode + 236
26  AppKit 0x195dd5e34 _DPSNextEvent + 588
27  AppKit 0x1968a3f44 
-[NSApplication(NSEventRouting) 
_nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
28  AppKit 0x1968a3c50 
-[NSApplication(NSEventRouting) 
nextEventMatchingMask:untilDate:inMode:dequeue:] + 72
29  AppKit 0x195dce780 -[NSApplication run] 
+ 368
30  libqcocoa.dylib0x105464b7c 
QCocoaEventDispatcher::processEvents(QFlags) + 
2164
31  QtCore 0x105c2bba0 
QEventLoop::exec(QFlags) + 596
32  QtCore 0x105c224a8 
QCoreApplication::exec() + 144
33  lyx0x102b42860 lyx::LyX::exec(int&, 
char**) + 864
34  lyx0x102a42990 main + 76
35  dyld   0x191565d54 start + 7184


Am 11.12.2025 um 18:32 schrieb Richard Kimberly Heck :

FYI.


 Forwarded Message Subject: LyX 2.5.0 RC2 crash report Mac M2 
Tahoe 26.1
Date: Thu, 11 Dec 2025 18:03:21 +0100
From: Gerhard Gsänger via lyx-users 
Reply-To: Gerhard Gsänger 
To: lyx-us...@lists.lyx.org

Here is a concise and well-structured version suitable for a problem report:

Hi,
On my MacBook M2 running macOS Tahoe 26.1 I have a working installation of LyX 
2.4.4. Recently, I also installed LyX 2.5.0 RC1. Because of the known Qt6 
issue, I removed RC1 by dragging it from the Applications folder to the Trash.
Today I installed LyX 2.5.0 RC2 alongside the existing 2.4.4 installation.
LyX 2.5.0 RC2 starts normally. For some reason, it opened three files that I 
had previously opened in RC1. I am not sure whether this is relevant.
When I quit LyX 2.5.0 RC2, the program closes normally, but a few seconds later 
a crash report appears. After dismissing the crash report, I can restart LyX 
2.5.0 RC2 without any unusual behavior. Creating, saving, and opening documents 
(including files created under 2.4.4) works as expected.
However, each time I quit LyX 2.5.0 RC2, it terminates normally but a crash 
report 

Re: LyX 2.5.0 RC2 crash report Mac M2 Tahoe 26.1

[Stephan Witt]

For your convenience :)

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib 0x1918f35b0 __pthread_kill + 8
1   libsystem_pthread.dylib0x19192d888 pthread_kill + 296
2   libsystem_c.dylib  0x191832850 abort + 124
3   lyx0x102b468bc 
lyx::error_handler(int) + 364
4   libsystem_platform.dylib   0x191937744 _sigtramp + 56
5   lyx0x102dd6d98 
lyx::frontend::Action::action() + 80
6   lyx0x102dd6d98 
lyx::frontend::Action::action() + 80
7   QtCore 0x105c70cc4 void 
doActivate(QObject*, int, void**) + 1472
8   QtGui  0x103c59078 
QAction::activate(QAction::ActionEvent) + 368
9   QtCore 0x105c6915c 
QObject::event(QEvent*) + 644
10  QtWidgets  0x104705590 
QApplicationPrivate::notify_helper(QObject*, QEvent*) + 336
11  QtWidgets  0x10470654c 
QApplication::notify(QObject*, QEvent*) + 504
12  lyx0x102dff590 
lyx::frontend::GuiApplication::notify(QObject*, QEvent*) + 28
13  QtCore 0x105c21ccc 
QCoreApplication::notifyInternal2(QObject*, QEvent*) + 200
14  QtCore 0x105c22db4 
QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 500
15  libqcocoa.dylib0x10546604c 
QCocoaEventDispatcherPrivate::processPostedEvents() + 360
16  libqcocoa.dylib0x10546729c 
QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 476
17  CoreFoundation 0x1919cc9e8 
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
18  CoreFoundation 0x1919cc97c __CFRunLoopDoSource0 
+ 172
19  CoreFoundation 0x1919cc6e8 
__CFRunLoopDoSources0 + 232
20  CoreFoundation 0x1919cb378 __CFRunLoopRun + 820
21  CoreFoundation 0x191a8535c 
_CFRunLoopRunSpecificWithOptions + 532
22  HIToolbox  0x19e488768 
RunCurrentEventLoopInMode + 316
23  HIToolbox  0x19e48b9b8 
ReceiveNextEventCommon + 272
24  HIToolbox  0x19e615308 
_BlockUntilNextEventMatchingListInMode + 48
25  AppKit 0x1962dc3c0 
_DPSBlockUntilNextEventMatchingListInMode + 236
26  AppKit 0x195dd5e34 _DPSNextEvent + 588
27  AppKit 0x1968a3f44 
-[NSApplication(NSEventRouting) 
_nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
28  AppKit 0x1968a3c50 
-[NSApplication(NSEventRouting) 
nextEventMatchingMask:untilDate:inMode:dequeue:] + 72
29  AppKit 0x195dce780 -[NSApplication run] 
+ 368
30  libqcocoa.dylib0x105464b7c 
QCocoaEventDispatcher::processEvents(QFlags) + 
2164
31  QtCore 0x105c2bba0 
QEventLoop::exec(QFlags) + 596
32  QtCore 0x105c224a8 
QCoreApplication::exec() + 144
33  lyx0x102b42860 lyx::LyX::exec(int&, 
char**) + 864
34  lyx0x102a42990 main + 76
35  dyld   0x191565d54 start + 7184

> Am 11.12.2025 um 18:32 schrieb Richard Kimberly Heck :
> 
> FYI.
> 
> 
>  Forwarded Message Subject: LyX 2.5.0 RC2 crash report Mac M2 
> Tahoe 26.1
> Date: Thu, 11 Dec 2025 18:03:21 +0100
> From: Gerhard Gsänger via lyx-users 
> Reply-To: Gerhard Gsänger 
> To: lyx-us...@lists.lyx.org
> 
> Here is a concise and well-structured version suitable for a problem report:
> 
> Hi,
> On my MacBook M2 running macOS Tahoe 26.1 I have a working installation of 
> LyX 2.4.4. Recently, I also installed LyX 2.5.0 RC1. Because of the known Qt6 
> issue, I removed RC1 by dragging it from the Applications folder to the Trash.
> Today I installed LyX 2.5.0 RC2 alongside the existing 2.4.4 installation.
> LyX 2.5.0 RC2 starts normally. For some reason, it opened three files that I 
> had previously opened in RC1. I am not sure whether this is relevant.
> When I quit LyX 2.5.0 RC2, the program closes normally, but a few seconds 
> later a crash report appears. After dismissing the crash report, I can 
> restart LyX 2.5.0 RC2 without any unusual behavior. Creating, saving, and 
> opening documents (including files created under 2.4.4) works as expected.
> However, each time I quit LyX 2.5.0 RC2, it terminates normally but a crash 
> report appears a few seconds later.
> The most recent cr

RE: LyX 2.5.0 Release Candidate 1

[Bernt Lie]

LyX 2.5.0 RC1 on Windows 11, latest version

* For some weird reason, the UI color scheme changes from Default Mode to Light 
Mode when I close the lid on my laptop, and re-open the lid. 



-Original Message-
From: lyx-users  On Behalf Of Richard Kimberly 
Heck
Sent: Sunday, October 19, 2025 9:24 PM
To: lyx-users ; LyX Developers 
; lyx-annou...@lists.lyx.org
Subject: LyX 2.5.0 Release Candidate 1

We are pleased to announce the first release candidate for LyX 2.5.0. 
This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new things that 
will be in the final release.

Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/

Please note that LyX 2.5 needs Python 3.8 or newer to work.

Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org, which you may do by replying to this 
message.

For info on what's new in LyX 2.5, see:

     https://wiki.lyx.org/LyX/NewInLyX25

We'd especially appreciate testing of these new features!

Riki


--
lyx-users mailing list
lyx-us...@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Release Candidate 1: ... how do I return the background color of a cell back to default?

[Jürgen Spitzmüller]

Am Mittwoch, dem 19.11.2025 um 19:45 +0100 schrieb Jürgen Spitzmüller:
> Am Mittwoch, dem 19.11.2025 um 08:25 + schrieb Bernt Lie:
> > I have changed the settings for the row in a table, and want to
> > change it back to the default (no color) setting.
> > * If I go back to the cell color setting and choose "Default",
> > nothing changes.
> 
> This has already been reported and is fixed for the next release.

Actually reported by you:
https://marc.info/?l=lyx-devel&m=176156108812468&w=2

and I had already answered back then:
https://marc.info/?l=lyx-devel&m=176158584602493&w=2

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Release Candidate 1: ... how do I return the background color of a cell back to default?

[Jürgen Spitzmüller]

Am Mittwoch, dem 19.11.2025 um 08:25 + schrieb Bernt Lie:
> I have changed the settings for the row in a table, and want to
> change it back to the default (no color) setting.
> * If I go back to the cell color setting and choose "Default",
> nothing changes.

This has already been reported and is fixed for the next release.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 Release Candidate 1: ... how do I return the background color of a cell back to default?

[Bernt Lie]

... to answer myself: I exited LyX v2.5.0 RC1, and re-opened it. Then the color 
was as it should be. Perhaps a little counter-intuitive that I have to exit and 
re-start to see the effect?

-Original Message-
From: Bernt Lie 
Sent: Wednesday, November 19, 2025 9:25 AM
To: LyX Developers 
Subject: RE: LyX 2.5.0 Release Candidate 1: ... how do I return the background 
color of a cell back to default?

I have changed the settings for the row in a table, and want to change it back 
to the default (no color) setting.
* If I go back to the cell color setting and choose "Default", nothing changes.

-Original Message-
From: lyx-users  On Behalf Of Richard Kimberly 
Heck
Sent: Sunday, October 19, 2025 9:24 PM
To: lyx-users ; LyX Developers 
; lyx-annou...@lists.lyx.org
Subject: LyX 2.5.0 Release Candidate 1

We are pleased to announce the first release candidate for LyX 2.5.0. 
This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new things that 
will be in the final release.

Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/

Please note that LyX 2.5 needs Python 3.8 or newer to work.

Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org, which you may do by replying to this 
message.

For info on what's new in LyX 2.5, see:

     https://wiki.lyx.org/LyX/NewInLyX25

We'd especially appreciate testing of these new features!

Riki


--
lyx-users mailing list
lyx-us...@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 Release Candidate 1: ... how do I return the background color of a cell back to default?

[Bernt Lie]

I have changed the settings for the row in a table, and want to change it back 
to the default (no color) setting.
* If I go back to the cell color setting and choose "Default", nothing changes.

-Original Message-
From: lyx-users  On Behalf Of Richard Kimberly 
Heck
Sent: Sunday, October 19, 2025 9:24 PM
To: lyx-users ; LyX Developers 
; lyx-annou...@lists.lyx.org
Subject: LyX 2.5.0 Release Candidate 1

We are pleased to announce the first release candidate for LyX 2.5.0. 
This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new things that 
will be in the final release.

Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/

Please note that LyX 2.5 needs Python 3.8 or newer to work.

Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org, which you may do by replying to this 
message.

For info on what's new in LyX 2.5, see:

     https://wiki.lyx.org/LyX/NewInLyX25

We'd especially appreciate testing of these new features!

Riki


--
lyx-users mailing list
lyx-us...@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 Release Candidate 1 -- weird font color problem

[Bernt Lie]

LyX v2.5.0 RC1 on latest Windows 11/64 bit.



  *   I marked some text with red color in LyX. The text appears as red in LyX, 
but the math appears in black.
[cid:image001.png@01DC5570.9541D550]
  *   In the PDF previewer (PDFgear), both text and math appears in red:
[cid:image002.png@01DC5570.9541D550]
  *   On printed paper, the text appears as blueish/purple, while the math 
appears in red
[cid:image003.png@01DC5571.2AD5EAC0]



I don't think the printer is low on red - some plots with red color lines looks 
nice and red.









-Original Message-
From: lyx-users  On Behalf Of Richard Kimberly 
Heck
Sent: Sunday, October 19, 2025 9:24 PM
To: lyx-users ; LyX Developers 
; lyx-annou...@lists.lyx.org
Subject: LyX 2.5.0 Release Candidate 1



We are pleased to announce the first release candidate for LyX 2.5.0.

This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new things that 
will be in the final release.



Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/



Please note that LyX 2.5 needs Python 3.8 or newer to work.



Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org, 
which you may do by replying to this message.



For info on what's new in LyX 2.5, see:



https://wiki.lyx.org/LyX/NewInLyX25



We'd especially appreciate testing of these new features!



Riki





--

lyx-users mailing list

lyx-us...@lists.lyx.org

https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC1 frequent crashes

[Jean-Marc Lasgouttes]

Le 06/11/2025 à 23:39, Jean-Marc Lasgouttes a écrit :

Le 06/11/2025 à 16:42, Stephan Witt a écrit :

Hi Gerd,

yes I think it’s useful, many thanks. I’ll add the developers to the 
conversation.



Indeed. I can reproduce
1/ enable "cursor follows scrollbar"
2/ put cursor on an empty paragraph
3/ scroll with mouse wheel until empty paragraph is out of screen.


Fixed in master at 60aeb817ced9.

Riki, this is candidate for 2.5.x.

JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC1 frequent crashes

[Jean-Marc Lasgouttes]

Le 06/11/2025 à 16:42, Stephan Witt a écrit :

Hi Gerd,

yes I think it’s useful, many thanks. I’ll add the developers to the 
conversation.



Indeed. I can reproduce
1/ enable "cursor follows scrollbar"
2/ put cursor on an empty paragraph
3/ scroll with mouse wheel until empty paragraph is out of screen.

JMarc



Here is the interesting part of the backtrace:

0   libsystem_kernel.dylib 0x1975925b0 __pthread_kill + 8
1   libsystem_pthread.dylib0x1975cc888 pthread_kill + 296
2   libsystem_c.dylib  0x1974d2808 abort + 124
3   lyx0x104b8b018 lyx::lyx_exit(int) + 
20
4   lyx0x1050290f0 
lyx::doAssertWithCallstack(bool) + 48
5   lyx0x104c5b9ac 
lyx::Undo::Private::doRecordUndo(lyx::UndoKind, lyx::DocIterator const&, long, long, 
lyx::CursorData const&, lyx::UndoElementStack&) + 96
6   lyx0x104c5c3ac 
lyx::Undo::Private::recordUndo(lyx::UndoKind, lyx::DocIterator const&, long, long, 
lyx::CursorData const&) + 204
7   lyx0x104c23df0 
lyx::Text::deleteEmptyParagraphMechanism(lyx::Cursor&, lyx::Cursor&, bool&) + 
652
8   lyx0x104af2968 
lyx::BufferView::checkDepm(lyx::Cursor&, lyx::Cursor&) + 68
9   lyx0x104aeac9c 
lyx::BufferView::mouseSetCursor(lyx::Cursor&, bool) + 336
10  lyx0x104aeaa30 
lyx::BufferView::setCursorFromScrollbar() + 264
11  lyx0x104fc1448 
lyx::frontend::GuiWorkArea::scrollTo(int) + 84
12  QtCore 0x107de0cc4 void 
doActivate(QObject*, int, void**) + 1472
13  QtWidgets  0x106981a44 
QAbstractSlider::setValue(int) + 324
14  lyx0x104fc22c4 
lyx::frontend::GuiWorkArea::wheelEvent(QWheelEvent*) + 536

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC1 frequent crashes

[Stephan Witt]

Hi Gerd,

yes I think it’s useful, many thanks. I’ll add the developers to the 
conversation.

Here is the interesting part of the backtrace:

0   libsystem_kernel.dylib 0x1975925b0 __pthread_kill + 8
1   libsystem_pthread.dylib0x1975cc888 pthread_kill + 296
2   libsystem_c.dylib  0x1974d2808 abort + 124
3   lyx0x104b8b018 lyx::lyx_exit(int) + 
20
4   lyx0x1050290f0 
lyx::doAssertWithCallstack(bool) + 48
5   lyx0x104c5b9ac 
lyx::Undo::Private::doRecordUndo(lyx::UndoKind, lyx::DocIterator const&, long, 
long, lyx::CursorData const&, lyx::UndoElementStack&) + 96
6   lyx0x104c5c3ac 
lyx::Undo::Private::recordUndo(lyx::UndoKind, lyx::DocIterator const&, long, 
long, lyx::CursorData const&) + 204
7   lyx0x104c23df0 
lyx::Text::deleteEmptyParagraphMechanism(lyx::Cursor&, lyx::Cursor&, bool&) + 
652
8   lyx0x104af2968 
lyx::BufferView::checkDepm(lyx::Cursor&, lyx::Cursor&) + 68
9   lyx0x104aeac9c 
lyx::BufferView::mouseSetCursor(lyx::Cursor&, bool) + 336
10  lyx0x104aeaa30 
lyx::BufferView::setCursorFromScrollbar() + 264
11  lyx0x104fc1448 
lyx::frontend::GuiWorkArea::scrollTo(int) + 84
12  QtCore 0x107de0cc4 void 
doActivate(QObject*, int, void**) + 1472
13  QtWidgets  0x106981a44 
QAbstractSlider::setValue(int) + 324
14  lyx0x104fc22c4 
lyx::frontend::GuiWorkArea::wheelEvent(QWheelEvent*) + 536

Best regards
Stephan

> Am 05.11.2025 um 18:24 schrieb Gerhard Gsänger :
> 
> Stephan
> 
> Please find attached the most recent crash report.
> I hope it helps.
> 
> Gerd


lyx-2025-11-03-161928.ips
Description: Binary data
> 
>> Am 04.11.2025 um 23:30 schrieb Stephan Witt :
>> 
>> Am 04.11.2025 um 18:21 schrieb Richard Kimberly Heck :
>>> 
 On 11/3/25 6:54 PM, Richard Kimberly Heck wrote:
> On 11/3/25 12:43 PM, Gerhard Gsänger via lyx-users wrote:
>> I experience crashes every second day. Unfortunately I’m unable to 
>> describe how to duplicate the problem. Mac M2 OS Tahoe what can I do to 
>> provide better information.
> If you immediately write down what you were doing when the crash 
> occurred, that would help quite a lot. If you can run LyX from a 
> terminal, you may get some kind of backtrace, which could also help. Are 
> you running any background tools,


lyx-2025-11-03-161928.ips
Description: Binary data
>> 
> like clipboard managers or anything like that?
 
 From Gerhard:
 
 I have the impression that the crash occurs when I scrolled several lines 
 up or down. However. I’m not sure about that.
 
 I use Yoink in the background. I think this is what you called a clipboard 
 manager, isn’t it.
>>> I am not on Mac, so I do not know.
 For the troubleshooting, I will leave it tuned off for a while.
 
 Where can I find instructions for running LyX from a terminal and how to 
 access the backtrace. I will be happy to try it.
>>> Anyone on OSX who can explain how to do this?
>> 
>> Hi Gerhard,
>> 
>> on macOS you may start the application Console (or Konsole) and there a 
>> section with crash reports (or Absturzberichte) at the left of the window. 
>> Look for the crash reports of LyX - you should find them there and choose 
>> one to share it with mail.
>> 
>> BR Stephan
> 

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC 1

[Jürgen Spitzmüller]

Am Montag, dem 27.10.2025 um 17:15 +0100 schrieb Jürgen Spitzmüller:
> There seems to be a bug that this does not update the color in the
> LyX workarea until you save/reopen (will look into it)

Will be fixed with the next release.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC 1

[Jürgen Spitzmüller]

Am Montag, dem 27.10.2025 um 10:34 + schrieb Bernt Lie:
> * I have used different colors in the cells of the topmost row of a
> table. How can I change this back to the default of no specified
> color at all?

Select the cells and set the cell color to standard.

There seems to be a bug that this does not update the color in the LyX
workarea until you save/reopen (will look into it), but it is
immediately updated in the LaTeX output.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 RC 1

[Bernt Lie]

Question:
* I have used different colors in the cells of the topmost row of a table. How 
can I change this back to the default of no specified color at all?

I can, of course, create a new row and copy the content into this, but I am 
curious as to how I can change colors, and in particular back to no colors at 
all.

A related "problem" is when I specify colors to text. In the past, if I give a 
color to text, and then change that color, this seems to leave a "mess" in the 
.tex/.lyx code with color specification around color specification... i.e., it 
doesn't look like the original color specification is removed, instead a new 
color specification is wrapped around the original one. At least, that has been 
my impression -- I may be wrong.


-Original Message-
From: lyx-users  On Behalf Of Richard Kimberly 
Heck
Sent: Sunday, October 19, 2025 9:24 PM
To: lyx-users ; LyX Developers 
; lyx-annou...@lists.lyx.org
Subject: LyX 2.5.0 Release Candidate 1

We are pleased to announce the first release candidate for LyX 2.5.0. 
This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new things that 
will be in the final release.

Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/

Please note that LyX 2.5 needs Python 3.8 or newer to work.

Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org, which you may do by replying to this 
message.

For info on what's new in LyX 2.5, see:

     https://wiki.lyx.org/LyX/NewInLyX25

We'd especially appreciate testing of these new features!

Riki


--
lyx-users mailing list
lyx-us...@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Release Candidate 1 -- math: white background?

[Koji Yokota]

> 2025/10/22 16:21、Bernt Lie のメール:
> 
> I am playing around with LyX v2.5.0 RC1, and use default settings on Windows 
> 11/64 bit, latest update.
>  
> Except for simple in-line math, it seems like in-line and displayed math is 
> shown with white background
>  
> 
>  
> At least in the KOMA Book style I use. 
>  
> Is this intentional? Or a bug?
> I know v2.5.0 is supposed to have more options when it comes to UI color 
> schemes, but I don’t see this white background in the Help/Tutorial file.

Did you change the UI color theme after first preview is generated (i.e. after 
previews with white backgrounds are generated)? Even in that case, the normal 
behavior is that preview png files are regenerated to reflect new background 
color.

Koji-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Release Candidate 1

[Richard Kimberly Heck]

On 10/22/25 4:34 PM, Enrico Forestieri wrote:

On Wed, Oct 22, 2025 at 04:31:34AM +0200, Marco Atzeri wrote:

On 19/10/2025 21:23, Richard Kimberly Heck wrote:
We are pleased to announce the first release candidate for LyX 
2.5.0. This is 'feature complete': no new features will be added. 
Most of the translation work has also been finished, though there 
are some new things that will be in the final release.


Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/

Please note that LyX 2.5 needs Python 3.8 or newer to work.

Please test this version and let us know if you run into any 
problems by reporting them to lyx-devel@lists.lyx.org, which you may 
do by replying to this message.


Hi Richard,

the attached patch is needed to properly compile on Cygwin

It is equivalent to the current    2.4.3-winres.patch we are
using to build the cygwin binary package.

https://cygwin.com/cgit/cygwin-packages/lyx/tree/
https://cygwin.com/packages/summary/lyx-src.html

windres changed and now requires a different invocation.


Thanks Marco. So, seemingly, the corresponding windres bug
https://sourceware.org/bugzilla/show_bug.cgi?id=27594
will not get fixed?

My workaround has been using a script properly named:

$ cat "/usr/local/bin/gcc -E -xc-header -DRC_INVOKED"
#!/bin/sh
gcc -E -xc-header -DRC_INVOKED "$@"

but your patch is certainly right, whatever the resolution of that bug.

I committed it to master at 63f2e83f after changing 
--preprocessor="gcc" to --preprocessor="$(CC)", in order to account 
for cross-compilations, where the command might be 
"x86_64-w64-mingw32-gcc", for example.


Riki, this should be backported to the 2.4.x branch, too.


Cherry-picked.

Riki



--

Richard Kimberly (Riki) Heck
Professor of Philosophy and Professor of Linguistics
Brown University

Pronouns: they/them/their
Website:  http://rkheck.frege.org/

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Release Candidate 1

[Enrico Forestieri]

On Wed, Oct 22, 2025 at 04:31:34AM +0200, Marco Atzeri wrote:

On 19/10/2025 21:23, Richard Kimberly Heck wrote:
We are pleased to announce the first release candidate for LyX 
2.5.0. This is 'feature complete': no new features will be added. 
Most of the translation work has also been finished, though there 
are some new things that will be in the final release.


Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/

Please note that LyX 2.5 needs Python 3.8 or newer to work.

Please test this version and let us know if you run into any 
problems by reporting them to lyx-devel@lists.lyx.org, which you may 
do by replying to this message.


Hi Richard,

the attached patch is needed to properly compile on Cygwin

It is equivalent to the current 2.4.3-winres.patch we are
using to build the cygwin binary package.

https://cygwin.com/cgit/cygwin-packages/lyx/tree/
https://cygwin.com/packages/summary/lyx-src.html

windres changed and now requires a different invocation.


Thanks Marco. So, seemingly, the corresponding windres bug
https://sourceware.org/bugzilla/show_bug.cgi?id=27594
will not get fixed?

My workaround has been using a script properly named:

$ cat "/usr/local/bin/gcc -E -xc-header -DRC_INVOKED"
#!/bin/sh
gcc -E -xc-header -DRC_INVOKED "$@"

but your patch is certainly right, whatever the resolution of that bug.

I committed it to master at 63f2e83f after changing --preprocessor="gcc" 
to --preprocessor="$(CC)", in order to account for cross-compilations, 
where the command might be "x86_64-w64-mingw32-gcc", for example.


Riki, this should be backported to the 2.4.x branch, too.

--
Enrico
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 RC1 - User interface style

[Thibaut Cuvelier]

On Wed, 22 Oct 2025 at 09:54, Bernt Lie  wrote:

> Windows 11/64 bit latest update:
>
>
>
> I played around with User interface style. I tried windowsvista. When I
> try to change to nother style from windowsvista, the User interface style
> pop-up menu gets messed up:
>
>
>
>
>
> If I restart LyX, this messed up menu seems to disappear. I have seen such
> mess-up with other User interface style, too. Sometimes, but not always, I
> am told that I need to restart LyX (e.g., when switching back to Default).
>

I just installed the RC1, but I couldn't reproduce the issue :/. It looks
like a Qt or driver problem, though.
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 Release Candidate 1 -- math: white background?

[Bernt Lie]

Slight update: if I exit LyX, and restart it, then LyX re-builds the instant 
previews (this takes awhile). After the re-build, the white background seems to 
have disappeared.

From: Bernt Lie
Sent: Wednesday, October 22, 2025 9:21 AM
To: LyX Developers 
Subject: RE: LyX 2.5.0 Release Candidate 1 -- math: white background?


I am playing around with LyX v2.5.0 RC1, and use default settings on Windows 
11/64 bit, latest update.



Except for simple in-line math, it seems like in-line and displayed math is 
shown with white background



[cid:image001.png@01DC433E.51AD2F90]



At least in the KOMA Book style I use.



  *   Is this intentional? Or a bug?
  *   I know v2.5.0 is supposed to have more options when it comes to UI color 
schemes, but I don’t see this white background in the Help/Tutorial file.



-Original Message-
From: lyx-users 
mailto:lyx-users-boun...@lists.lyx.org>> On 
Behalf Of Richard Kimberly Heck
Sent: Sunday, October 19, 2025 9:24 PM
To: lyx-users mailto:lyx-us...@lists.lyx.org>>; LyX 
Developers mailto:lyx-devel@lists.lyx.org>>; 
lyx-annou...@lists.lyx.org<mailto:lyx-annou...@lists.lyx.org>
Subject: LyX 2.5.0 Release Candidate 1



We are pleased to announce the first release candidate for LyX 2.5.0.

This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new things that 
will be in the final release.



Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/



Please note that LyX 2.5 needs Python 3.8 or newer to work.



Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org<mailto:lyx-devel@lists.lyx.org>, 
which you may do by replying to this message.



For info on what's new in LyX 2.5, see:



https://wiki.lyx.org/LyX/NewInLyX25



We'd especially appreciate testing of these new features!



Riki





--

lyx-users mailing list

lyx-us...@lists.lyx.org<mailto:lyx-us...@lists.lyx.org>

https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 RC1 - User interface style

[Bernt Lie]

Windows 11/64 bit latest update:



I played around with User interface style. I tried windowsvista. When I try to 
change to nother style from windowsvista, the User interface style pop-up menu 
gets messed up:



[cid:image001.png@01DC4338.FF521030]



If I restart LyX, this messed up menu seems to disappear. I have seen such 
mess-up with other User interface style, too. Sometimes, but not always, I am 
told that I need to restart LyX (e.g., when switching back to Default).







-Original Message-
From: lyx-users  On Behalf Of Richard Kimberly 
Heck
Sent: Sunday, October 19, 2025 9:24 PM
To: lyx-users ; LyX Developers 
; lyx-annou...@lists.lyx.org
Subject: LyX 2.5.0 Release Candidate 1



We are pleased to announce the first release candidate for LyX 2.5.0.

This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new things that 
will be in the final release.



Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/



Please note that LyX 2.5 needs Python 3.8 or newer to work.



Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org, 
which you may do by replying to this message.



For info on what's new in LyX 2.5, see:



https://wiki.lyx.org/LyX/NewInLyX25



We'd especially appreciate testing of these new features!



Riki





--

lyx-users mailing list

lyx-us...@lists.lyx.org

https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 RC1 - Color Scheme

[Bernt Lie]

LyX v2.5.0 RC1 on Windows 11/64 bit, latest version.



I started to experiment with Color Scheme (see below), to see if that was 
related to the previously reported “problem” with white background for 
equations.



I installed LyX v2.5.0 RC1 without first deleting LyX v2.4.4, and later 
un-installed LyX v2.4.4. Up until now, LyX v2.5.0 RC1 has used exactly the same 
color scheme as in LyX v2.4.4. Then I have tried all of System Default, Light 
Mode, and Dark Mode. Switching between these models does not work smoothly: it 
appears to take time from I click on Apply to when the UI scheme changes, if it 
changes at all. The first time I tried Dark Mode, the background of the 
pull-down menu was black, and I cound’t see the text in the menu. After a 
couple of switches and restarts, that now seems to work. I have tried to switch 
back to System Default (is that the color scheme of LyX v2.4.4??). Sometimes, 
the UI colors change when I click on Apply or OK, but not always.

[cid:image001.png@01DC4337.981A3970]



In spite of the fragility, I have observed three different color schemes:
1. A pale scheme, which I suspect is the System Default

2. A Dark scheme

3. A light sandstone color – is that Light Mode?



-Original Message-
From: lyx-users  On Behalf Of Richard Kimberly 
Heck
Sent: Sunday, October 19, 2025 9:24 PM
To: lyx-users ; LyX Developers 
; lyx-annou...@lists.lyx.org
Subject: LyX 2.5.0 Release Candidate 1



We are pleased to announce the first release candidate for LyX 2.5.0.

This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new things that 
will be in the final release.



Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/



Please note that LyX 2.5 needs Python 3.8 or newer to work.



Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org, 
which you may do by replying to this message.



For info on what's new in LyX 2.5, see:



https://wiki.lyx.org/LyX/NewInLyX25



We'd especially appreciate testing of these new features!



Riki





--

lyx-users mailing list

lyx-us...@lists.lyx.org

https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 Release Candidate 1 -- math: white background?

[Bernt Lie]

I am playing around with LyX v2.5.0 RC1, and use default settings on Windows 
11/64 bit, latest update.



Except for simple in-line math, it seems like in-line and displayed math is 
shown with white background



[cid:image001.png@01DC4335.2FC96E10]



At least in the KOMA Book style I use.



  *   Is this intentional? Or a bug?
  *   I know v2.5.0 is supposed to have more options when it comes to UI color 
schemes, but I don’t see this white background in the Help/Tutorial file.



-Original Message-
From: lyx-users  On Behalf Of Richard Kimberly 
Heck
Sent: Sunday, October 19, 2025 9:24 PM
To: lyx-users ; LyX Developers 
; lyx-annou...@lists.lyx.org
Subject: LyX 2.5.0 Release Candidate 1



We are pleased to announce the first release candidate for LyX 2.5.0.

This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new things that 
will be in the final release.



Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/



Please note that LyX 2.5 needs Python 3.8 or newer to work.



Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org, 
which you may do by replying to this message.



For info on what's new in LyX 2.5, see:



https://wiki.lyx.org/LyX/NewInLyX25



We'd especially appreciate testing of these new features!



Riki





--

lyx-users mailing list

lyx-us...@lists.lyx.org

https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Release Candidate 1

[Marco Atzeri]

On 19/10/2025 21:23, Richard Kimberly Heck wrote:
We are pleased to announce the first release candidate for LyX 2.5.0. 
This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new 
things that will be in the final release.


Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/

Please note that LyX 2.5 needs Python 3.8 or newer to work.

Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org, which you may do by replying 
to this message.


Hi Richard,

the attached patch is needed to properly compile on Cygwin

It is equivalent to the current 2.4.3-winres.patch we are
using to build the cygwin binary package.

https://cygwin.com/cgit/cygwin-packages/lyx/tree/
https://cygwin.com/packages/summary/lyx-src.html

windres changed and now requires a different invocation.

Regards
Marco


--- origsrc/lyx-2.5.0~RC1/development/cygwin/Makefile.am2025-10-04 
21:00:02.0 +0200
+++ src/lyx-2.5.0~RC1/development/cygwin/Makefile.am2025-10-22 
03:18:59.435044300 +0200
@@ -5,7 +5,7 @@ include $(top_srcdir)/config/common.am
 
 .rc.o:
cp $(top_srcdir)/development/Win32/packaging/icons/lyx_*32x32.ico .
-   windres -I$(top_builddir) --preprocessor "$(CPP) -xc-header 
-DRC_INVOKED" $< -o $@
+   windres -I$(top_builddir) --preprocessor="gcc" --preprocessor-arg="-E" 
--preprocessor-arg="-xc-header" --preprocessor-arg="-DRC_INVOKED" $< -o $@
 
 bin_PROGRAMS = lyxeditor lyxwin
 bin_SCRIPTS = lyxeditor.sh
--- origsrc/lyx-2.5.0~RC1/src/Makefile.am   2025-10-04 21:00:02.0 
+0200
+++ src/lyx-2.5.0~RC1/src/Makefile.am   2025-10-22 03:19:50.227052600 +0200
@@ -43,7 +43,7 @@ if LYX_WIN_RESOURCE
 .rc.o:
cp $(top_srcdir)/development/Win32/packaging/icons/lyx.ico .
cp $(top_srcdir)/development/Win32/packaging/icons/lyx_doc.ico .
-   $(RC) -I$(top_builddir) --preprocessor "$(CPP) -xc-header -DRC_INVOKED" 
$< -o $@
+   $(RC) -I$(top_builddir) --preprocessor="gcc" --preprocessor-arg="-E" 
--preprocessor-arg="-xc-header" --preprocessor-arg="-DRC_INVOKED" $< -o $@
 endif
 
 if INSTALL_MACOSX
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Release Candidate 1: use of bowtie symbol gives trouble.

[Jürgen Spitzmüller]

Am Dienstag, dem 21.10.2025 um 20:06 +0200 schrieb Kees Zeelenberg:
> Exporting LyX's math manual to pdf (with pdflatex under Windows-11)
> leads to insertion of a line "\usepackage{mathrel⋈}" in the
> intermediate TeX-file. This leads to the error message that this file
> "mathrel⋈" cannot be found; in fact there is even not a file
> mathrel.sty in CTAN. This error is caused by the bowtie symbol in the
> table in section 14 of the math manual.
> With LyX-2.4.4, everything works fine.

Thanks, should be fixed.

You can fix it also easily locally by doing this change:
https://codeberg.org/LyX-org/lyx/commit/dc0d406c8ef14f25ce6c3d401c1323201379a69c

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 Release Candidate 1: use of bowtie symbol gives trouble.

[Kees Zeelenberg]

Exporting LyX's math manual to pdf (with pdflatex under Windows-11) leads to 
insertion of a line "\usepackage{mathrel⋈}" in the intermediate 
TeX-file. This leads to the error message that this file "mathrel⋈" 
cannot be found; in fact there is even not a file mathrel.sty in CTAN. This 
error is caused by the bowtie symbol in the table in section 14 of the math 
manual.
With LyX-2.4.4, everything works fine.

Kees

> -Oorspronkelijk bericht-
> Van: lyx-users  Namens Richard Kimberly Heck
> Verzonden: zondag 19 oktober 2025 21:24
> Aan: lyx-users ; LyX Developers  de...@lists.lyx.org>; lyx-annou...@lists.lyx.org
> Onderwerp: LyX 2.5.0 Release Candidate 1
> 
> We are pleased to announce the first release candidate for LyX 2.5.0.
> This is 'feature complete': no new features will be added. Most of the 
> translation
> work has also been finished, though there are some new things that will be in 
> the
> final release.
> 
> Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/
> 
> Please note that LyX 2.5 needs Python 3.8 or newer to work.
> 
> Please test this version and let us know if you run into any problems by 
> reporting
> them to lyx-devel@lists.lyx.org, which you may do by replying to this message.
> 
> For info on what's new in LyX 2.5, see:
> 
>  https://wiki.lyx.org/LyX/NewInLyX25
> 
> We'd especially appreciate testing of these new features!
> 
> Riki
> 
> 
> --
> lyx-users mailing list
> lyx-us...@lists.lyx.org
> https://lists.lyx.org/mailman/listinfo/lyx-users

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Release Candidate 1 -- weird footnote bug

[Jürgen Spitzmüller]

Am Dienstag, dem 21.10.2025 um 13:44 + schrieb Bernt Lie:
> I have a floating object with a frameless box inside, and a table
> inside this again: this allows for simple inclusion of footnotes in
> the table.
>  
> I have included a table footnote with an url environment, without
> problems:
>  
> url: https://en.wikipedia.org/wiki/Hydrogen
>  
> But the following table footnote with url, crashes the preview of the
> pdf file:
>  
> url: https://en.wikipedia.org/wiki/File:Hydrogen_Spectra.jpg

Use the workaround I already suggested to you in a different thread:

Add to Document > Settings > Local Layout:

InsetLayout Box:Frameless
NeedCProtect -1
End

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Release Candidate 1 -- bug

[Jürgen Spitzmüller]

Am Dienstag, dem 21.10.2025 um 12:17 + schrieb Bernt Lie:
> Bug in LyX 2.5.0 (and also in LyX 2.4.4, possibly earlier versions):
> 
> In one of my documents, I have marked some words as being of another
> language than my default language in the document (US English). I do
> this via the Edit/Language menu; the main purpose is to avoid
> spellchecker problems.
> 
> If I mark any word as any of the Latin versions of language, I get
> the following error message when trying to generate a pdf file:

This is not a bug in LyX. It looks like your LaTeX distribution is not
up to date.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0 Release Candidate 1 -- bug

[Scott Kostyshak]

On Tue, Oct 21, 2025 at 12:17:22PM +, Bernt Lie wrote:
> Bug in LyX 2.5.0 (and also in LyX 2.4.4, possibly earlier versions):
> 
> In one of my documents, I have marked some words as being of another language 
> than my default language in the document (US English). I do this via the 
> Edit/Language menu; the main purpose is to avoid spellchecker problems.
> 
> If I mark any word as any of the Latin versions of language, I get the 
> following error message when trying to generate a pdf file:
> 
> 
> >   \sys_if_engine_opentype:T
>  
> > The control sequence at the end of the top line
> > of your error message was never \def'ed. If you have
> > misspelled it (e.g., `\hobx'), type `I' and the correct
> > spelling (e.g., `I\hbox'). Otherwise just continue,
> > and I'll forget about whatever was undefined.

Hi Bernt,

Can you sen an example problem that gives a compilation error?

Thanks,
Scott


signature.asc
Description: PGP signature
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 Release Candidate 1 -- weird footnote bug

[Bernt Lie]

I have a floating object with a frameless box inside, and a table inside this 
again: this allows for simple inclusion of footnotes in the table.



I have included a table footnote with an url environment, without problems:



url: https://en.wikipedia.org/wiki/Hydrogen



But the following table footnote with url, crashes the preview of the pdf file:



url: https://en.wikipedia.org/wiki/File:Hydrogen_Spectra.jpg



[cid:image001.png@01DC42A1.2B51EEF0]

The offending character seems to be the underscore in the file name: if I 
change it to the (non-existent) fil File:HydrogenSpectra.jpg, then the pdf file 
previews.



If I take this url outside of the url box and include it as regular text, then 
there is no problem.



And if I use the footnote with the url outside of the frameless box/minipage, 
i.e., in a standard text line, there is no problem.









-Original Message-
From: lyx-users  On Behalf Of Richard Kimberly 
Heck
Sent: Sunday, October 19, 2025 9:24 PM
To: lyx-users ; LyX Developers 
; lyx-annou...@lists.lyx.org
Subject: LyX 2.5.0 Release Candidate 1



We are pleased to announce the first release candidate for LyX 2.5.0.

This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new things that 
will be in the final release.



Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/



Please note that LyX 2.5 needs Python 3.8 or newer to work.



Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org, 
which you may do by replying to this message.



For info on what's new in LyX 2.5, see:



https://wiki.lyx.org/LyX/NewInLyX25



We'd especially appreciate testing of these new features!



Riki





--

lyx-users mailing list

lyx-us...@lists.lyx.org

https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 Release Candidate 1 -- bug

[Bernt Lie]

Bug in LyX 2.5.0 (and also in LyX 2.4.4, possibly earlier versions):

In one of my documents, I have marked some words as being of another language 
than my default language in the document (US English). I do this via the 
Edit/Language menu; the main purpose is to avoid spellchecker problems.

If I mark any word as any of the Latin versions of language, I get the 
following error message when trying to generate a pdf file:


>   \sys_if_engine_opentype:T
 
> The control sequence at the end of the top line
> of your error message was never \def'ed. If you have
> misspelled it (e.g., `\hobx'), type `I' and the correct
> spelling (e.g., `I\hbox'). Otherwise just continue,
> and I'll forget about whatever was undefined.


-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

RE: LyX 2.5.0 Release Candidate 1

[Bernt Lie]

Perhaps silly questions...

* Should I remove LyX 2.4.4 before installing LyX 2.5.0 RC 1, or can they 
co-exist?
* Should I install Python 3.8 or newer on my Windows PC before installing LyX 
2.5.0? Will LyX find the Python installation, or do I need to include Python in 
the path? [I don't actively use Python, so I'm a little rusty on installing 
Python...]



-Original Message-
From: lyx-users  On Behalf Of Richard Kimberly 
Heck
Sent: Sunday, October 19, 2025 21:24
To: lyx-users ; LyX Developers 
; lyx-annou...@lists.lyx.org
Subject: LyX 2.5.0 Release Candidate 1

We are pleased to announce the first release candidate for LyX 2.5.0. 
This is 'feature complete': no new features will be added. Most of the 
translation work has also been finished, though there are some new things that 
will be in the final release.

Find it here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.5/

Please note that LyX 2.5 needs Python 3.8 or newer to work.

Please test this version and let us know if you run into any problems by 
reporting them to lyx-devel@lists.lyx.org, which you may do by replying to this 
message.

For info on what's new in LyX 2.5, see:

     https://wiki.lyx.org/LyX/NewInLyX25

We'd especially appreciate testing of these new features!

Riki


--
lyx-users mailing list
lyx-us...@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-users
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jürgen Spitzmüller]

Am Samstag, dem 05.07.2025 um 13:58 +0200 schrieb Jürgen Spitzmüller:
> > At the moment I see #12374 
> 
> #12394?

Oh, and #12374 as well (I wasn't considering the 2.4.x milestone).

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jürgen Spitzmüller]

Am Samstag, dem 05.07.2025 um 13:43 +0200 schrieb Pavel Sanda:
> it does not mean you should feel responsible for the bug. 

I didn't understand it that way, just wasn't sure which you had in
mind.

> At the moment I see #12374 

#12394? IMO this should be postponed, but it's Riki's call.

> (and obviously #13009 ;)

Yes. Normally, I'd opt for postponing as well. But then, we promised to
do something for so long, and it would be a rather trivial change.
Except that it requires a format change.

I could probably do it very quickly.

Let's see what Riki has to say about it.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Pavel Sanda]

On Sat, Jul 05, 2025 at 08:59:11AM +0200, Jürgen Spitzmüller wrote:
> > > From what I see there are 1-2 bugs left for Eugene & Juergen & me
> > > to decide,
> 
> Which do you have in mind? I had a look at the ramining bugs targeted
> at 2.5.0, but I don't see any where I feel addressed.

It was just based on the fact that you interacted and might have better idea
how to move forward with milestoning, it does not mean you should feel
responsible for the bug. At the moment I see #12374 (and obviously #13009 ;)

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jürgen Spitzmüller]

Am Freitag, dem 04.07.2025 um 21:10 +0200 schrieb Pavel Sanda:
> Ok, the zombies are gone now and I am mostly done with my crusade!

Thanks, very helpful!

> > From what I see there are 1-2 bugs left for Eugene & Juergen & me
> > to decide,

Which do you have in mind? I had a look at the ramining bugs targeted
at 2.5.0, but I don't see any where I feel addressed.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Pavel Sanda]

On Fri, Jul 04, 2025 at 02:09:00PM -0400, Richard Kimberly Heck wrote:
> On 7/4/25 1:02 PM, Pavel Sanda wrote:
> > On Fri, Jul 04, 2025 at 10:02:42AM +0200, Jürgen Spitzmüller wrote:
> > > It depends on when you want to announce feature freeze (I suggest: now)
> > My suggestion is this: I'll go and drop the zombied bugs.
> > 
> > Then we should go through the rest of milestoned ones and decide which ones 
> > we want to have in 2.5. I think there were few which would be worth to have.
> 
> Yes, thanks, good idea. Post a link to a list of them when it's ready.

Ok, the zombies are gone now and I am mostly done with my crusade!

(No special link for list necessary, just look at 
https://www.lyx.org/trac/wiki/BugTrackerHome
for section with 2.4.x and 2.5.0 milestone.)


>From what I see there are 1-2 bugs left for Eugene & Juergen & me to decide,
~10 bugs for JMarc to glance over and *lot of* bugs for Riki's review.

The Riki's plate does not seem to be realistic for 2.5, but that's
up to him to decide whether fix/retarget or drop the target ;)

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Richard Kimberly Heck]

On 7/4/25 1:02 PM, Pavel Sanda wrote:

On Fri, Jul 04, 2025 at 10:02:42AM +0200, Jürgen Spitzmüller wrote:

It depends on when you want to announce feature freeze (I suggest: now)

My suggestion is this: I'll go and drop the zombied bugs.

Then we should go through the rest of milestoned ones and decide which ones we 
want to have in 2.5. I think there were few which would be worth to have.


Yes, thanks, good idea. Post a link to a list of them when it's ready.

I'll plan to package beta1 in the next few days.

Riki


--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Pavel Sanda]

On Fri, Jul 04, 2025 at 10:02:42AM +0200, Jürgen Spitzmüller wrote:
> It depends on when you want to announce feature freeze (I suggest: now)

My suggestion is this: I'll go and drop the zombied bugs. 

Then we should go through the rest of milestoned ones and decide which ones we
want to have in 2.5. I think there were few which would be worth to have.

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jean-Marc Lasgouttes]

Le 04/07/2025 à 10:02, Jürgen Spitzmüller a écrit :

Am Donnerstag, dem 03.07.2025 um 17:26 -0400 schrieb Richard Kimberly
Heck:

At what point should we start thinking about translations?


After beta?

It depends on when you want to announce feature freeze (I suggest: now)
and string freeze (I suggest: after some beta feedback time).

After beta, it would also be a good idea to branch 2.5.x.


+1

JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jürgen Spitzmüller]

Am Donnerstag, dem 03.07.2025 um 17:26 -0400 schrieb Richard Kimberly
Heck:
> At what point should we start thinking about translations?

After beta?

It depends on when you want to announce feature freeze (I suggest: now)
and string freeze (I suggest: after some beta feedback time).

After beta, it would also be a good idea to branch 2.5.x.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Richard Kimberly Heck]

On 7/3/25 3:40 PM, José Matos wrote:

On Thu, 2025-07-03 at 19:34 +0200, Jürgen Spitzmüller wrote:

Am Donnerstag, dem 03.07.2025 um 10:56 -0400 schrieb Richard Kimberly
Heck:

OK. I guess we should discuss what we think the next steps are. We've
had some feedback on the alpha release, but not a lot. Should we try
a beta? I would have time to do that whenever.

Yes.

--
Jürgen

+1

It is a good idea.


At what point should we start thinking about translations?

Riki



--

Richard Kimberly (Riki) Heck
Professor of Philosophy and Professor of Linguistics
Brown University

Pronouns: they/them/their
Website:  http://rkheck.frege.org/

--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[José Matos]

On Thu, 2025-07-03 at 19:34 +0200, Jürgen Spitzmüller wrote:
> Am Donnerstag, dem 03.07.2025 um 10:56 -0400 schrieb Richard Kimberly
> Heck:
> > OK. I guess we should discuss what we think the next steps are. We've
> > had some feedback on the alpha release, but not a lot. Should we try
> > a beta? I would have time to do that whenever.
> 
> Yes.
> 
> -- 
> Jürgen

+1

It is a good idea. :-)
-- 
José Abílio
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jürgen Spitzmüller]

Am Donnerstag, dem 03.07.2025 um 10:56 -0400 schrieb Richard Kimberly
Heck:
> OK. I guess we should discuss what we think the next steps are. We've
> had some feedback on the alpha release, but not a lot. Should we try
> a beta? I would have time to do that whenever.

Yes.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Richard Kimberly Heck]

On 7/1/25 9:32 AM, Pavel Sanda wrote:

On Tue, Apr 29, 2025 at 02:33:31PM +0200, Pavel Sanda wrote:

Another thing I would like to propose to stop endlessly postponing major 
milestones.
Our bug lists grew over reasonable size.

...

I spend quite some time sorting out bugs for 2.4.0 and its' waisting time
for every new relase if no one touched the bug for a half a decade or more.
Moreover it makes it harder to focus on bugs which are more recent/relevant.

Hi Riki,

I am done with first pass of all bugs which had 2.5/2.4.x milestone.

Large part of bugs is in fact zombies with no one having time/real interest to 
fix them. Let us know once you start seriously moving towards 2.5, after those 
are dropped we will have realistic estimation what's ahead for us wrt 2.5.


OK. I guess we should discuss what we think the next steps are. We've 
had some feedback on the alpha release, but not a lot. Should we try a 
beta? I would have time to do that whenever.


Riki


--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Pavel Sanda]

On Tue, Jul 01, 2025 at 03:45:41PM +0200, Jean-Marc Lasgouttes wrote:
> Le 01/07/2025 ?? 15:32, Pavel Sanda a écrit :
> > Large part of bugs is in fact zombies with no one having time/real interest
> > to fix them. Let us know once you start seriously moving towards 2.5, after
> > those are dropped we will have realistic estimation what's ahead for us wrt 
> > 2.5.
> 
> Was it to be expected that we have only two bugs fixed for 2.5 here?
> https://www.lyx.org/trac/wiki/BugTrackerHome

Well, I closed those which fix were released in alpha1 so we keep track
of those which were targetted for the new release.
As Juergen pointed out it might not have been the brightest idea as
reporters might think we actually released useful release.

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jean-Marc Lasgouttes]

Le 01/07/2025 à 15:32, Pavel Sanda a écrit :

Large part of bugs is in fact zombies with no one having time/real interest
to fix them. Let us know once you start seriously moving towards 2.5, after
those are dropped we will have realistic estimation what's ahead for us wrt 2.5.


Was it to be expected that we have only two bugs fixed for 2.5 here?
https://www.lyx.org/trac/wiki/BugTrackerHome

JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Pavel Sanda]

On Tue, Apr 29, 2025 at 02:33:31PM +0200, Pavel Sanda wrote:
> Another thing I would like to propose to stop endlessly postponing major 
> milestones.
> Our bug lists grew over reasonable size.
...
> I spend quite some time sorting out bugs for 2.4.0 and its' waisting time
> for every new relase if no one touched the bug for a half a decade or more.
> Moreover it makes it harder to focus on bugs which are more recent/relevant.

Hi Riki,

I am done with first pass of all bugs which had 2.5/2.4.x milestone.

Large part of bugs is in fact zombies with no one having time/real interest
to fix them. Let us know once you start seriously moving towards 2.5, after
those are dropped we will have realistic estimation what's ahead for us wrt 2.5.

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0~alpha1

[Richard Kimberly Heck]

On 5/26/25 7:48 PM, José Matos wrote:

On Mon, 2025-05-26 at 19:00 -0400, Richard Kimberly Heck wrote:

So I was a bit confused about the naming conventions (thanks to Pavel
and Jürgen for setting me straight) and so have repackaged 'gamma 1' as
alpha 1. Please prepare binaries!

Riki

It is difficult for me to dissociate this from Star Trek's gamma and delta
quadrants (where the unknown lies). :-D

So with your most recent we are back to Earth. :-)


Or at least the Federation.

Riki


--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0~alpha1

[José Matos]

On Mon, 2025-05-26 at 19:00 -0400, Richard Kimberly Heck wrote:
> So I was a bit confused about the naming conventions (thanks to Pavel 
> and Jürgen for setting me straight) and so have repackaged 'gamma 1' as 
> alpha 1. Please prepare binaries!
> 
> Riki

It is difficult for me to dissociate this from Star Trek's gamma and delta
quadrants (where the unknown lies). :-D

So with your most recent we are back to Earth. :-)

SCNR.
-- 
José Abílio
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[José Matos]

On Tue, 2025-04-29 at 11:37 -0400, Richard Kimberly Heck wrote:
> This sounds reasonable to me.
> 
> Riki

FWIW I also agree.
-- 
José Abílio
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Richard Kimberly Heck]

On 4/29/25 8:33 AM, Pavel Sanda wrote:

On Mon, Apr 28, 2025 at 12:48:37PM -0400, Richard Kimberly Heck wrote:

If you think things are reasonably settled, I will do some kind of 'nightly'
package of 2.5.0, and see if we can get a bit of testing for it. Then we can
think about more concrete plans.

Another thing I would like to propose to stop endlessly postponing major 
milestones.
Our bug lists grew over reasonable size.

In particular we could drop the milestone altogether if bug
1) already had 2.4.0 milestone in the past and
2) does not have patch attached and
3) no one will respond to gently ping for finishing in 2.5 (or at least
explicitly plans to address it in 2.6) and
(4? not sure about this one) there was no reasonable debate/progress
in comments during 2.5 dev cycle

And similar policy for 2.4.x milestones. If something already had 2.3.x
milestone and no progress since then, lets drop the milestone.

I spend quite some time sorting out bugs for 2.4.0 and its' waisting time
for every new relase if no one touched the bug for a half a decade or more.
Moreover it makes it harder to focus on bugs which are more recent/relevant.

Opinions?


This sounds reasonable to me.

Riki


--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jean-Marc Lasgouttes]

Le 29/04/2025 à 14:33, Pavel Sanda a écrit :

Another thing I would like to propose to stop endlessly postponing major 
milestones.
Our bug lists grew over reasonable size.

In particular we could drop the milestone altogether if bug
1) already had 2.4.0 milestone in the past and
2) does not have patch attached and
3) no one will respond to gently ping for finishing in 2.5 (or at least
explicitly plans to address it in 2.6) and
(4? not sure about this one) there was no reasonable debate/progress
in comments during 2.5 dev cycle

And similar policy for 2.4.x milestones. If something already had 2.3.x
milestone and no progress since then, lets drop the milestone.

I spend quite some time sorting out bugs for 2.4.0 and its' waisting time
for every new relase if no one touched the bug for a half a decade or more.
Moreover it makes it harder to focus on bugs which are more recent/relevant.


As someone who just went through the 2.5 bugs list, I agree to 1-4.

JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Pavel Sanda]

On Mon, Apr 28, 2025 at 12:48:37PM -0400, Richard Kimberly Heck wrote:
> If you think things are reasonably settled, I will do some kind of 'nightly'
> package of 2.5.0, and see if we can get a bit of testing for it. Then we can
> think about more concrete plans.

Another thing I would like to propose to stop endlessly postponing major 
milestones.
Our bug lists grew over reasonable size.

In particular we could drop the milestone altogether if bug 
1) already had 2.4.0 milestone in the past and
2) does not have patch attached and
3) no one will respond to gently ping for finishing in 2.5 (or at least
   explicitly plans to address it in 2.6) and 
(4? not sure about this one) there was no reasonable debate/progress
   in comments during 2.5 dev cycle

And similar policy for 2.4.x milestones. If something already had 2.3.x
milestone and no progress since then, lets drop the milestone.

I spend quite some time sorting out bugs for 2.4.0 and its' waisting time
for every new relase if no one touched the bug for a half a decade or more.
Moreover it makes it harder to focus on bugs which are more recent/relevant.

Opinions?

Pavel
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jürgen Spitzmüller]

Am Montag, dem 28.04.2025 um 12:48 -0400 schrieb Richard Kimberly Heck:
> If you think things are reasonably settled, I will do some kind of
> 'nightly' package of 2.5.0, and see if we can get a bit of testing
> for it. Then we can think about more concrete plans.

We can start with that as soon as you are ready. As far as I am
concerned, things are settled (after today's minor final polishment).

Thibaut intends to look into docbook implementation (which might need
some time to get right), but I don't think we need to have that ready
for the first round of testing.

The more people trying it (with backup documents), the better.

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Richard Kimberly Heck]

On 4/27/25 11:18 PM, Jürgen Spitzmüller wrote:

Am Montag, dem 28.04.2025 um 00:29 +0200 schrieb Jean-Marc Lasgouttes:

Le 27/04/2025 à 21:12, Richard Kimberly Heck a écrit :
If what I have in mind works well, then we can always backport like I 
did for the performance work.

In this case, I'd also think we could move on. We have more than enough
things to provide.


Agreed.


I like the idea of being faster than we were for 2.4.0.

Definitely.

 From my POV, we are done (except of course for testing and ironing out
bugs this certainly introduced).


If you think things are reasonably settled, I will do some kind of 
'nightly' package of 2.5.0, and see if we can get a bit of testing for 
it. Then we can think about more concrete plans.


I'll also plan on a 2.4.4 release in near future.

Riki

-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jürgen Spitzmüller]

Am Montag, dem 28.04.2025 um 00:29 +0200 schrieb Jean-Marc Lasgouttes:
> Le 27/04/2025 à 21:12, Richard Kimberly Heck a écrit :
> > With this work, which is fantastic, it really seems to me like we
> > are ready to start thinking about potentially considering maybe
> > moving toward 2.5.0. Not to be too definitive about it!
> 
> I agree that this is fantastic. Congrats to Jürgen for all this work.

Thank you. I am also glad myself to see how it now all pays off.

> 
> From this perspective, I would say that releasing 1.5.0 soon 

;-)

> is a good idea. If what I have in mind works well, then we can always
> backport like I did for the performance work.

In this case, I'd also think we could move on. We have more than enough
things to provide.

> I like the idea of being faster than we were for 2.4.0.

Definitely.

From my POV, we are done (except of course for testing and ironing out
bugs this certainly introduced).

-- 
Jürgen
-- 
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel

Re: LyX 2.5.0

[Jean-Marc Lasgouttes]

Le 27/04/2025 à 21:12, Richard Kimberly Heck a écrit :
With this work, which is fantastic, it really seems to me like we are 
ready to start thinking about potentially considering maybe moving 
toward 2.5.0. Not to be too definitive about it!


I agree that this is fantastic. Congrats to Jürgen for all this work.

JMarc, I'm curious what you think about this, and what plans you might 
have for improvements, and when you think that might stabilize.


My plans, as often, are for July. Up to then, I will probably be 
preparing for the big changes by adapting some function to the fact that 
an inset does not cover a rectangular box anymore. It is hard to see 
what are all the places that will be hit, unfortunately.


As for stability, frankly I do not know. I know what I want to 
implement, but I do not know what assumptions I will break. I would be 
glad if I could in advance use Coord::insets cache only for mathed, but 
I am not sure that it is doable.


From this perspective, I would say that releasing 1.5.0 soon is a good 
idea. If what I have in mind works well, then we can always backport 
like I did for the performance work.


I like the idea of being faster than we were for 2.4.0.

JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
https://lists.lyx.org/mailman/listinfo/lyx-devel