bugGNU Octave - Bugs: bug #42248, echo_executing_commands does not...

 
 

bug #42248: echo_executing_commands does not echo when executing from stdin

Submitted by:  Sigbert Klinke <sigbert>
Submitted on:  Wed 30 Apr 2014 04:05:01 PM UTC  
 
Category: InterpreterSeverity: 2 - Minor
Priority: 3 - LowItem Group: Regression
Status: Wont FixAssigned to: None
Originator Name: sigbertOpen/Closed: Closed
Release: 3.8.1Operating System: GNU/Linux

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Sun 07 Jun 2015 05:41:34 PM UTC, comment #3:

I think we can call this bug report resolved, reporter seems satisfied with using the ECHO_SCRIPTS value (1) instead of ECHO_CMD_LINE (4) with current versions of Octave to show input from non-interactive script text.

Mike Miller <mtmiller>
Project Administrator
Thu 01 May 2014 09:49:05 AM UTC, comment #2:

Using

delivers much more output since all the functions called by octave are displayed, too. I use octave as computing server and just want to see the user input echoed.

But the solution with "echo_executing_commands (1);" and
works as in 3.6.x. Thanks a lot.

Sigbert Klinke <sigbert>
Wed 30 Apr 2014 11:52:19 PM UTC, comment #1:

Confirmed, only applies to Octave commands sent to the interpreter on stdin. The correct behavior persists if you run your example as

telling Octave to run the m-file instead of reading it from the standard input stream. And either using the -x command-line option as shown above, or changing your script to set the echo_executing_commands value to 1 instead of 4.

Mike Miller <mtmiller>
Project Administrator
Wed 30 Apr 2014 04:05:01 PM UTC, original submission:

The attached test.m called from the command line via "octave -qf < test.m" results in 3.8.0 & 3.8.1:

and in 3.6.4:

If I start octave 3.8.1 and type in the command by hand then I get the same result as in 3.6.4.

The problem might be with the function

in the file libinterp/corefcn/input.cc .

When typing in the commands within octave the function is called, when calling "octave -qf < test.m" the function seems not be called.

Sigbert Klinke <sigbert>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

Attached Files
file #31288:  test.m added by sigbert (95B - text/x-objcsrc)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by rik5 (Updated the item)
  • -unavailable- added by mtmiller (Posted a comment)
  • -unavailable- added by sigbert (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 9 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sun 07 Jun 2015 05:41:34 PM UTCmtmillerStatusConfirmed=>Wont Fix
      Open/ClosedOpen=>Closed
    Mon 02 Feb 2015 03:48:41 AM UTCrik5Priority5 - Normal=>3 - Low
    Wed 30 Apr 2014 11:52:19 PM UTCmtmillerCategoryOctave Function=>Interpreter
      Severity3 - Normal=>2 - Minor
      Item GroupIncorrect Result=>Regression
      StatusNone=>Confirmed
      Summaryecho_executing_commands delivers unexpected output=>echo_executing_commands does not echo when executing from stdin
    Wed 30 Apr 2014 04:05:01 PM UTCsigbertAttached File-=>Added test.m, #31288

    Back to the top


    Powered by Savane 3.1-cleanup1