Hi,
This is a CI job I'm working on that's intended to run automated tests:
https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/
Currently there's about 2300 failing tests (out of 6000), so I'm guessing
more stuff needs to be installed.
Detailed results via this link:
https://ci.inria.fr/
On Fri, Feb 24, 2017 at 06:45:28PM +0100, Jean-Marc Lasgouttes wrote:
> Who has Work In Progress that should go to 2.3? How long do we need?
I don't have anything big I'm working on for 2.3.
Scott
signature.asc
Description: PGP signature
On Sun, Feb 26, 2017 at 07:37:45PM +0100, Günter Milde wrote:
> commit d319976566784c1e2fa3ad9b4fde5ef9bbb3da18
> Author: Günter Milde
> Date: Sun Feb 26 19:33:00 2017 +0100
>
> ctests: sort inverted unreliable tests.
>
> We don't invert unreliable tests for the same reason they ar
On 2017-02-26, Jürgen Spitzmüller wrote:
> Am Sonntag, den 26.02.2017, 11:49 + schrieb Guenter Milde:
>> We can either
>> a) Report this as a bug (as even the default fonts will lead to
>> "missing
>> glyph" warnings).
>>
>> b) Overwrite the TU-specific definition with the generic one:
>
On 2017-02-26, Jürgen Spitzmüller wrote:
> Am Sonntag, den 26.02.2017, 13:58 + schrieb Guenter Milde:
>> Mind, that the latexSpecialT1 is named wrong: it actually cares for
>> the special character macros present for all standard LaTeX font
>> encodings (T1, T2A, T2B, ... , TU).
> No it doesn
On 2017-02-26, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Am Sonntag, den 26.02.2017, 15:48 + schrieb Guenter Milde:
>> The patch e68afbe671394 "plain quote fixes" relies on two wrong
>> assumptions:
>> a) \textquote... commands are only available in T
Hi,
I just want to let people know that (hopefully) we now have a working
pipeline where:
- A CI job [1] on Mondays, builds and uses Doxygen to generate "sourcedoc"
- The LyX server, on Tuesdays, then pulls in and deploys the "sourcedoc" as
https://www.lyx.org/sourcedoc/latest/
We'll see by
On 2017-02-20, Scott Kostyshak wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> On Mon, Feb 20, 2017 at 06:40:26PM +0100, Jean-Pierre Chrétien wrote:
>> Sure, but that means a lot of test to be moved to unreliable:nonstandard.
Not moved but added. In contrast to "invert", adding
On Sun, Feb 26, 2017 at 02:33:07PM +0200, racoon wrote:
> Every time I try to open the document settings LyX crashes.
>
> LyX Version 2.3.0dev
> Built from git commit hash 3c329db0
I imagine that it works on a previous commit? If so, are you familiar
with a git bisect? It takes time, but it is a
On Sun, Feb 26, 2017 at 04:10:21PM +0100, Jürgen Spitzmüller wrote:
> Am Sonntag, den 26.02.2017, 11:49 + schrieb Guenter Milde:
> > My preference is d).
>
> Mine is a).
I'll let you both decide since I know nothing about this. It doesn't
seem to me that a and d are mutually exclusive.
Scott
Am Sonntag, den 26.02.2017, 15:48 + schrieb Guenter Milde:
> The patch e68afbe671394 "plain quote fixes" relies on two wrong
> assumptions:
>
> a) \textquote... commands are only available in T1.
>
> No. Also in T2A, T4,
Maybe. However, I get identical output for these with \textquotedbl and
The patch e68afbe671394 "plain quote fixes" relies on two wrong
assumptions:
a) \textquote... commands are only available in T1.
No. Also in T2A, T4, TU, as well as e.g. LGR.
b) \\char39 and \\char34 are double and single plain quotes.
This is depends on the font encoding.
As a result, the pa
Am Sonntag, den 26.02.2017, 13:58 + schrieb Guenter Milde:
> Mind, that the latexSpecialT1 is named wrong: it actually cares for
> the
> special character macros present for all standard LaTeX font
> encodings
> (T1, T2A, T2B, ... , TU).
No it doesn't. We explicitly check for bparams.font_enco
Am Sonntag, den 26.02.2017, 11:49 + schrieb Guenter Milde:
> We can either
>
> a) Report this as a bug (as even the default fonts will lead to
> "missing
> glyph" warnings).
>
> b) Overwrite the TU-specific definition with the generic one:
>
> \DeclareTextCommand{\textcompwordmark
Le 25/02/2017 à 21:09, Enrico Forestieri a écrit :
Then, a decision has to still be taken as regards the original problem
in this thread. I think that the patch Günther proposed on Jan. 25 is
the less controversial one.
I think you mean
https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg
On 2017-02-22, Jürgen Spitzmüller wrote:
> Am Dienstag, den 14.02.2017, 15:05 +0100 schrieb Jürgen Spitzmüller:
>> I think the reason is that LaTeX actually switched to TU font
>> encoding
> Tonight's update of latex-base brings back \textquotebdl and
> \textquotesingle to TU encodings.
> I will
On 2017-02-21, Scott Kostyshak wrote:
> On Tue, Feb 14, 2017 at 09:34:38PM +, Guenter Milde wrote:
>> >2196 - export/doc/es/UserGuide_dvi3_systemF (Failed)
>> >2203 - export/doc/es/UserGuide_pdf5_systemF (Failed)
>> These two have the known problem to produce wrong output, e.g.
>>
Every time I try to open the document settings LyX crashes.
LyX Version 2.3.0dev
Built from git commit hash 3c329db0
OS: Windows 7
On 2017-02-25, Guillaume Munch wrote:
> Le 25/02/2017 à 21:12, Guillaume Munch a écrit :
>> Le 25/02/2017 à 20:07, Guenter Milde a écrit :
>>> On a similar note: could the "backspace at begin of inset dissolves it"
>>> feature be ported to mathed, too?
>> This is a good idea, for consistency with
On 2017-02-26, Jürgen Spitzmüller wrote:
> Am Samstag, den 25.02.2017, 15:39 -0500 schrieb Scott Kostyshak:
>> After a TL update today, I now get missing glyphs errors from
>> latex/languagenesting2_pdf5_systemF
>> We could ignore the glyphs errors, but it would be nice to figure out
>> if
>> t
Am Samstag, den 25.02.2017, 15:39 -0500 schrieb Scott Kostyshak:
> After a TL update today, I now get missing glyphs errors from
>
> latex/languagenesting2_pdf5_systemF
>
> We could ignore the glyphs errors, but it would be nice to figure out
> if
> the change is expected or if this is a bug th
21 matches
Mail list logo
