[Octave-bug-tracker] [bug #52567] invoking octave with conflicting arguments dumps core

[Dan Sebald]

Follow-up Comment #3, bug #52567 (project octave):

Works here.  Do you want some type of warning/error prompt before the message?
 E.g.:


error: --eval "CODE" and script file are mutually exclusive options
usage: octave [-HVWdfhiqvx] [--debug] [--debug-jit] [--doc-cache-file file]
       [--echo-commands] [--eval CODE] [--exec-path path]
       [--force-gui] [--help] [--image-path path]
       [--info-file file] [--info-program prog] [--interactive]
       [--jit-compiler] [--line-editing] [--no-gui] [--no-history]
       [--no-init-file] [--no-init-path] [--no-line-editing]
       [--no-site-file] [--no-window-system] [--norc] [-p path]
       [--path path] [--persist] [--silent] [--traditional]
       [--verbose] [--version] [file]


What is "warning()" function?  A gnulib command?  Or is it somehow accessing
the equivalent of Octave interpreter function "warning"?  If the latter, is
the use of "warning()" in the early stages of launch a problem?

    _______________________________________________________

Reply to this item at:

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

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