Re: fprintf bug?

[John W. Eaton]

On  9-Aug-2006, Dmitri A. Sergatskov wrote:

| I see some bug with 2.9.7.
| If I do not put ";" after u (in my case u = 1) I get this junk:
| ...
| ii =  14
| u =  1
| ii =  15
| u =  1
| /bin/bash: -c: line 0: syntax error near unexpected token `('
| /bin/bash: -c: line 0: `lessecho -p0x22 -d0x22 -e\\ -n0x3b -n0x20
| -n0x2a -n0x3f -n0x9 -n0xa -n0x27 -n0x22 -n0x28 -n0x29 -n0x3c -n0x3e
| -n0x5b -n0x5d -n0x7c -n0x26 -n0x5e -n0x60 -n0x23 -n0x5c -- e(fid)'
| octave:4>

I assume you fed the complete code block to Octave by pasting it in a
window.  If so, then this happens because there are enough lines in
the output to invoke the pager at the end of the for loop.  At that
point, you are no longer interactinge with Octave, but with the
pager.  So it tries to read input from the terminal.  The next
characters are

  f c l o s e ( f i d ) \n

so then it tries to do these operations and fails with the funny
message above.  You can duplicate this problem with

  more on
  ones (100, 1)

and then at the less prompt, type

  f c l o s e ( f i d ) RET

I don't see how we can avoid this problem.

jwe