[Top][All Lists]

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

[Octave-bug-tracker] [bug #52567] invoking octave with conflicting argum

From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #52567] invoking octave with conflicting arguments dumps core
Date: Fri, 1 Dec 2017 00:32:48 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

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

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

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:


  Message sent via/by Savannah

reply via email to

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