Skip to main content
Emacs

Return to Answer

replaced http://emacs.stackexchange.com/ with https://emacs.stackexchange.com/
Source Link
Community Bot
Community Bot
  • 1

(Migrated from a comment.)

If you can get Octave to work in the terminal but not in Emacs, it may be a problem with Emacs getting access to your OSX path. See this answerthis answer, which suggests installing the exec-path-from-shell package to deal with that problem (which you can do via the Emacs package manager: M-x list-packages).

(Migrated from a comment.)

If you can get Octave to work in the terminal but not in Emacs, it may be a problem with Emacs getting access to your OSX path. See this answer, which suggests installing the exec-path-from-shell package to deal with that problem (which you can do via the Emacs package manager: M-x list-packages).

(Migrated from a comment.)

If you can get Octave to work in the terminal but not in Emacs, it may be a problem with Emacs getting access to your OSX path. See this answer, which suggests installing the exec-path-from-shell package to deal with that problem (which you can do via the Emacs package manager: M-x list-packages).

Source Link
Dan ♦
Dan ♦
  • 33.4k
  • 7
  • 106
  • 171

(Migrated from a comment.)

If you can get Octave to work in the terminal but not in Emacs, it may be a problem with Emacs getting access to your OSX path. See this answer, which suggests installing the exec-path-from-shell package to deal with that problem (which you can do via the Emacs package manager: M-x list-packages).