On 05/12/2018 12:09 AM, Richard Kimberly Heck wrote:
> On 05/11/2018 11:44 PM, Joel Kulesza wrote:
>> LyX Developers,
>>
>> As I'm writing my dissertation, I've been using LyX 2.2.3 but today
>> decided to try migrating it to 2.3.0. Upon doing so, I encountered
>> what appears to be a regression (
On Fri, May 11, 2018 at 10:09 PM, Richard Kimberly Heck
wrote:
> On 05/11/2018 11:44 PM, Joel Kulesza wrote:
>
> LyX Developers,
>
> As I'm writing my dissertation, I've been using LyX 2.2.3 but today
> decided to try migrating it to 2.3.0. Upon doing so, I encountered what
> appears to be a reg
On 05/11/2018 11:44 PM, Joel Kulesza wrote:
> LyX Developers,
>
> As I'm writing my dissertation, I've been using LyX 2.2.3 but today
> decided to try migrating it to 2.3.0. Upon doing so, I encountered
> what appears to be a regression (or else I've been doing something
> invalid all along that 2
On 05/11/2018 10:20 PM, Uwe Stöhr wrote:
>
> _Should I remove the Win installer code from LyX's git?_
No, I may wish to make use of it. I am in the process of figuring out
how to build the Windows installer myself, as you suggested. The code
belongs to LyX, not to you.
> If yes, I'll release inst
Am 07.04.2018 um 00:48 schrieb Richard Kimberly Heck:
installer that is as automatic as it can be. Many of the rest of us have
real doubts about the wisdom of this,
That is what annoys me. You doubt that I am wise enough to set up LyX
for Windows users.
First of all, I specifically said that
Am 07.04.2018 um 00:40 schrieb Richard Kimberly Heck:
If MiKTeX can be broken some other
way, that's a bug in MiKTeX and not one we should be trying to fix via
the LyX installer.
That is the fundamental difference between my and your approach. I see
the user perspective. And for the user it i
On 05/10/2018 02:37 PM, Richard Kimberly Heck wrote:
> On 05/10/2018 11:41 AM, Kornel Benko wrote:
>> Am Mittwoch, 9. Mai 2018 11:59:01 CEST schrieb Richard Kimberly Heck
>> :
>>> On 05/09/2018 11:18 AM, Pavel Sanda wrote:
Jürgen Spitzmüller wrote:
> 2018-05-06 19:50 GMT+02:00 Richard Kim
On Thursday, 10 May 2018 12.30.25 WEST Jean-Marc Lasgouttes
wrote:
> What is strange is that __repalcement_assert seems to be related to
> __gnu_parallel. Could this be a compiler/library bug?
>
> JMarc
Could it be that search and replace code uses another thread? That
would explain the __gnu_p
On Thursday, 10 May 2018 18.32.00 WEST Scott Kostyshak wrote:
> Should I still do the above? I'm not sure if it would still be useful
> after reading the messages that came after this.
>
> Thanks for helping debug,
>
> Scott
There is no need to.
The problem seems to be in the calling code. This
On 05/11/2018 09:11 AM, Juergen Spitzmueller wrote:
> commit de67b68b1dc140321e5d0e2e6b4507c972703744
> Author: Juergen Spitzmueller
> Date: Fri May 11 15:11:06 2018 +0200
>
> Fix InsetBox::contentAlignment()
>
> Some cases where alignment is possible were missing.
>
> Cand
10 matches
Mail list logo
