https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/412/
Am 18.09.2017 um 18:17 schrieb Jürgen Spitzmüller :
>
> Am Montag, den 18.09.2017, 18:13 +0200 schrieb Juergen Spitzmueller:
>> commit 3b89cd9c283d1daadfbf1d7367aa103450a276ae
>> Author: Juergen Spitzmueller
>> Date: Mon Sep 18 18:12:21 2017 +0200
>>
>>Update internal Hunspell to latest re
On 09/18/2017 05:24 AM, Jean-Marc Lasgouttes wrote:
> Le 15/09/2017 à 17:39, Richard Heck a écrit :
>> The dark text is correct. It seems, quite generally, like the color is
>> not right when the painting begins at the top, but then it becomes right
>> when it is reset at the inset. If I scroll dow
Am Montag, 18. September 2017 um 20:02:25, schrieb Jürgen Spitzmüller
> Am Montag, den 18.09.2017, 19:45 +0200 schrieb Kornel Benko:
> > Missing:
> > 3rdparty/hunspell/1.6.2/src/hunspell/license.hunspell,
> > 3rdparty/hunspell/1.6.2/src/hunspell/license.myspell
>
> These were left out by
Am Montag, den 18.09.2017, 19:45 +0200 schrieb Kornel Benko:
> Missing:
> 3rdparty/hunspell/1.6.2/src/hunspell/license.hunspell,
> 3rdparty/hunspell/1.6.2/src/hunspell/license.myspell
These were left out by purpose (the license is in the top dir). I
missed them when adapting CMakeList.
Am Dienstag, den 19.09.2017, 01:50 +0900 schrieb K. Yokota:
> Jürgen, sorry to have missed your question.
>
> Actually, I simply hesitated to include ujclasses because, judging
> from the circulating information on web, upLaTeX seems a room for a
> change and wondered if it is good thing to add an
Am Montag, 18. September 2017 um 18:17:33, schrieb Jürgen Spitzmüller
> Am Montag, den 18.09.2017, 18:13 +0200 schrieb Juergen Spitzmueller:
> > commit 3b89cd9c283d1daadfbf1d7367aa103450a276ae
> > Author: Juergen Spitzmueller
> > Date: Mon Sep 18 18:12:21 2017 +0200
> >
> > Update interna
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/411/--
[...truncated 1151 lines...]
make[3]: Leaving directory '/build/workspace/src'
make[2]: Leaving directory '/build/workspace/src'
Making all in sourcedoc
make[2]: Ent
Jürgen, sorry to have missed your question.
Actually, I simply hesitated to include ujclasses because, judging from the
circulating information on web, upLaTeX seems a room for a change and
wondered if it is good thing to add another line in the long dropdown list
of document classes.
Supporting
Am Montag, den 18.09.2017, 18:13 +0200 schrieb Juergen Spitzmueller:
> commit 3b89cd9c283d1daadfbf1d7367aa103450a276ae
> Author: Juergen Spitzmueller
> Date: Mon Sep 18 18:12:21 2017 +0200
>
> Update internal Hunspell to latest release (1.6.2)
Please test whether this builds with cmake.
W
Am Montag, den 18.09.2017, 11:41 +0200 schrieb Jürgen Spitzmüller:
> > What is not reasonable is that we insist in disabling aspell and
> > enchant what hunspell is used. What is the point? (I know, it is
> > separate from your effort).
>
> I do not find this reasonable either.
Fixed in master an
Le 18/09/2017 à 14:46, Stephan Witt a écrit :
The patch makes no difference again, sorry. Removing the mentioned line
changes it to gray background.
And there are no letters drawn on this background?
It might be that there is a paint event that is sent before the metrics
have been computed.
Am 18.09.2017 um 15:36 schrieb Jean-Marc Lasgouttes :
>
> Le 18/09/2017 à 14:46, Stephan Witt a écrit :
>> The patch makes no difference again, sorry. Removing the mentioned line
>> changes it to gray background.
>
> I am not completely surprised. What does the "painting" debug flag tell us?
==
Le 18/09/2017 à 14:46, Stephan Witt a écrit :
The patch makes no difference again, sorry. Removing the mentioned line
changes it to gray background.
I am not completely surprised. What does the "painting" debug flag tell us?
JMarc
Le 18/09/2017 à 15:15, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Le 12/09/2017 ?? 16:44, Pavel Sanda a écrit :
I tried, but... :)
Are you still able to compile on the ubuntu 12.04 oldie?
Even if I try beta tarball to avoid our autotools version requirements
it chokes on signal.h and its
Jean-Marc Lasgouttes wrote:
> Le 12/09/2017 ?? 16:44, Pavel Sanda a écrit :
>> I tried, but... :)
>> Are you still able to compile on the ubuntu 12.04 oldie?
>> Even if I try beta tarball to avoid our autotools version requirements
>> it chokes on signal.h and its C++11 constructs. Are we completel
Am 18.09.2017 um 14:28 schrieb Jean-Marc Lasgouttes :
>
> Le 18/09/2017 à 12:48, Stephan Witt a écrit :
>> Doesn’t help, sorry.
>> Perhaps the black screen is „painted“ by the null painter?
>
> The NullPainter is really something that cannot paint. It does not rely on Qt
> at all.
>
> Can you t
Le 18/09/2017 à 12:48, Stephan Witt a écrit :
Doesn’t help, sorry.
Perhaps the black screen is „painted“ by the null painter?
The NullPainter is really something that cannot paint. It does not rely
on Qt at all.
Can you try the following? I had removed these calls but I am not sure
what th
2017-09-18 13:14 GMT+02:00 Kornel Benko :
> > CMakers, does -DLYX_EXTERNAL_HUNSPELL=OFF -DLYX_USE_ASPELL=ON
> > -DLYX_USE_ENCHANT=ON give you all three spellers as option?
>
> Yes, I see all three spellers as option.
> To be sure I don't use external HUNSPELL:
> # ldd /usr/local/bin/lyx2.4
Am Montag, 18. September 2017 um 12:14:30, schrieb Jürgen Spitzmüller
> 2017-09-18 11:53 GMT+02:00 Jean-Marc Lasgouttes :
>
> > What could make it useful is that you could decide to enforce the use of
> > the new C++ API (if we ever get it to work). If the system hunspell is not
> > good enough,
Am 18.09.2017 um 12:24 schrieb Jean-Marc Lasgouttes :
>
> Le 17/09/2017 à 22:30, Stephan Witt a écrit :
>> Am 17.09.2017 um 21:27 schrieb Jean-Marc Lasgouttes :
>>>
>>> Le 17/09/2017 à 19:48, Stephan Witt a écrit :
Hi JMarc,
another problem I’ve seen: after running view-pdflatex e.g.
>>
Le 17/09/2017 à 22:30, Stephan Witt a écrit :
Am 17.09.2017 um 21:27 schrieb Jean-Marc Lasgouttes :
Le 17/09/2017 à 19:48, Stephan Witt a écrit :
Hi JMarc,
another problem I’ve seen: after running view-pdflatex e.g.
the work area doesn’t show correct background color.
Wow. The situation is w
Le 18/09/2017 à 12:12, Stephan Witt a écrit :
I’m using a self-compiled hunspell with explicit given include path. Please,
don’t break this for RC1.
I do not think we are going to make big changes like that for rc1. We
just want to update the built-in one.
JMarc
2017-09-18 12:12 GMT+02:00 Stephan Witt :
> I’m using a self-compiled hunspell with explicit given include path.
> Please, don’t break this for RC1.
>
I will commit to master only first and ask CMakers to check before I
backport.
Jürgen
>
> Stephan
Le 18/09/2017 à 11:50, Stephan Witt a écrit :
I’m providing a mini screen-cast to demonstrate what happens.
1. Open splash
2. Cursor down twice
3. Resize window
Can you try to turn on the "painting" channel? My impression is the the
first paintings are do not use the FullScreenUpdate strategy
2017-09-18 11:53 GMT+02:00 Jean-Marc Lasgouttes :
> What could make it useful is that you could decide to enforce the use of
> the new C++ API (if we ever get it to work). If the system hunspell is not
> good enough, one can fall back on the bundled one.
>
Yes, right. I did not mean, however, tha
Am 18.09.2017 um 11:53 schrieb Jean-Marc Lasgouttes :
>
> Le 18/09/2017 à 11:41, Jürgen Spitzmüller a écrit :
>> I do not find this reasonable either. But it seems that nobody ever used
>> internal hunspell with automake anyway (otherwise, we would have known
>> earlier that it did not work).
>
Le 18/09/2017 à 11:41, Jürgen Spitzmüller a écrit :
I do not find this reasonable either. But it seems that nobody ever used
internal hunspell with automake anyway (otherwise, we would have known
earlier that it did not work).
What could make it useful is that you could decide to enforce the u
Am 18.09.2017 um 11:26 schrieb Jean-Marc Lasgouttes :
>
> Le 17/09/2017 à 22:32, Jean-Marc Lasgouttes a écrit :
>> Yes, it looks like it. I tried to run a bit with valgrind, but did not
>> detect anything useful. It could be related to Richard's font problems.
>
> Do you still see this issue aft
2017-09-18 11:34 GMT+02:00 Jean-Marc Lasgouttes :
> What is not reasonable is that we insist in disabling aspell and enchant
> what hunspell is used. What is the point? (I know, it is separate from your
> effort).
>
I do not find this reasonable either. But it seems that nobody ever used
internal
Le 12/09/2017 à 16:44, Pavel Sanda a écrit :
I tried, but... :)
Are you still able to compile on the ubuntu 12.04 oldie?
Even if I try beta tarball to avoid our autotools version requirements
it chokes on signal.h and its C++11 constructs. Are we completely
done with 12.04 or is there still some
Le 17/09/2017 à 18:28, Jürgen Spitzmüller a écrit :
Are you still trying? I have successfully updated to 1.6.2 here (more
or less the same subset, apart from one pair of files that has been
dropped from hunspell meanwhile, dictmgr.{cpp,h}).
I did not find time to progress on this front. Please
Le 17/09/2017 à 22:32, Jean-Marc Lasgouttes a écrit :
Yes, it looks like it. I tried to run a bit with valgrind, but did not
detect anything useful. It could be related to Richard's font problems.
Do you still see this issue after the last pair of fixes?
JMarc
Le 15/09/2017 à 17:39, Richard Heck a écrit :
The dark text is correct. It seems, quite generally, like the color is
not right when the painting begins at the top, but then it becomes right
when it is reset at the inset. If I scroll down, then when the inset
goes off the top of the screen, the te
Le 17/09/2017 à 22:33, Stephan Witt a écrit :
Am 17.09.2017 um 22:30 schrieb Jean-Marc Lasgouttes :
Le 17/09/2017 à 22:26, Stephan Witt a écrit :
It works.
Good, feel free to commit, or I'll do it tomorrow.
No need to do it fast.
The patch is in now (and in features/properpaint).
JMarc
Am 18.09.2017 um 05:55 schrieb Scott Kostyshak :
>
> On Sun, Sep 17, 2017 at 06:24:46PM +0200, Stephan Witt wrote:
>
>>> Den 13. sep. 2017 03:29, skrev Scott Kostyshak:
It actually amazes me how few people care about including bitmaps
>>
>> I certainly care too.
>
> Rereading the email I s
Am 18.09.2017 um 08:36 schrieb Jürgen Spitzmüller :
>
> Am Sonntag, den 17.09.2017, 22:51 +0200 schrieb Stephan Witt:
>> I’ve just learned that the converter calls for on-screen display in
>> build_script in GraphicsConverter.cpp and for export to pdf seem to
>> have different interpretation of $$
Am 17.09.2017 um 22:51 schrieb Stephan Witt :
>
> Am 17.09.2017 um 21:07 schrieb Stephan Witt :
>>
>> Am 17.09.2017 um 19:48 schrieb Jürgen Spitzmüller :
>>>
>>> Am Sonntag, den 17.09.2017, 15:26 +0200 schrieb Stephan Witt:
Because of the change directory coded in inkscape starter the $$i f
Am Sonntag, 17. September 2017 um 23:55:15, schrieb Scott Kostyshak
> On Sat, Sep 16, 2017 at 09:37:55PM +0200, Kornel Benko wrote:
>
> > > Ah good to know. Should that change be ported to 2.3.x?
> >
> > From my POV, yes.
>
> OK go ahead (if you have time).
>
> Scott
No problem, done at adfc
39 matches
Mail list logo
