Re: [Nano-devel] ready for testing: nano-1.3.8pre2

[David Lawrence Ramsey]

Mike Frysinger wrote:

<snip>

>is it just me or is the 'goto line #' feature broken ?
>
>ctrl+w -> ctrl+t -> 54
>nano tells me to be reasonable instead of going to line 54 :(

Hmmm.  I can't seem to reproduce this.  When I do the above, nano goes
to line 54 as expected.  There used to be a bug in parse_line_column()
that caused a problem like this, but I fixed it weeks ago, before there
were any 1.3.8 prereleases.  The only way it should be failing on that
is if you have a comma after "54" without a column number after it.

You could try setting a breakpoint on parse_line_column() with gdb, and
seeing what values are placed into *line and *column.  For your example,
*line should obviously be 54, and *column should be (placewewant + 1),
since it's unspecified.  If they don't match, please let me know.