Octave took over Terminal.app in Mac OS X

[Louyclare]

I have installed Octave 3.0.0 on my Intel Mac OS 10.4.11. It seems to have configured itself to automatically run in the Terminal.app. This behavior is fine with me, however, whenever I launch the Terminal.app to run a shell (e.g. bash or tcsh) it automatically launches in Octave. The first line in the Terminal is: imac-2006:~ louyclare$ exec '/Applications/Octave.app/Contents/Resources/bin/octave' When I quit Octave, the Terminal.app window closes. Bringing up a new Terminal window simply re-launches Octave. This behavior is unaffected by the Terminal Preferences settings. The setting for "When creating a new Terminal window:" has two radio button options: 1) Execute the default login shell using /usr/bin/login and 2) Execute this comand (specify complete path): I have /bin/bash in the area provided. Does anybody know how I can run Octave in the Terminal.app and still launch Terminal.app in a shell?

[Thomas Treichl]

Louyclare schrieb:

> I have installed Octave 3.0.0 on my Intel Mac OS 10.4.11. It seems to
> have configured itself to automatically run in the Terminal.app. This
> behavior is fine with me, however, whenever I launch the Terminal.app to
> run a shell (e.g. bash or tcsh) it automatically launches in Octave. The
> first line in the Terminal is: imac-2006:~ louyclare$ exec
> '/Applications/Octave.app/Contents/Resources/bin/octave' When I quit
> Octave, the Terminal.app window closes. Bringing up a new Terminal
> window simply re-launches Octave. This behavior is unaffected by the
> Terminal Preferences settings. The setting for "When creating a new
> Terminal window:" has two radio button options: 1) Execute the default
> login shell using /usr/bin/login and 2) Execute this comand (specify
> complete path): /I have /bin/bash in the area provided/. Does anybody
> know how I can run Octave in the Terminal.app and still launch
> Terminal.app in a shell?

Hi Louyclare,

This should be working per default. Normally, if you double-click Octave.app's
icon then a Terminal.app opens and executes Octave inside (so Octave doesn't run
as a bash replacement but is executed from bash with the line exec
'/Applications/Octave.app/Contents/Resources/bin/octave' - can you reproduce that?).

If you double-click the Terminal.app icon then Terminal.app opens. There is some
setting on Macs where this may be overwritten but it is not overwritten from
Octave.app. Somebody already reported such a behaviour some time ago but I don't
know how it was fixed, maybe this helps for you

   http://www.nabble.com/octave-stole-my-Terminal-td12640966.html#a12642832

If you find out more details then please let us know about it.

   Thomas

PS. My radio-button options settings of Terminal.app always is 1) Execute the
default login shell using /usr/bin/login
_______________________________________________
Help-octave mailing list
Help-octave@...
https://www.cae.wisc.edu/mailman/listinfo/help-octave

[Fumihiro CHIBA]

Hello

It is supposed: you use the bash shell; and Octave.app is located in  
Applications folder.

Please try the following commands
$ alias octave="/Applications/Octave.app/Contents/Resources/bin/octave"
$ octave
or
put the following ".bash_profile" on your home directory.
------------------->8------------------------
if [ -f ~/.bashrc ];then
         . ~/.bashrc
fi
PATH=$PATH:/usr/local/bin
BASH_ENV=~/.bashrc
export BASH_ENV PATH
export GNUTERM=x11
alias octave="/Applications/Octave.app/Contents/Resources/bin/octave"
alias gnuplot="/Applications/GnuPlot.app/Contents/Resources/bin/gnuplot"
------------------->8------------------------
where I use gnuplot with X11. If you want to use gnuplot with  
aquaterm, change
"export GNUTERM=x11"  to "export GNUTERM=aqua".


With regards,
-----------------------
Fumihiro CHIBA

On 2008/01/06, at 3:26, Louyclare wrote:

> I have installed Octave 3.0.0 on my Intel Mac OS 10.4.11. It seems  
> to have configured itself to automatically run in the Terminal.app.  
> This behavior is fine with me, however, whenever I launch the  
> Terminal.app to run a shell (e.g. bash or tcsh) it automatically  
> launches in Octave. The first line in the Terminal is: imac-2006:~  
> louyclare$ exec '/Applications/Octave.app/Contents/Resources/bin/
> octave' When I quit Octave, the Terminal.app window closes.  
> Bringing up a new Terminal window simply re-launches Octave. This  
> behavior is unaffected by the Terminal Preferences settings. The  
> setting for "When creating a new Terminal window:" has two radio  
> button options: 1) Execute the default login shell using /usr/bin/
> login and 2) Execute this comand (specify complete path): I have /
> bin/bash in the area provided. Does anybody know how I can run  
> Octave in the Terminal.app and still launch Terminal.app in a shell?
> View this message in context: Octave took over Terminal.app in Mac  
> OS X
> Sent from the Octave - General mailing list archive at Nabble.com.
> _______________________________________________
> Help-octave mailing list
> Help-octave@...
> https://www.cae.wisc.edu/mailman/listinfo/help-octave

_______________________________________________
Help-octave mailing list
Help-octave@...
https://www.cae.wisc.edu/mailman/listinfo/help-octave

[Louyclare]

Hi Thomas,

When I double click the Octave.app icon I get a Terminal window with Octave running. When I double click the Terminal.app icon I get the exact same thing, a Terminal window with Octave running.

I looked through the posts that you referred me to on:

http://www.nabble.com/octave-stole-my-Terminal-td12640966.html#a12642832

The originator of that thread seemed to have exactly the same problem that I am having. By the end of the thread, he still did not have a solution though. One band-aid offered in a post that seems to help is typing the following command at the Octave prompt:

system ("exec bash")

This takes me out of Octave and into a bash shell. Exiting this takes me right back to Octave. So it appears that somehow Octave has somehow become my default shell in Terminal.app.

Interestingly, the same behavior does not occur with an X11 terminal window. Launching an xterm takes me straight to a bash shell. From here I can type the command:

exec '/Applications/Octave.app/Contents/Resources/bin/octave'

then Octave launches. Exiting Octave takes me back to the bash command prompt.

I did find something that may be the ultimate source of the problem, but I don't know how it is involved. That is the file:

/Applications/Octave.app/Contents/Resources/script

This appears to be a #!/bin/sh script that in turn executes an applescript that launches Octave. I don't know how or where this script file is called, however. There is nothing in my .bashrc or .profile that sources anything mysterious.

Louyclare

Thomas Treichl wrote:

Louyclare schrieb:
> I have installed Octave 3.0.0 on my Intel Mac OS 10.4.11. It seems to
> have configured itself to automatically run in the Terminal.app. This
> behavior is fine with me, however, whenever I launch the Terminal.app to
> run a shell (e.g. bash or tcsh) it automatically launches in Octave. The
> first line in the Terminal is: imac-2006:~ louyclare$ exec
> '/Applications/Octave.app/Contents/Resources/bin/octave' When I quit
> Octave, the Terminal.app window closes. Bringing up a new Terminal
> window simply re-launches Octave. This behavior is unaffected by the
> Terminal Preferences settings. The setting for "When creating a new
> Terminal window:" has two radio button options: 1) Execute the default
> login shell using /usr/bin/login and 2) Execute this comand (specify
> complete path): /I have /bin/bash in the area provided/. Does anybody
> know how I can run Octave in the Terminal.app and still launch
> Terminal.app in a shell?

Hi Louyclare,

This should be working per default. Normally, if you double-click Octave.app's
icon then a Terminal.app opens and executes Octave inside (so Octave doesn't run
as a bash replacement but is executed from bash with the line exec
'/Applications/Octave.app/Contents/Resources/bin/octave' - can you reproduce that?).

If you double-click the Terminal.app icon then Terminal.app opens. There is some
setting on Macs where this may be overwritten but it is not overwritten from
Octave.app. Somebody already reported such a behaviour some time ago but I don't
know how it was fixed, maybe this helps for you

   http://www.nabble.com/octave-stole-my-Terminal-td12640966.html#a12642832

If you find out more details then please let us know about it.

   Thomas

PS. My radio-button options settings of Terminal.app always is 1) Execute the
default login shell using /usr/bin/login
_______________________________________________
Help-octave mailing list
[e-mail]
https://www.cae.wisc.edu/mailman/listinfo/help-octave

[Thomas Treichl]

Louyclare schrieb:

> Hi Thomas,
>
> When I double click the Octave.app icon I get a Terminal window with Octave
> running. When I double click the Terminal.app icon I get the exact same
> thing, a Terminal window with Octave running.
>
> I looked through the posts that you referred me to on:
>
> http://www.nabble.com/octave-stole-my-Terminal-td12640966.html#a12642832
>
> The originator of that thread seemed to have exactly the same problem that I
> am having. By the end of the thread, he still did not have a solution
> though. One band-aid offered in a post that seems to help is typing the
> following command at the Octave prompt:
>
> system ("exec bash")
>
> This takes me out of Octave and into a bash shell. Exiting this takes me
> right back to Octave. So it appears that somehow Octave has somehow become
> my default shell in Terminal.app.
>
> Interestingly, the same behavior does not occur with an X11 terminal window.
> Launching an xterm takes me straight to a bash shell. From here I can type
> the command:
>
> exec '/Applications/Octave.app/Contents/Resources/bin/octave'
>
> then Octave launches. Exiting Octave takes me back to the bash command
> prompt.
>
> I did find something that may be the ultimate source of the problem, but I
> don't know how it is involved. That is the file:
>
> /Applications/Octave.app/Contents/Resources/script
>
> This appears to be a #!/bin/sh script that in turn executes an applescript
> that launches Octave. I don't know how or where this script file is called,
> however. There is nothing in my .bashrc or .profile that sources anything
> mysterious.
>
> Louyclare

Louyclare,

I was able to reproduce the problem - my Terminal.app now behaves the same like
yours and a similar problem with a solution how to solve it can be found in the
Internet. There is a bug in Terminal.app (seems to be on my 10.4.9 system, too).
A description about what is going on is here:

   http://www.macusenet.com/archive/index-t-36473.html

Ok, sow how I could solve my problem: I double-clicked Terminal.app (which
automatically calls our exec '.../octave' script that we have written) and then
I called the 'system' command in Octave

   octave-3.0.0:1> system ("exec bash")

on that system command I type

   MyMac:~$ rm ~/Library/Preferences/com.apple.terminal.plist

to restore my Terminal.app's defaults and then I close Terminal.app via the main
menu to make sure all windows are closed and no other running script is left in
any of the windows. That's it, does it work for you, too?

And after that quest I will never press the 'Apply All' menu entry in the window
menubar of Terminal.app anymore ;)

   Thomas
_______________________________________________
Help-octave mailing list
Help-octave@...
https://www.cae.wisc.edu/mailman/listinfo/help-octave