Re: Qt terminal status / linux distro packages

[Daniel J S. <dan...@ie...>]

On 08/22/2012 12:00 PM, Ethan A Merritt wrote:
> On Wednesday, August 22, 2012 07:10:44 am Daniel J Sebald wrote:
>
>> If the Qt terminal is included with the next release and the user
>> doesn't have Qt operational on his or her system, what will happen?
>> That's all I meant.
>
> So far the inclusion of the qt terminal is optional and must be requested
> specifically via
>     ./configure --enable-qt
>
> If you enable it but do not have the required dependencies installed then
> you get a configuration error message and gnuplot is built without qt even
> though you requested it.

OK.


> In the 4.6 release notes it is recommended to distribution packagers that
> they pick one of X11/wxt/qt for the package configuration rather than
> cramming all of them into a single build.   This is especially true since
> the wxt and qt terminals cannot be used together in a single session
> anyhow.  I have not tried to track the extent to which individual distros
> have followed this suggestion.

I don't know if leaving out the X11 terminal is a good idea.  At least 
one of the apps I know of will choose "x11" if the user doesn't set an 
environment variable specifying an alternative gnuplot terminal.  So, if 
the distro creators leave out x11 that will cause problems in at least 
this case.

To address this, the app will have to adjust accordingly but that means 
the distro creator will also have to get the latest for that app.

Is there some way for an external app to get back to the default 
terminal when gnuplot is launched?  That would solve the issue so that 
apps to have to specify a window based upon what system they run on.  Is 
there some way for an external app to query what the available terminals 
are?

... OK just tried a few things.  I see the way to get back to the 
default terminal is with "set term pop".  That's provided a "set term 
push" hasn't been done.  It's not exactly the same as going back to the 
default.  Why does "unset term" behave the way it does?  It basically is 
the same as "set term", i.e., displays a list of available terminals. 
Why would a list be displayed for an operation that wants to unset 
something?  For example, one wouldn't write "unset term eps".


> Mojca Miklavec<moj...@gm...>  wrote:
>> [ OpenSUSE 11.1 pkg-config error ]
>> Bad maintenance. Bug closed as "NO RESPONSE" here:
>>      https://bugzilla.novell.com/show_bug.cgi?id=715882
>> One should reopen it or file a new one.
>
> I don't think we should try too hard to retroactively work around
> distro packaging errors.  It was never our error, OpenSUSE has fixed
> it in a later release, and the work-around is obvious from both the
> gnuplot and the SUSE bug trackers.   Let's just disregard this and
> move on.

Yeah, that one isn't an issue, just bad luck.

As far as my operation, Qt looks nice aside from the print problem Mojca 
reports and a small bug in the coordinate computations for the key box 
that I created a bug-report for.  Then there is Windows Qt; I'll see if 
I can find someone interested in testing that.

Dan