On 11/04/2017 2:45 p.m., Scott Kostyshak wrote:
A second reason to keep the alpha is that very few Windows and Mac users
can compile a development version. An alpha is nice in situations where
we cannot reproduce a bug. We can ask users if they can still reproduce
e.g. a serious crash that
On Mon, Nov 21, 2016 at 10:00:19PM -0500, Scott Kostyshak wrote:
> On Mon, Nov 21, 2016 at 05:13:55PM +, Jean-Pierre Chrétien wrote:
>
> > 88% tests passed, 669 tests failed out of 5553
> > Does this sound correct? I have TL2016 with all language collections and
> > fonts installed.
>
>
On Thu, Apr 06, 2017 at 09:41:57AM +0100, José Abílio Matos wrote:
> On Thursday, 6 April 2017 02.56.51 WEST Scott Kostyshak wrote:
> > I see it's used in other places in lyx2lyx (grep for '== True'), so
> > perhaps this is convention in Python?
>
> Nope.
>
> The convention is the former:
>
>
On Mon, Apr 10, 2017 at 09:46:45AM +0200, Jean-Marc Lasgouttes wrote:
> It was proably discussed last time, but I do not remember: what is the
> rationale for having an alpha before feature freeze? Shouldn't it be
> the opposite?
The requirements and expectations of an alpha are low. I think it
On Mon, Apr 10, 2017 at 09:41:56AM +0200, Jean-Marc Lasgouttes wrote:
> I would expect LTS to be a safe, conservative choice, but I may be
> wrong.
I think you are right.
Scott
signature.asc
Description: PGP signature
On Mon, Apr 10, 2017 at 11:47:40PM +0200, Uwe Stöhr wrote:
> El 10.04.2017 a las 09:41, Jean-Marc Lasgouttes escribió:
>
> > I have not followed the recent Qt development, but I find it depressing
> > that we have to use the latst and greatest because anything older has
> > significant issues. I
On Mon, Apr 10, 2017 at 11:20:51PM +0200, Uwe Stöhr wrote:
> El 10.04.2017 a las 10:43, Jean-Marc Lasgouttes escribió:
>
> > > I have not heard about this rule.
> >
> > This is why there is the word "propose" in the sentence above.
>
> OK. Nevertheless I support this rule. Btw. where can I find
On Tue, Apr 11, 2017 at 02:58:08AM +0200, Uwe Stöhr wrote:
> El 10.04.2017 a las 05:35, Scott Kostyshak escribió:
>
> > This commit broke the test
> >
> >check_Length
> >
> > I'm guessing that there is no regression and that the test just needs to
> > be updated. Uwe, can you please take a
El 10.04.2017 a las 05:35, Scott Kostyshak escribió:
This commit broke the test
check_Length
I'm guessing that there is no regression and that the test just needs to
be updated. Uwe, can you please take a look?
How is this test executed? What problems do you get and where is the
test
The attached simple patch fixes
http://www.lyx.org/trac/ticket/10618
The bug is that on opening /saving a file only the float type is written
to the label. But there exists a detailed label writing function that is
just not called (only on buffer update).
OK to go in or have I overseen
El 10.04.2017 a las 11:05, Jean-Marc Lasgouttes escribió:
These environment always put the result its own page for technical
reasons. All the original reporter said is "I think the 'Here if
possible' and 'Here definitely' GUI options should still remain available".
I think we have here the
El 10.04.2017 a las 09:41, Jean-Marc Lasgouttes escribió:
I have not followed the recent Qt development, but I find it depressing
that we have to use the latst and greatest because anything older has
significant issues. I would expect LTS to be a safe, conservative
choice, but I may be wrong.
El 10.04.2017 a las 05:33, Scott Kostyshak escribió:
5 months ago the user "backbone" presented a patch that fixes the bug for me
(see attached).
I don't understand what is wrong wit this patch and all further patches do
not work.
See comment 15. backbone replied to this question.
I don't
El 10.04.2017 a las 23:20, Uwe Stöhr escribió:
You mean that formulas are now also indented within LyX. I'll have a look but.
I had a look but failed as often: I cannot find a start point where
displayed formulas are painted. I often have to stop at this point. LyX
needs like a sitemap
El 10.04.2017 a las 10:43, Jean-Marc Lasgouttes escribió:
I have not heard about this rule.
This is why there is the word "propose" in the sentence above.
OK. Nevertheless I support this rule. Btw. where can I find accepted rules?
I could not find a better solution that I proposed. When
On Mon, Apr 10, 2017 at 03:07:34PM +0200, Jean-Marc Lasgouttes wrote:
> Le 10/04/2017 à 12:27, José Abílio Matos a écrit :
> > Since this fixes a bug I think that it should be committed.
> > For the final version I intend to uniform all the changes that have been
> > done
> > to support python 2
Am 10.04.2017 um 05:40 schrieb Scott Kostyshak :
>
> Dear all,
>
> I think there is agreement that master is pretty stable. Besides just a
> feeling, I think that this can be confirmed by looking at the trac
> tickets with "2.3.0" milestone and tickets with the "regression"
>
Le 10/04/2017 à 21:05, racoon a écrit :
Hi!
Can someone check
http://www.lyx.org/trac/ticket/10455
and put it into master for testing?
Best,
Daniel
Hello Daniel and the list,
you also have
http://www.lyx.org/trac/ticket/10483
http://www.lyx.org/trac/ticket/10379
Hi!
Can someone check
http://www.lyx.org/trac/ticket/10455
and put it into master for testing?
Best,
Daniel
On 10.04.2017 11:14, Jean-Marc Lasgouttes wrote:
Le 08/04/2017 à 09:13, racoon a écrit :
In "Advices for using the LyX bug tracker"
http://www.lyx.org/trac/wiki/reportingBugs
It is stated: "When reporting a bug, indicate your LyX version and
*platform* (the latter via TicketKeywords)."
I
Le 10/04/2017 à 12:27, José Abílio Matos a écrit :
Since this fixes a bug I think that it should be committed.
For the final version I intend to uniform all the changes that have been done
to support python 2 and 3 to make the code more maintainable.
OK, I did that.
JMarc
On Monday, 10 April 2017 11.02.21 WEST Jean-Marc Lasgouttes wrote:
> As I wrote, it fixes my problem. Do you want me to apply it, or are
> there reasons to hold it?
>
> JMarc
Since this fixes a bug I think that it should be committed.
For the final version I intend to uniform all the changes
On Monday, 10 April 2017 10.58.51 WEST Jean-Marc Lasgouttes wrote:
> No, because doing everything by opposition to others is like doing doing
> it like them: it is following their whim
:-)
> Seriously, I am not sure about the alpha release. It is serious work,
> and I am not sure what we will
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/148/
Le 05/04/2017 à 22:08, Enrico Forestieri a écrit :
Most probably you have some non-ascii characters in a \DeclareLaTeXClass
line in some of your layout files. Now those files are explicitly read as
utf-8 encoded. If this is so, the attached patch should help.
Another consequence of the recent
Le 10/04/2017 à 11:49, José Abílio Matos a écrit :
FWIW, IMHO it all comes to:
What is the event that we think is relevant to jump to the 3.x series?
If none then the first number in the 2.x.y moniker is irrelevant and it should
be dropped.
I agree with what you write, but it does not seem
Le 10/04/2017 à 11:27, José Abílio Matos a écrit :
Again following your reasoning since everyone is abandoning the alpha release
we should keep it. ;-)
No, because doing everything by opposition to others is like doing doing
it like them: it is following their whim :)
Seriously, I am not
On Monday, 10 April 2017 08.50.32 WEST Jean-Marc Lasgouttes wrote:
> Version numbers are just version numbers, I do not think that they make
> as much of a difference than getting versions out fast. In the case of
> firefox and gcc, the important part of the new release scheme was speed.
> The
On Monday, 10 April 2017 08.46.45 WEST Jean-Marc Lasgouttes wrote:
> It was proably discussed last time, but I do not remember: what is the
> rationale for having an alpha before feature freeze? Shouldn't it be the
> opposite?
I think that this is the usual procedure. Take Fedora as an example,
Le 08/04/2017 à 09:13, racoon a écrit :
In "Advices for using the LyX bug tracker"
http://www.lyx.org/trac/wiki/reportingBugs
It is stated: "When reporting a bug, indicate your LyX version and
*platform* (the latter via TicketKeywords)."
I changed the page. Is it better now?
JMarc
Le 10/04/2017 à 02:21, Uwe Stöhr a écrit :
As reported in
http://www.lyx.org/trac/ticket/10270
LyX forbids incorrectly the float placement options.
The attached patch fixed this.
These environment always put the result its own page for technical
reasons. All the original reporter said is "I
Le 08/04/2017 à 02:13, Uwe Stöhr a écrit :
But OK, I moved it now as you requested.
Thanks Uwe.
JMarc
Le 08/04/2017 à 04:58, Uwe Stöhr a écrit :
El 07.04.2017 a las 10:51, Jean-Marc Lasgouttes escribió:
Maybe more like:...
Thanks.
The patch is now in including this hint and the new BLS unit is
available for all lengths.
Thanks.
JMarc
Le 10/04/2017 à 01:00, Uwe Stöhr a écrit :
El 06.04.2017 a las 11:10, Jean-Marc Lasgouttes escribió:
That is not how it works. Actually, I propose to add a rule to our
coding rules that says that no code which does not take in account
zoom and DPI when drawing should be accepted (with the
Am Montag, 10. April 2017 um 09:43:15, schrieb Jean-Marc Lasgouttes
> Le 10/04/2017 à 09:23, Kornel Benko a écrit :
> > The first number is value in pixels(250) for 2342baselineskip%,
> > the second is value in Big Points for 2342baselineskip%
> >
> > I propose more readable
Le 10/04/2017 à 05:36, Scott Kostyshak a écrit :
First the obvious conclusion, those number are completely arbitrary. Each of
those versions has been a major version on its own. And as usual I propose to
go the way of gcc (not necessarily dropping the first .0 ;-) ). And use simply
a major
Le 10/04/2017 à 05:40, Scott Kostyshak a écrit :
I think there is agreement that master is pretty stable. Besides just a
feeling, I think that this can be confirmed by looking at the trac
tickets with "2.3.0" milestone and tickets with the "regression"
keyword.
Yes, I think it is time to think
Le 10/04/2017 à 09:23, Kornel Benko a écrit :
The first number is value in pixels(250) for 2342baselineskip%,
the second is value in Big Points for 2342baselineskip%
I propose more readable output for check_Length.cpp.
For instance the attached.
Yes, please put it in and fix the test.
Le 10/04/2017 à 06:39, Scott Kostyshak a écrit :
Dear all,
I would like to propose that we release our LyX 2.3.0 alpha binaries for
Mac and Windows with Qt 5.9.0beta1 and that we release our final LyX
2.3.0 binaries with the final release of Qt 5.9.0.
Hello,
A question: do we have compelling
Am Samstag, 8. April 2017 um 22:49:48, schrieb Jean-Marc Lasgouttes
> Le 08/04/2017 à 16:24, Kornel Benko a écrit :
> >> I think this is real breakage and not due to me testing things. Perhaps
> >> related to Uwe's recent changes?
> >
> > Fails under cmake too (e.g. #ctest -R
40 matches
Mail list logo