Re: Bug#522062: octave3.0: can't edit function files from octave session

[Rafael Laboissiere]

* Sergey B Kirpichev <address@hidden> [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

I seems that octave is now unable to launch an editor in the terminal it
is running.  For instance, doing:

    octave> edit editor "/usr/bin/vim %s"
    octave> edit f.m
    Vim: Warning: Output is not to a terminal

is similar to doing in the shell:

    shell> /usr/bin/vim f.m > /dev/null
    Vim: Warning: Output is not to a terminal

I am not sure this is a real bug.  I am forwarding this reply to the
help-octave mailing list (please, respect the M-F-T header).  Let us see
what they tell us.

-- 
Rafael