[Octave-bug-tracker] [bug #60453] Input function on windows fails to trim carriage return character when running in batch mode

[Rik]

Follow-up Comment #5, bug #60453 (project octave):

Starting at the other end with the input() function itself, the code is very
simple


  octave::input_system& input_sys = interp.get_input_system ();

  return input_sys.get_user_input (args, std::max (nargout, 1));


Maybe the constructor for either the interpreter or the input_system is called
differently or not initialized fully when Octave believes it is running in
batch mode.

In Octave's defense, batch mode is not meant to be interactive.  Typically a
programmer develops a script in interactive mode, tests it with sample data,
and when it is completely debugged it is ready for using in batch mode where
you call "octave script data_file".

Because it is uncertain how, and therefore when, this will be fixed I would
just use the simple workaround of adding "--no-gui" to the command line when
running scripts like this.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60453>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/