[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug in command line completion
From: |
Jaroslav Hajek |
Subject: |
Re: Bug in command line completion |
Date: |
Tue, 26 May 2009 21:05:17 +0200 |
On Tue, May 26, 2009 at 5:24 PM, John W. Eaton <address@hidden> wrote:
> On 11-May-2009, Rik wrote:
>
> | The Mercurial tip for Octave shows an odd behavior for undefined
> | variables or functions. Specifically, after attempting to use an
> | undefined variable it is added to the command line completion list even
> | though it does not exist. This behavior is not present in the 3.0.0
> | stable release.
> |
> | To reproduce:
> | 1) type 'fo<TAB><TAB>' to show functions and variables starting with 'fo'.
> | Octave responds with:
> | fopen for fork format formula
> |
> | 2) type 'foobar<ENTER>'
> | Octave responds with:
> | error: `foobar' undefined near line 1 column 1
> |
> | 3) type 'fo<TAB><TAB>'
> | Octave responds with:
> | foobar fopen for fork format formula
> |
> | 'foobar' does not appear to be in any other symbol table as the
> | functions 'who' and 'which' know nothing about foobar.
>
> I checked in the following change for this problem.
>
> http://hg.savannah.gnu.org/hgweb/octave/rev/9c2349a51218
>
> I think this change is also a more complete fix for the problem
> with undefined symbols appearing in the output from who that Jaroslav
> fixed with 9250:80c299c84796.
>
> This change should probably be applied for 3.2.0.
>
OK, I'll include it in RC4.
--
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz