Jean-Marc Lasgouttes wrote:
> Le 10/03/2017 ?? 16:32, Jean-Marc Lasgouttes a écrit :
>> commit 9a013637bbe7c35dc90cb28ff874da99133a1f8b
>> Author: Jean-Marc Lasgouttes
>> Date: Fri Mar 10 16:29:09 2017 +0100
>>
>> Experiment: limit size of strings read from lib/symbols
>>
>> Coverity com
On Fri, Mar 10, 2017 at 09:22:09AM +, José Abílio Matos wrote:
> On Friday, 10 March 2017 07.31.43 WET Scott Kostyshak wrote:
> > agree that * is an established wildcard, but doesn't it mean "all" or
> > "everything"? For example, inset-forall uses '*' for "all insets".
> > Wouldn't the analog
Guillaume Munch wrote:
> commit 24f68aff8d2ba9139017ca3927eda1f1aaf039af
> Author: Guillaume Munch
> Date: Sat Mar 11 00:11:02 2017 +0100
>
> Nonsense for whoever insists on using gcc4.6 & qt4.8 in 2017
Does it mean it is not supposed to work with those two or it should?
I just quickly ch
Am Freitag, 10. März 2017 um 20:02:38, schrieb Jean-Marc Lasgouttes
> Le 08/03/2017 à 10:45, Helge Hafting a écrit :
> >> FWIW, I can reproduce it. I'll have a look when I can.
> > I have debugged some more, and the problem is with explicit linebreaks
> > (ctrl+enter)
>
> Thanks Helge for the ni
On Wednesday, 8 March 2017 01.33.03 WET Pavel Sanda wrote:
> My take on this is that release manager responsibility is to set and publish
> deadlines and push people who are responsible for their area of expertise
> to fix or stabilize that in reasonable time. So it's more of understanding
> whom t
On Wednesday, 8 March 2017 00.17.33 WET Scott Kostyshak wrote:
> Makes sense. I guess in the end this is the decision of the branch
> maintainer.
>
> Scott
Agreed. :-)
--
José Abílio
Le 08/03/2017 à 10:45, Helge Hafting a écrit :
FWIW, I can reproduce it. I'll have a look when I can.
I have debugged some more, and the problem is with explicit linebreaks
(ctrl+enter)
Thanks Helge for the nice analysis. This problem is not in master and is
new to 2.2.3dev.
Here is a propo
Am Freitag, 10. März 2017 um 19:26:12, schrieb Jean-Pierre Chrétien
> Le 10/03/2017 à 19:19, Jean-Pierre Chrétien a écrit :
>
> >
> > Just made a test to be sure, I pushed
> > * a quite small commit about AGUTeX.lyx
> > * a fresh update of fr.po and fr.gmo (however with only 3 changes this
Le 10/03/2017 à 19:19, Jean-Pierre Chrétien a écrit :
Just made a test to be sure, I pushed
* a quite small commit about AGUTeX.lyx
* a fresh update of fr.po and fr.gmo (however with only 3 changes this time,
instead of ~ a hundred the last time).
We'll see what mails lyx-devel will get fr
Le 10/03/2017 à 10:02, Kornel Benko a écrit :
Am Donnerstag, 9. März 2017 um 18:18:38, schrieb Pavel Sanda
IIRC we have some maximal size of mails which can get through our conferences.
Esp. with po/gmo changes those limits will be hit.
Pavel
Maybe, but consider that gmo-changes are not se
Le 10/03/2017 à 16:32, Jean-Marc Lasgouttes a écrit :
commit 9a013637bbe7c35dc90cb28ff874da99133a1f8b
Author: Jean-Marc Lasgouttes
Date: Fri Mar 10 16:29:09 2017 +0100
Experiment: limit size of strings read from lib/symbols
Coverity complains that we might read strings that are arbit
Le 10/03/2017 à 16:19, Kornel Benko a écrit :
Am Freitag, 10. März 2017 um 16:05:01, schrieb Jean-Marc Lasgouttes
Le 10/03/2017 à 16:01, Jürgen Spitzmüller a écrit :
That is what I figured out. I seems to me that it could be done in
an
easier way, although I do not know which one yet :)
Me
Am Freitag, den 10.03.2017, 16:05 +0100 schrieb Jean-Marc Lasgouttes:
> Something else is weird: if the filter is "abc", then it matches
> abc
> xxaxbyycyy
> but bot
> xxcxaxxvyyy
>
> So the characters can be separate, but should be ordered correctly.
> What
> is the use case for
Am Freitag, 10. März 2017 um 16:05:01, schrieb Jean-Marc Lasgouttes
> Le 10/03/2017 à 16:01, Jürgen Spitzmüller a écrit :
> >> That is what I figured out. I seems to me that it could be done in
> >> an
> >> easier way, although I do not know which one yet :)
> >
> > Me neither.
>
> Something els
Le 10/03/2017 à 16:01, Jürgen Spitzmüller a écrit :
That is what I figured out. I seems to me that it could be done in
an
easier way, although I do not know which one yet :)
Me neither.
Something else is weird: if the filter is "abc", then it matches
abc
xxaxbyycyy
but bot
xxcxa
Am Freitag, den 10.03.2017, 15:17 +0100 schrieb Jean-Marc Lasgouttes:
> Le 10/03/2017 à 14:59, Jürgen Spitzmüller a écrit :
> > > A way to fix the coverity issue would be to assert on p>=0, but I
> > > have
> > > to ask: how do we know that p!=-1?
> >
> > AFAICS it can actually be -1, if the filte
Le 10/03/2017 à 14:59, Jürgen Spitzmüller a écrit :
I have no clear idea either (since you asked me). The code was written
by Abdel, I just copied it over from LayoutBox. But I try:
OK, I see now.
AFAICS it can actually be -1, if the filter string is not found. So we
probably should not asser
Le 10/03/2017 à 14:59, Jürgen Spitzmüller a écrit :
A way to fix the coverity issue would be to assert on p>=0, but I
have
to ask: how do we know that p!=-1?
AFAICS it can actually be -1, if the filter string is not found. So we
probably should not assert here, but leave the loop.
So
- LASSER
I have no clear idea either (since you asked me). The code was written
by Abdel, I just copied it over from LayoutBox. But I try:
Am Freitag, den 10.03.2017, 11:34 +0100 schrieb Jean-Marc Lasgouttes:
> We have a coverity issue about the folowing code:
>
> QString CCItemDelegate::underlineFilter(Q
Am Freitag, 10. März 2017 um 12:37:36, schrieb Kornel Benko
> Am Freitag, 10. März 2017 um 12:15:21, schrieb Jean-Pierre Chrétien
>
> > Le 10/03/2017 à 08:31, Scott Kostyshak a écrit :
> >
> > >
> > > I'll change it to "default" if no one beats me to it and no one
> > > disagrees in the next co
Am Freitag, 10. März 2017 um 12:15:21, schrieb Jean-Pierre Chrétien
> Le 10/03/2017 à 08:31, Scott Kostyshak a écrit :
>
> >
> > I'll change it to "default" if no one beats me to it and no one
> > disagrees in the next couple of days.
>
> Will this new option allow to run easily ctest on defaul
Le 10/03/2017 à 08:31, Scott Kostyshak a écrit :
I'll change it to "default" if no one beats me to it and no one
disagrees in the next couple of days.
Will this new option allow to run easily ctest on default output exports ?
--
Jean-Pierre
We have a coverity issue about the folowing code:
QString CCItemDelegate::underlineFilter(QString const & s) const
{
QString const & f = cc_->filter();
if (f.isEmpty())
return s;
// step through data item and put "(x)" for every matching character
Hello,
The attached patch looks straightforward to me, but since this is a
sensitive area in terms of portability, I would like some people to take
a quick look at it.
I am not sure actually how to properly test it.
JMarc
From 99a9ae001062c83e8d8c2efd80bc6d938a35c62b Mon Sep 17 00:00:00 2001
Am Freitag, den 10.03.2017, 10:36 +0100 schrieb Jean-Marc Lasgouttes:
> Jürgen, please check that I did the right thing.
Yes, looks correct.
Thanks
Jürgen
signature.asc
Description: This is a digitally signed message part
Le 10/03/2017 à 10:35, Jean-Marc Lasgouttes a écrit :
commit e2f2915f8edcc558e7d41b6e9bf8e0a6838ba47d
Author: Jean-Marc Lasgouttes
Date: Fri Mar 10 10:32:38 2017 +0100
Be careful about unparsable bibtex years
Handle gracefully the case where the regex that parses a year fails.
T
On Friday, 10 March 2017 07.31.43 WET Scott Kostyshak wrote:
> agree that * is an established wildcard, but doesn't it mean "all" or
> "everything"? For example, inset-forall uses '*' for "all insets".
> Wouldn't the analogy here be for it to mean "all formats", which is not
> what we want?
I had
Am Donnerstag, 9. März 2017 um 18:18:38, schrieb Pavel Sanda
> Richard Heck wrote:
> > >> No. It may be that you are not whitelisted for posting to lyx-cvs.
> > >
> > > There have been posts from j...@lyx.org last month on lyx-cvs.
> >
> > Mystery, then.
>
> IIRC we have some maximal size of mai
28 matches
Mail list logo
