Re: trunk r113878: Refine previous change.

[Stefan Monnier]

>> FWIW, I've fairly often written code which uses goto-char with
>> a position that can be outside of point-min...point-max, knowing that it
>> will go to the closest possible position.

> Did you ever pass a negative position?
> Were you passing a position outside the currently accessible portion of
> the buffer, but within the unnarrowed limits, or was it just an arbitrarily
> large value to mean "point-max" (and if so, why not just use point-max)?

Typically it's a slightly sloppy value.  E.g. (1- pos) or (1+ pos) or
just `pos' but where that position was valid in the past and some
buffer changes may have rendered it invalid.

So it typically is a valid position in 99% of the cases, but I know that
it's not guaranteed to be so in 100% of the cases.


        Stefan