The bug tracker sent you this email. Replying to it, though, only emails
the development list. You'd do best to reply on the original bug, which
you can do by clicking on the link at the bottom of the email.
Riki
On 07/22/2018 07:59 PM, Virgil L wrote:
> Thank you! It's great to hear that the
On 07/22/2018 05:35 PM, Jean-Marc Lasgouttes wrote:
> Le 22/07/2018 à 23:23, Jean-Marc Lasgouttes a écrit :
>> commit 20976e81fb25899ee8d3ec5ed941fda6b453f59f
>> Author: Jean-Marc Lasgouttes
>> Date: Sun Jul 22 22:13:44 2018 +0200
>>
>> Improve DEPM
>> Now any sequence of spaces
Thank you! It's great to hear that the bug may already have been eliminated.
However, if I read it correctly, the description of the other bug does NOT
emphasize or mention \setminted which in my case is the real culprit, because
it yields errors that BREAK the execution of the LaTeX code.
The
Le 22/07/2018 à 23:23, Jean-Marc Lasgouttes a écrit :
commit 20976e81fb25899ee8d3ec5ed941fda6b453f59f
Author: Jean-Marc Lasgouttes
Date: Sun Jul 22 22:13:44 2018 +0200
Improve DEPM
Now any sequence of spaces around old cursor will be removed, even at
start or end of
Am Sonntag, 22. Juli 2018 20:05:10 CEST schrieb Jürgen Spitzmüller
:
> Am Sonntag, den 22.07.2018, 19:13 +0200 schrieb Jürgen Spitzmüller:
> > > Disallow any inset inside ERT
> >
> > Yes, I was sure this is the issue.
>
> fixed.
>
> Jürgen
>
Confirmed, ja/Math.lyx tests succeeded now.
Le 22/07/2018 à 20:36, Jean-Marc Lasgouttes a écrit :
Le 22/07/2018 à 19:33, Thomas DiPrete a écrit :
I found this in the console from 7/17, which is the date I reported
the bug. I hope it is helpful. I've attached to this message the
several versions.
I am not sure that this contains more
Le 22/07/2018 à 19:33, Thomas DiPrete a écrit :
I found this in the console from 7/17, which is the date I reported the
bug. I hope it is helpful. I've attached to this message the several
versions.
I am not sure that this contains more information about what LyX is
doing at this time. I am
Le 22/07/2018 à 18:59, Daniel a écrit :
But I am a bit lost. You state the widths above as em fractions but say
that the values are integers. Do you mean that the list of widths widths
above are as defined in the booktab package but you are using integer
values to set the line width in LyX?
Am Sonntag, den 22.07.2018, 19:13 +0200 schrieb Jürgen Spitzmüller:
> > Disallow any inset inside ERT
>
> Yes, I was sure this is the issue.
fixed.
Jürgen
signature.asc
Description: This is a digitally signed message part
Am Sonntag, den 22.07.2018, 14:06 +0200 schrieb Kornel Benko:
> bisect led to
> d41c3f27d9192bd3b0de89a04ccf2fcf16bb4c91 is the first bad commit
> commit d41c3f27d9192bd3b0de89a04ccf2fcf16bb4c91
> Author: Juergen Spitzmueller
> Date: Tue Jul 10 07:11:59 2018 +0200
>
> Disallow any inset
On 21/07/2018 21:13, Jean-Marc Lasgouttes wrote:
Le 21/07/2018 à 19:50, Daniel a écrit :
The widths are:
heavy=0.008em
thin=0.05em
cmid=0.03em
If I do use these values, I can only see a difference between heavy
and thin beyond 180% zoom (at 100dpi) and the 3 width are different
only over
On Thu, Jul 19, 2018 at 4:28 PM, Jean-Marc Lasgouttes
wrote:
>
> Please try it out. If people like it, it can be backported.
>
> JMarc
I tried this and though I didn't experiment extensively (or try to break
it), I really like it on its first impression. Good addition.
Thanks,
Joel
Am Sonntag, 22. Juli 2018 15:01:06 CEST schrieb Jean-Marc Lasgouttes
:
> Le 22/07/2018 à 14:57, Jean-Marc Lasgouttes a écrit :
> > Le 22/07/2018 à 14:06, Kornel Benko a écrit :
> >> bisect led to
> >> d41c3f27d9192bd3b0de89a04ccf2fcf16bb4c91 is the first bad commit
> >> commit
Le 22/07/2018 à 14:57, Jean-Marc Lasgouttes a écrit :
Le 22/07/2018 à 14:06, Kornel Benko a écrit :
bisect led to
d41c3f27d9192bd3b0de89a04ccf2fcf16bb4c91 is the first bad commit
commit d41c3f27d9192bd3b0de89a04ccf2fcf16bb4c91
Author: Juergen Spitzmueller
Date: Tue Jul 10 07:11:59 2018 +0200
Le 22/07/2018 à 14:06, Kornel Benko a écrit :
bisect led to
d41c3f27d9192bd3b0de89a04ccf2fcf16bb4c91 is the first bad commit
commit d41c3f27d9192bd3b0de89a04ccf2fcf16bb4c91
Author: Juergen Spitzmueller
Date: Tue Jul 10 07:11:59 2018 +0200
Disallow any inset inside ERT
Not a lyx2lyx
Am Sonntag, 22. Juli 2018 13:35:23 CEST schrieb Jean-Marc Lasgouttes
:
> Le 22/07/2018 à 11:08, Kornel Benko a écrit :
> > Am Sonntag, 22. Juli 2018 10:32:59 CEST schrieb Jürgen Spitzmüller
> > :
> >> Am Sonntag, den 22.07.2018, 09:59 +0200 schrieb Kornel Benko:
> >>> It is \ only. Search for
Le 22/07/2018 à 11:08, Kornel Benko a écrit :
Am Sonntag, 22. Juli 2018 10:32:59 CEST schrieb Jürgen Spitzmüller
:
Am Sonntag, den 22.07.2018, 09:59 +0200 schrieb Kornel Benko:
It is \ only. Search for instance for ' sungsmittel', then open the
ERT to the left.
Not here. See screenshot. Are
Am Sonntag, 22. Juli 2018 10:32:59 CEST schrieb Jürgen Spitzmüller
:
> Am Sonntag, den 22.07.2018, 09:59 +0200 schrieb Kornel Benko:
> > It is \ only. Search for instance for ' sungsmittel', then open the
> > ERT to the left.
>
> Not here. See screenshot. Are you sure yours is a clean checkout?
Am Sonntag, den 22.07.2018, 09:34 +0200 schrieb Jürgen Spitzmüller:
> Am Sonntag, den 22.07.2018, 07:44 +0200 schrieb Kornel Benko:
> > IMHO, the master has some time before release. Pleading for the
> > change.
>
> We certainly need to do that change, but still there will be this
> backwards
Am Sonntag, 22. Juli 2018 09:37:45 CEST schrieb Jürgen Spitzmüller
:
> Am Sonntag, den 22.07.2018, 07:38 +0200 schrieb Kornel Benko:
> > I am using the latest master too.
> > Changing the language of both German paragraphs in multicol env to
> > Japanese and substituting
> > \U\a\ss etc to Üäß
>
Am Sonntag, den 22.07.2018, 07:38 +0200 schrieb Kornel Benko:
> I am using the latest master too.
> Changing the language of both German paragraphs in multicol env to
> Japanese and substituting
> \U\a\ss etc to Üäß
> then the compilation succeeds.
Strange. We did the opposite change just
Am Sonntag, den 22.07.2018, 07:44 +0200 schrieb Kornel Benko:
> IMHO, the master has some time before release. Pleading for the
> change.
We certainly need to do that change, but still there will be this
backwards compatibility problem we cannot sort out (except if we
introduce our own
22 matches
Mail list logo