Re: Octave 4.4 Proposal: make --no-gui the default

[Daniel J Sebald]

On 03/15/2018 09:48 PM, Daniel J Sebald wrote:
> On 03/14/2018 12:26 PM, Mike Miller wrote:
> > On Wed, Mar 14, 2018 at 12:24:29 -0500, John W. Eaton wrote:
> > > On 03/14/2018 11:57 AM, avlas wrote:
> > >
> > > > Wondering actually if you would consider applying this also to 
> > > > Octave 4.2.2...
> > >
> > > It's too late for that, 4.2.2 is already on ftp.gnu.org.
> >
> > This also doesn't seem like an appropriate change for a patch release.
>
> I just read the emails for this thread.  I'm not sure what the proper 
> syntax is supposed to be, but I'm having poor results with the latest 
> tip, with --no-gui option or no option.  It's as if Octave command line 
> immediately comes back to the shell prompt.  It looks like Octave has 
> simply exited after the first line, but then I try again and start 
> getting the results of what I think are two Octave's running 
> simultaneously.  The words I type come out wrong, the keyboard seems 
> slow and unresponsive, then responsive for a bit.  I'll do a complete 
> rebuild and see if anything changes.
>
> Dan
>
>
> GNU Octave, version 4.5.0+
> Copyright (C) 2016 John W. Eaton and others.
> This is free software; see the source code for copying conditions.
> There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
> FITNESS FOR A PARTICULAR PURPOSE.  For details, type 'warranty'.
>
> Octave was configured for "x86_64-pc-linux-gnu".
>
> Additional information about Octave is available at http://www.octave.org.
>
> Please contribute if you find this software useful.
> For more information, visit http://www.octave.org/get-involved.html
>
> Read http://www.octave.org/bugs.html to learn how to submit bug reports.
> For information about changes from previous versions, type 'news'.
>
> octave:1> octave:1>
> octave:1>
> octave:1> octave:1>
> octave:1> octave:1>
> octave:1> octave:1>
> octave:1> octave:1> octave:1> terror: 'exi' undefined near line 1 column 1
> octave:1> xi
> error: 'txi' undefined near line 1 column 1
> octave:1> ierror: 'etext' undefined near line 1 column 1
> octave:1>
> ans =  0 + 1i
> octave:2> octave:1>
> octave:2> octave:1> q
> error: 'q' undefined near line 1 column 1
> octave:2> quitoctave:1> octave:1> octave:1>
> octave:2>
> octave:2>
> octave:2>
> octave:2> exiterror: 't' undefined near line 1 column 1
> octave:1>
>
> octave:2>
> octave:2> octave:1>
> octave:2> octave:1>
>
> octave:2> octave:1> octave:1>
> octave:2>
> octave:2> octave:1> octave:1> octave:1> octave:1>
> octave:2> octave:1> octave:1>
> octave:2>
> octave:2>
> octave:2> octave:1>


I think I've identified the issue.  With the change in meaning of the 
no-option version comes a restriction that one shouldn't be able to run 
Octave as a background process when there is no option.  So right now, 
with the tip there is a difference between

run-octave &

and

run-octave --no-gui &

the former being something many of us will be typing for a while out of 
habit.

I created a bug report here:

https://savannah.gnu.org/bugs/index.php?53355

Dan