I think there has been a subtle change in Octave --no-gui behavior in
the past ten or twenty changesets that wants to run the "first time
use"
configuration wizard. It may be this changeset:
http://hg.savannah.gnu.org/hgweb/octave/rev/6fe746def1aa
Also load settings and translations in --no-gui mode (bugs #44222 and
#45199)
Thanks for pointing to it. I wondered why my PPA build did not work,
but
locally everything was fine.
Stefan
Oups, I hadn't thought of this side effect. The configuration wizard
is the
only place where the user learns about where its settings will be
stored.
That's why I enabled it even in --no-gui where settings are now also
used.
On the other hand the only real configuration that this wizard currently
proposes is whether to show the news window, which is not relevant in
--no-gui mode.
I'll disable the wizard, until we find another solution (e.g. a
--no-wizard
flag).
Pantxo
IMHO the --no-gui option always implies a --no-wizard flag.
Stefan
What if the wizard is ever used to configure settings that are also
relevant in --no-gui mode (e.g. the language for the figure menus and
tool-tips)?
I don't think many users that use the --no-gui option will care about
the language settings or tooltips, except they creating their own GUI
with qthandles. However, for getting language information on command
line, the common way is to check the environment variables.
I attached a patch that I'll push on stable if no one opposes.
Note however that the criteria to launch the wizard is the presence of
an Octave settings file. I you first run --no-gui mode without a wizard,
a settings file will be created anyway (because it is now needed). Now
the first time you'll run octave in gui mode the wizard (and the
configuration, information contained therein) won't show up as a
configuration file already exists.
Why is it needed? It was not needed before your change (6fe746def1aa). I
can't find any setting that could be useful in no-gui mode. There's not
even a language setting in the config file.