Menu
I recently installed GNU Octave on my Mac using Homebrew and as soon as I typed octave into bash, it opened up the octave-gui window. The Octave GUI looks quite unappealing (on a mac, at least) so I wanted to use the command line interface. My fix was to create a permanent alias in ~/.bash_profile which was alias octave='octave --no-gui'.
Is there a more permanent fix to this? That is, how can I start using octave without invoking the GUI instead of the CLI? Is there a solution where I don't have to do this by using an alias. (Not that using the alias is a big issue, but I just wanted a better fix to starting Octave on the command line itself.)
752
In either case, you can immediately begin typing Octave commands. If you get into trouble, you can usually interrupt Octave by typing Control-C (written C-c for short). C-c gets its name from the fact that you type it by holding down CTRL and then pressing c. Doing this will normally return you to Octave's prompt.
The central window in the GUI is the Octave command-line interface. In this window Octave displays an initial message and then a prompt indicating it is ready to accept input. If you have chosen the traditional command-line interface then only the command prompt appears in the same window that was running a shell.
Find the GNU Octave entry in this editor and change the command to '/usr/bin/octave --force-gui' in the properties window. Thereafter tick off the box which asks the program to be run in the terminal. Voila!
I also install through brew I found that just run:
octave-cli you will see the octave in terminal:
GNU Octave, version 4.2.0-rc2 Copyright (C) 2016 John W. Eaton and others. This is free software; see the source code for copying conditions. There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or ... octave:1> According to here :
octave -W
will force octave to open in CLI. It works for me.
37
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
