octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #49589] octave --eval starts slightly differen


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #49589] octave --eval starts slightly differently from octave --no-gui --eval
Date: Sat, 17 Dec 2016 20:34:41 -0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0

URL:
  <http://savannah.gnu.org/bugs/?49589>

                 Summary: octave --eval starts slightly differently from
octave --no-gui --eval
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Fri 11 Nov 2016 12:26:21 PM PST
                Category: Interpreter
                Severity: 1 - Wish
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: Postponed
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

This has to do with the controlling terminal and the way the octave executable
is or is not detached from the terminal.

Compare the following


$ octave --no-gui --eval "system (sprintf('ps o tname h %d', getpid));"
pts/1
$ octave --eval "system (sprintf('ps o tname h %d', getpid));"
?


Obvious workaround is to always run batch scripts with the --no-gui option,
but I think (maybe it's just me) that it would be nice if Octave knew that if
it is not running in interactive mode, it should not fork and detach from the
controlling terminal.

I am sure I have seen some odd behavior with signals or job control relating
to this, which is when I first noticed it and started running all batch
command tests with --no-gui.

I don't see an easy way to do this other than replicating the entire command
line processing logic from the full octave program into the octave shim
wrapper, so that it knows whether octave-gui will be running the GUI or not.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?49589>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]