[Pkg-octave-devel] Bug#522062: Bug#522062: octave3.0: can't edit function files from octave session
thomas.weber.mail at gmail.com
Sun Jan 3 17:59:39 UTC 2010
On Fri, May 01, 2009 at 06:48:00PM +0200, Thomas Weber wrote:
> On Wed, Apr 01, 2009 at 03:53:25PM +0200, Rafael Laboissiere wrote:
> > * Sergey B Kirpichev <skirpichev at gmail.com> [2009-03-31 17:43]:
> > > Package: octave3.0
> > > Version: 1:3.0.1-6lenny3
> > > Severity: normal
> > >
> > > How to reproduce:
> > > shell> mkdir -p ~/octave
> > > shell> unset DISPLAY
> > > octave> edit home "~/octave"
> > > octave> edit mode "sync"
> > > octave> EDITOR
> > > ans = vim
> > > octave> edit f.m
> > > Vim: Warning: Output is not to a terminal
> > >
> > > Workarround:
> > > Use gvim or emacs with X window support.
> > >
> > > Problem seems to be related to RETURN_OUTPUT parameter of the system()
> > > function. Compare, for example,
> > > octave> system("vim test.m")
> > > vs
> > > octave> system("vim test.m",) # edit() uses system() like this
There's a work-around given via xterm at
I don't think there's much more we can do. It seems not too many people
use a non-graphical editor from within an Octave session.
Unless someone comes up with a better idea, I will close this bug in the
More information about the Pkg-octave-devel