Re: GUD octave support

[John W. Eaton]

On  6-Dec-2007, Nick Roberts wrote:

|  > | Normally a user would want the Octave's current behaviour, so this would
|  > | only be provided when Octave was invoked with the "--fullname" option.
|  > | 
|  > | Does that provide a clearer picture?
|  > 
|  > I think users would be surprised to see Z^ZFILENAME, or are you
|  > suggesting that this is an optional output format, not the one used
|  > for interactive users of Octave?
| 
| That's exactly what I am suggesting.  Normal users would not start Octave
| with the "--fullname" option.
| 
|  > In any case, with the current version of Octave, I see the following
|  > (for example):
|  > 
|  >   octave:1> dbstop plot 1
|  >   ans =  181
|  >   octave:2> plot
|  >   plot: line 181, column 7
|  >   isscalar
|  >   keyboard: stopped in /usr/share/octave/2.9.17/m/plot/plot.m at line 181
|  > 
|  > so isn't that already sufficient information for GUD?
| 
| I have Ubuntu Feisty with GNU Octave, version 2.1.73 (i486-pc-linux-gnu),
| and I see:
| 
|   octave:1> dbstop plot 1
|   ans = 178
|   octave:2> plot
|   plot: line 178, column 3
|   __gnuplot_set__
| 
| Maybe I'm doing something wrong, or maybe my version of Octave is too old.

2.1.73 is quite old.  The current recommended version is 2.9.18 (will
become 3.0 relatively soon).

| The output that you show is probably OK providing
| 
| 1) Octave doesn't output similar text at other times (ambiguity).
| 2) It always outputs fullnames?
| 
| and most importantly:
| 
| 3) That the format of this output doesn't change.  As it appears to be
|    intended for humans to read it is quite conceivable that someone
|    will `improve' it at sometime.
| 
| The advantage of using something like:
| 
| ^Z^ZFILENAME:LINENO
| 
| is that it is unambiguous, as Octave would not normally output ^Z^Z and
| unlikely to change, so matching the regexp won't break.

OK, I'd consider a patch.  I think some other option name like
--gud-mode would make more sense than --fullname.

jwe