Re: qt_processTermEvent received a GE_fontprops event. This should not have happened

[Tatsuro M. <tma...@ya...>]

----- Original Message -----

> From: Tatsuro MATSUOKA 
> To: Merritt Ethan ; gnuplot-beta
> Cc: 
> Date: 2018/3/15, Thu 10:36
> Subject: Re: qt_processTermEvent received a GE_fontprops event. This should not have happened
> 
> ----- Original Message -----
> 
>>  From: sfeam 
>>  To: gnuplot-beta Tatsuro MATSUOKA 
>>  Cc: 
>>  Date: 2018/3/15, Thu 10:09
>>  Subject: Re: qt_processTermEvent received a GE_fontprops event. This should 
> not have happened
>> 
>>  On Thursday, 15 March 2018 09:38:21 Tatsuro MATSUOKA wrote:
>>>   On Ubuntu on WSL and Cygwin
>>> 
>>>   At first plot in gnuplot in the bash session.
>>> 
>>>   $ gnuplot-qt
>>>   gnuplot> pl x
>>> 
>>>   Warning: slow font initializationgnuplot> qt_processTermEvent 
> received a 
>>  GE_fontprops event. This should not have happened
>>> 
>>>   plot is
>>>   http://www.geocities.jp/tmgpltwin/Files/gnuplot_qt_first_20180315.png
>>> 
>>>   If re-execute
>>>   pl x
>>>   plot becomes correct.
>>> 
>>>   Then
>>> 
>>>   gnuplot> exit
>>>   And re-execute gnuplot
>>>   $ gnuplot-qt
>>> 
>>>   gnuplot> pl x
>>> 
>>>   Then plot is correct.
>>> 
>>>   Perhaps interaction between gnuplot and X-sever has some issue.
>>>   Am I right?
>> 
>>  Not the X-server, the font server.
>>  If the font is not yet in the system font cache it must be
>>  processed and stored.  This can be slow, so the first time
>>  a font is requested you may get the error message about
>>  "slow font initialization".  After that the font is in the
>>  cache so access is fast.  On my systems the font cache
>>  is persistent so you would generally only see such a message
>>  if you have not logged in or run gnuplot for a long time.
>>  I do not know how persistent the cache is under Windows.
>> 
>>>   Does anyone know work around?
>> 
>>  If it only happens once per session I don't think it an an error.
>>  The font server really is slow on the first access and gnuplot
>>  is telling you that.  The same thing would happen for any other
>>  program that requested a font for the first time, but it might
>>  not print a message.
>> 
>>      Ethan
> Thank for explanation.
> 
> I also think it is an error.
> But I want a workaround.
> 
> 
> (Recently I use VxXsrv as Xsever.)
> If I use Cygwin/X, the behavior disappear and work as expected gnuplot-qt on 
> Cygwin.
> Perhaps all processes being executed in cygwin solves the issue.
> 
> After using below, I can use Cygwin/X on WSL.
> https://superuser.com/questions/1180005/cygwin-x-and-windows-subsystem-for-linux
> However, the situation is the same as that in VcXsrv.
> 
> For WSL, I have consider something different.
> 
> Anyway, thanks for the hint.
> 
> Tatsuro

Dirty workaround for WSL
I describe the below in ~/.bashrc

gnuplot5 -e "set term qt; pl x; exit"

gnuplot flush appears ar bash start-up.

Much better workaround will exist.

Anyway thank for explanation again.
Tatsuro