On Sunday, 9 December 2018 20.17.15 WET Richard Kimberly Heck wrote:
> Here:
>
> http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/
>
> Please prepare binaries.
>
> Note that 2.3.x remains closed until the release, hopefully later this week.
>
> Riki
I have updated in copr for Fedora 28, 29 and raw
The kpsewhich bug which caused slowness on windows when a document used
a bibtex database in the initial 2.3.1 installer, has reappeared in
2.3.2 on my windows 7 system. See
https://marc.info/?l=lyx-devel&m=153580258026277&w=2. A second windows
2.3.1 installer was produced in which the problem
On 12/11/18 5:56 PM, Andrew Parsloe wrote:
> The kpsewhich bug which caused slowness on windows when a document
> used a bibtex database in the initial 2.3.1 installer, has reappeared
> in 2.3.2 on my windows 7 system. See
> https://marc.info/?l=lyx-devel&m=153580258026277&w=2. A second windows
> 2
On 12/11/18 6:25 PM, Richard Kimberly Heck wrote:
> On 12/11/18 5:56 PM, Andrew Parsloe wrote:
>> The kpsewhich bug which caused slowness on windows when a document
>> used a bibtex database in the initial 2.3.1 installer, has reappeared
>> in 2.3.2 on my windows 7 system. See
>> https://marc.info/
On 12/12/2018 12:34 PM, Richard Kimberly Heck wrote:
On 12/11/18 6:25 PM, Richard Kimberly Heck wrote:
On 12/11/18 5:56 PM, Andrew Parsloe wrote:
The kpsewhich bug which caused slowness on windows when a document
used a bibtex database in the initial 2.3.1 installer, has reappeared
in 2.3.2 o
On 12/11/18 11:42 PM, Andrew Parsloe wrote:
>
> On 12/12/2018 12:34 PM, Richard Kimberly Heck wrote:
>> On 12/11/18 6:25 PM, Richard Kimberly Heck wrote:
>>> On 12/11/18 5:56 PM, Andrew Parsloe wrote:
The kpsewhich bug which caused slowness on windows when a document
used a bibtex databas
On 12/12/18 1:41 AM, Richard Kimberly Heck wrote:
> Another issue like the one we had with the 2.3.1 release, related to the
> fix for #9158. The commit message explains the issue. The fix seems to
> me to make sense anyway.
>
> The second patch also seems to me to make sense, and it ought to preve
Another issue like the one we had with the 2.3.1 release, related to the
fix for #9158. The commit message explains the issue. The fix seems to
me to make sense anyway.
The second patch also seems to me to make sense, and it ought to prevent
these kinds of issues arising in future. But maybe it's