On Thu, Apr 05, 2018 at 15:31:06 +0100, D Haley wrote:
> Do we know if there is a particular commit that upstream applied to fix
> this?
FTR, it was fixed in this upstream commit
https://hg.savannah.gnu.org/hgweb/octave/rev/1265c7f0119a
And this fix is included in the upcoming Octave 4.4
Ah, ignore my last. I had incorrectly read the version numbering - I am
still running the same version as originally reported.
Apologies for the noise.
On 22/09/17 16:53, Mike Miller wrote:
> Control: forwarded -1 https://savannah.gnu.org/bugs/?52090
>
> On Thu, Sep 21, 2017 at 23:03:57 +0100,
Hi,
> I will try to push for upstream to keep the default value to false. A
> compromise position might be to have the first run dialog suggest that
> it be enabled, but if the setting is ever deleted manually or corrupted
> or unable to read in any way, it should always default to disabled.
>
Control: forwarded -1 https://savannah.gnu.org/bugs/?52090
On Thu, Sep 21, 2017 at 23:03:57 +0100, D Haley wrote:
> 1) The GUI should be clear as to what setting the backend is currently
> using. I think it is a concern that there are two settings that have the
> capacity to be "out-of-sync".
Thanks for keeping tabs here, I've been using --force-gui for some time
now, before it was the default. May or may not be a useful tidbit.
> Is it possible the qt-settings file is created by something other than
> Octave on your system?
I've only been using the current debian packages, and
On Thu, Sep 21, 2017 at 19:56:30 +0100, D Haley wrote:
> It looks like the QT UI does not match what happens internally in Octave
> if the line is absent from the file.
>
> If the line "allow_web_connection=true" is present, then the web
> connection proceeds, and the network tab in settings
P.S. I assume the reason for the line not being present is that it was
not written to the file in an earlier version, and I have upgraded to a
later version which only writes the line when re-creating the file from
scratch.
On 21/09/17 18:04, Mike Miller wrote:
> On Thu, Sep 21, 2017 at 17:58:04
Hi,
It looks like the QT UI does not match what happens internally in Octave
if the line is absent from the file.
If the line "allow_web_connection=true" is present, then the web
connection proceeds, and the network tab in settings reflects the setting.
If the line "allow_web_connection=false"
On Thu, Sep 21, 2017 at 17:58:04 +0100, D Haley wrote:
> Thanks for getting back so quickly. That command yields no output (no
> such line) - the file does however exist.
>
> $ grep allow_web_connection ~/.config/octave/qt-settings
> $
Ok. That indicates that the setting is not actually being
Hello,
Thanks for getting back so quickly. That command yields no output (no
such line) - the file does however exist.
$ grep allow_web_connection ~/.config/octave/qt-settings
$
On 21/09/17 17:55, Mike Miller wrote:
> On Thu, Sep 21, 2017 at 11:50:24 +0100, D Haley wrote:
>> I was a little
On Thu, Sep 21, 2017 at 11:50:24 +0100, D Haley wrote:
> I was a little concerned at this message, as in the settings, the option
> "Allow Octave to connect to the Octave web site to display current news
> and information" is unchecked.
This is troubling, thanks for reporting it.
I have looked
Package: octave
Version: 4.0.3-3
Severity: minor
Dear Maintainer,
I was having some network troubles recently, and I was using octave. A
short time after launching the program (octave --force, I was greeted
with "Octave's community news source seems to be unavailable. For the
latest news,
12 matches
Mail list logo
