On 03/31/2016 02:50 PM, Stefan Monnier wrote:
> (it would break some code, but most of it is already fundamentally
> broken because it should use `point-min` rather than hardcoding 1, so
> it's not *that* terrible).

Amusingly, always using (point-min) also leads to interesting bugs. For example, Proof General uses one large overlay to indicate which part of a buffer has been processed. When updated, that overlay is set to cover (point-min) to (end of last processed statement). Of course, when narrowing is in effect, this means that the overlay is made to start at the lowest narrowed point; then when the buffer is widened, you realize that the bounds of the overlay are wrong.