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

[Markus Mützel]

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

We have this code block in octave.cc:
https://hg.savannah.gnu.org/hgweb/octave/file/26af8b64a739/libinterp/octave.cc#l403

    if (m_options.gui ())
      {
        if (m_options.no_window_system ())
          {
            std::cerr << "error: --gui and --no-window-system are mutually
exclusive options" << std::endl;
            octave_print_terse_usage_and_exit ();
          }
        if (! m_options.line_editing ())
          {
            std::cerr << "error: --gui and --no-line-editing are mutually
exclusive options" << std::endl;
            octave_print_terse_usage_and_exit ();
          }
        if (m_options.server ())
          {
            std::cerr << "error: --gui and --server are mutually exclusive
options" << std::endl;
            octave_print_terse_usage_and_exit ();
          }
      }


That makes me believe that we might need to take care in the initialization of
the interpreter to not use a combination of settings that we need to avoid
presumably. (In this case, running the GUI combined with setting `line_editing
= false;`.)

Is there an easy way to check during interpreter initialization if we are
using the GUI?


    _______________________________________________________

Reply to this item at:

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

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